## TL;DR

Keep each personalization's substitution data under the 10,000 byte limit; large per-recipient payloads fail the whole request.

## Steps

1. Goal: one request, thousands of personalized messages, fully attributable.

2. Step 1. Build the personalizations array: one entry per recipient with their to address and per-recipient dynamic_template_data or substitutions.

3. Step 2. Attach custom_args per personalization: your internal user id, campaign id, or segment. These ride along with the email and come back in the events, so you can join SendGrid events to your own tables.

4. Step 4. Chunk large audiences into multiple requests rather than one giant call; a single malformed personalization can fail the batch.

5. Step 5. Join events back on custom_args: delivered, open, and click events per user id give per-recipient funnels.

6. Verify: test to seed addresses with distinct data each, confirm each seed got the right content, and confirm custom_args appear in the events. Pitfall: custom_args get no substitution, so put literal values there.

## When to use

You are seeing this: Goal: one request, thousands of personalized messages, fully attributable. Use this skill when you run into "SendGrid per-recipient personalization at bulk scale".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
