Where merges go wrong
A template that reads well with your own name in it can still misfire on row 214. The usual culprits are not spelling mistakes in the template but the data behind it: a first name column filled with Info because the contact was taken from info@, a company name in capitals straight from a registry, a town left blank, or N/A typed by whoever built the list. Each produces an email that tells the recipient it was sent in bulk without anyone looking.
Most sending tools show you one sample, usually the first row. This preview walks through all of them, collects the problems in one table and lets you step through only the rows that need attention, so you can fix the spreadsheet once instead of apologising later.
Checking a merge
Write the template
Type the subject and body. Insert data with
{{column name}}and add a fallback after a vertical bar, as in{{first_name|there}}, for values that may be empty. Matching ignores case, spaces and underscores, so{{First Name}}finds afirst_namecolumn.Add the recipients
Choose the CSV or paste it. The first row must hold the column names. Delimiters are detected for you, and up to 5,000 rows are merged.
Read the field strip
Every token appears as a chip, red if no column matches it. Below it you will see fields written in another program's syntax, such as
{first_name}or*|FNAME|*, that would be sent as typed, and the columns your template never uses.Step through the rows
Use Previous and Next to read each merged email with its problems listed underneath. Switch to Rows with problems to skip the clean ones.
Fix and export
Correct the CSV or add fallbacks, then download the merged CSV. It keeps your columns and adds the merged subject, merged body, a status of ok, check or fix, and the problems found.
Example: five rows, three kinds of trouble
The template opened with Hi {{first_name|there}},, mentioned {{company}} twice, {{trade|local businesses}} once and {{town}} once, and had no fallback for the town. The five fictional rows produced two clean emails, one to check and two to fix.
Row 3 came out as "Hi Info," and "QUAY JOINERY LTD", and its empty town left "in ." in the middle of a sentence. Row 4 had no first name or trade, so both fallbacks were used and the email read naturally. Row 5 gave "Hi tom," in lower case and the town placeholder N/A was treated as missing. Row 6 repeated row 2's address, so that person would have received the email twice.
email,first_name,company,trade,town priya@harbourdental.example,Priya,Harbour Dental Ltd,dental practices,Leeds info@quayjoinery.example,Info,QUAY JOINERY LTD,joiners, sam@glenbakery.example,,Glen Bakery,,York tom@marshplumbing.example,tom,Marsh Plumbing,plumbers,N/A priya@harbourdental.example,Priya,Harbour Dental Ltd,dental practices,Leeds
Row 3 Check: "company" is in capitals ("QUAY JOINERY LTD").
Row 3 Check: "first_name" is a role word ("Info").
Row 3 Fix: "town" is empty and has no fallback: the text has a gap.
Row 5 Check: "first_name" is all lower case ("tom").
Row 5 Fix: "town" holds a placeholder ("N/A") and has no fallback.
Row 6 Check: Same email address as row 2.What the preview checks
Value checks only run on columns the template actually uses, so an untidy notes column you never merge will not fill the report.
| Check | Level | Example that triggers it |
|---|---|---|
| Token with no matching column | Fix | {{postcode}} when the CSV has no postcode column |
| Empty value and no fallback | Fix | Blank town in "based in {{town}}" |
| Greeting left without a name | Fix | "Hi ," after merging |
| No email address in the row | Fix | Empty email column |
| Placeholder text | Check or fix | N/A, null, TBC, a lone dash |
| Capitals or all lower case | Check | PRIYA, tom |
| Company name in a name field | Check | first_name = Harbour Dental Ltd |
| Role word as a name | Check | Info, Sales, Office, Team |
| Full name in a first name field | Check | first_name = Priya Shah |
| Same address twice | Check | Duplicate email rows |
| Fallback used | Note | {{first_name|there}} on a blank name |
Before the merged emails go anywhere
- Give every optional token a fallback that still reads as a sentence, and leave required fields such as the company without one so gaps stay visible.
- Replace merge syntax from other tools with
{{ }}tokens, or the recipient sees the raw placeholder. - Fix role words and capitals in the CSV rather than in the template, so the next campaign starts clean.
- Remove duplicate addresses and anyone on your suppression list before importing the list into your sender.
- Keep a clear opt-out line in the template body, since a merge cannot add one later.
- Read at least three merged rows aloud, including one that uses every fallback.
Questions people ask
How do I preview a mail merge before sending?
Paste your template and recipient CSV here and step through each merged email. The tool fills every token from the matching column, shows the result row by row and lists the problems it finds, from empty values to names in capitals. Fix the data, check the preview again, then load the cleaned list into whichever program does the sending.
What is a fallback in a merge field?
A fallback is the text used when a value is empty. Written as {{first_name|there}}, it turns a blank name into "Hi there," instead of "Hi ,". Fallbacks suit optional fields such as a first name or a trade. For essential details such as the company name, leaving the fallback out is safer, because the preview then flags the row for fixing.
Why are my merge fields not being replaced?
Either the token names a column that does not exist, or it uses another program's syntax. This preview matches {{tokens}} to column names regardless of case, spaces and underscores, and shows unmatched tokens in red. Placeholders such as {first_name}, [First Name], %Company% or *|FNAME|* are listed separately because they would be sent exactly as typed.
Can I use this with Gmail, Outlook or Word mail merge?
Use it to clean the data and test the wording; the sending happens elsewhere. Word, Outlook and most Gmail add-ons have their own field syntax, so once the CSV is tidy, either rewrite the tokens in that syntax or use the merged CSV, whose merged_subject and merged_body columns hold the finished text for each row.
Is my contact list uploaded?
No. The template and the CSV are processed by JavaScript in this tab, and the merged CSV is created on your device. Nothing is sent to Map Extract, to an email provider or to anyone else, and closing the page clears it all.
Where your data goes
Your template and recipient list stay in this browser tab. Parsing, merging and the checks run locally, and the merged CSV download is built on your device. No email is sent and nothing is stored.
Checked against the tool on