# Event email merge-tag case matrix

English worksheet for one campaign version. Use internal case IDs, not attendee names, email addresses, ticket codes or access links. Test only in an authorized environment or tightly controlled audience.

## Message and field inventory

| Field | Source system and exact field | Event edition | Optional copy or material instruction? | Approved fallback or hold owner |
|---|---|---|---|---|
| Recipient role (buyer or ticket holder) | | | | |
| Greeting name | | | | |
| Event date and local time | | | | |
| Venue, entrance or online joining route | | | | |
| Ticket or access category | | | | |
| Language or message variant | | | | |
| Link destination | | | | |
| Other: | | | | |

## Controlled cases

Add a row for every conditional branch that changes an action. “Expected” must say what the *resolved message* should show, not merely whether the template contains a token.

| Case ID | Record condition | Expected audience/variant | Expected resolved fact or fallback | Observed subject/body/link | Pass, hold or exclude | Owner / correction |
|---|---|---|---|---|---|---|
| A | Complete record for this event edition | | | | | |
| B | Optional name absent | | Neutral greeting or approved copy | | | |
| C | Material date, entrance or join field absent | | Hold until approved fact is available | | | |
| D | Record from another event edition | | Excluded or correct edition variant | | | |
| E | Ticket type or language changed after sync | | Current variant | | | |
| F | Buyer and ticket holder differ | | Approved recipient role | | | |
| G | Conditional access branch should not match | | Excluded branch | | | |

## Evidence and retest

| Check | Record |
|---|---|
| Campaign version, target audience and field map checked | |
| Provider method used: recipient-specific preview, controlled delivery or approved registration test | |
| Last source sync and profile value checked | |
| Subject, preview text, body, links, image text and footer reviewed | |
| Failed case fixed at source, mapping, rule, token or approved fallback | |
| Failed case and one previously passing case retested | |
| Actual recipient selection checked separately | |
| Unresolved material field and owner | |
| Final decision: send / hold, reviewer and time | |

A Mailchimp test email alone does **not** populate contact-specific audience merge tags. Use [Mailchimp's troubleshooting guidance](https://mailchimp.com/help/troubleshooting-merge-tags/) and [preview documentation](https://mailchimp.com/help/preview-and-test-your-email-campaign/) for its current controls. Other providers differ. This matrix does not approve an audience or prove delivery.