Email Personalisation Token and Merge Error Audit
Find broken merge tags, awkward fallbacks and wrong assumptions in personalised emails before they embarrass you in real inboxes.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Help me test personalisation in my email before sending. My email tool uses merge tags written like [TAG_SYNTAX_EXAMPLE]. I will paste the email template with all its tags and fallbacks: [EMAIL_TEMPLATE]. I will also paste ten sample contact records, including messy ones such as empty names, all-caps names, names with titles and company names: [SAMPLE_RECORDS]. Please do the following. 1) List every merge tag and fallback in the template. 2) Mentally render the email for each of the ten sample records, in a table with the columns Record, Rendered greeting, Rendered key line, and Problem (blank, "Hi ,", all caps, wrong order, company name used as a person's name, plural/singular mismatch, awkward possessive). 3) Counts: how many of the ten render cleanly, and what percentage that is. 4) Recommended fallbacks and phrasing that reads well even when data is missing, for example a neutral greeting. 5) A data cleaning list: fields to fix at the source, in priority order. 6) A pre-send test checklist, including sending to real test addresses and viewing on mobile. Rules: do not assume your rendering matches the tool; say it must be checked in a real preview and mark tool-specific syntax or fallback behaviour [VERIFY]. Do not invent tag names. Do not infer a person's gender, age or background from their name; recommend avoiding that.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.