GPT for Google Sheets, Docs AI, Slides, Forms

Preview and Test Your Gmail Mail Merge Before You Send

Preview and test-send a Gmail mail merge from Google Sheets before launch: catch broken merge tags, blank names, bad links and attachments, and wrong recipients with a simple QA checklist.

Preview and Test Your Gmail Mail Merge Before You Send

The fastest way to ruin a campaign is to send “Hi ,” to a few hundred people. Mail Merge for Gmail and Google Sheets lets you build your list in a spreadsheet, preview how messages will look per row, and run a test send so you catch mistakes before your recipients do.

Try Mail Merge for Gmail and Sheets →

Exact preview and test-send mechanics can vary by product version. Use this page as a workflow guide and confirm the specific buttons and options in your own setup before a large send.

Why preview and test sends matter in mail merge

A mail merge applies one template to many rows. That is powerful, but it also means a single mistake repeats across the whole list — a broken merge tag, a blank field, or the wrong link appears in every copy.

Previewing several rows and sending a test to yourself turns an invisible risk into something you can see and fix in minutes. It is the single highest-leverage habit for campaign quality.

The 7 mistakes to catch before sending

  1. Wrong or broken merge tags — a tag that does not match a column name shows up as raw text or blank.
  2. Blank names and empty fields — missing data produces “Hi ,” or awkward gaps; use fallbacks.
  3. Broken links — wrong, expired, or non-HTTPS links, especially merge-tagged ones.
  4. Bad attachments — the wrong file, a missing file, or the wrong per-row link where attachments are used.
  5. Wrong recipients — test rows, internal addresses, duplicates, or unsubscribed contacts left in the list.
  6. Formatting issues — broken layout, blocked images with no text fallback, or competing calls to action.
  7. Missing signature or opt-out — no sender identity, or no unsubscribe language on a marketing-style send.

Add a few control columns so nothing launches by accident:

Column Purpose
status Draft, ready, sent, replied, bounced
test_recipient Marks rows used only for internal test sends
reviewed Yes/no confirmation that the row was checked
send? Explicit go/no-go flag for the row
notes Owner notes, edge cases, personalization to double-check

Set up a reviewable Sheet campaign →

How to send a test email and review multiple rows

  1. Pick representative rows. Choose a typical row, a row with a long company name, and a row with a missing field.
  2. Send a test to yourself and a teammate. Use a test_recipient row or your own address, not a live contact.
  3. Read it as a recipient. Check the greeting, every merge field, and the fallbacks.
  4. Open on desktop and mobile. Layout and link sizing can differ.
  5. Click everything. The main call to action, every link, and any attachment or attachment link.
  6. Fix the template, not just one row. If a tag is broken in the test, correct the template so all rows are fixed.

Checklist before launching the full campaign

  • Recipient list cleaned: duplicates, bounces, and unsubscribes removed.
  • All merge tags match column names and have fallbacks.
  • Subject line is honest and renders correctly.
  • Links and call to action verified on multiple rows.
  • Attachments confirmed where used.
  • Signature, footer, and opt-out language present.
  • A small batch sent first before the full list.
  • Gmail/Workspace sending limits respected.

What to monitor after sending

Where supported, watch opens, clicks, replies, bounces, and unsubscribes so you can prioritize follow-ups and clean the list for next time. Treat a spike in bounces or opt-outs as a signal to pause and review list quality and message relevance. No tool can guarantee inbox placement, so ongoing monitoring matters.

Mail merge preview and test-send FAQ

How do I preview a Gmail mail merge before sending?

Choose a few representative rows and review how the message renders for each, checking merge fields, fallbacks, links, and formatting. Then send a test to yourself before launching the full list. Confirm the exact preview options in your product version.

How do I send a test email for a mail merge?

Send to your own address or a row flagged as a test recipient, not a live contact. Read it as a recipient, open it on desktop and mobile, and click every link and call to action.

What are the most common mail merge mistakes?

Broken merge tags, blank fields with no fallback, wrong or non-HTTPS links, bad attachments, wrong recipients, broken formatting or blocked images, and a missing signature or opt-out.

How many test rows should I check?

Check at least a typical row, a row with unusually long values, and a row with a missing field, so you catch both normal and edge-case rendering before sending.

What should I monitor after the campaign goes out?

Where supported, monitor opens, clicks, replies, bounces, and unsubscribes. A rise in bounces or opt-outs is a signal to pause and review list quality and message relevance.

Catch merge mistakes before your recipients do

Build the list in Google Sheets, preview several rows, send a test, then launch with confidence.

Try Mail Merge for Gmail and Sheets →