A Gmail campaign needs a recipient-data test as well as a visual test. A single attractive preview cannot establish that every merge field, attachment, sender identity, or unsubscribe choice will be correct when the message is sent.
Create a controlled test population
Use addresses you control or people who explicitly agreed to receive the test. Include representative rows: a complete name, a missing optional field, and any unusually long text. Keep the real contact list separate so the test cannot accidentally reach the full audience.
If using a spreadsheet, confirm the first tab, email column, and merge-tag mapping. Inspect names and addresses together. For a layout, use the actual final heading, images, buttons, and footer rather than a shorter placeholder version.
Inspect the received copies
Check the sender, To and copy behavior, subject, greeting, custom fields, links, attachments, and the mail-merge unsubscribe footer. Every recipient receives an attachment added to the same draft, so a shared attachment must be appropriate for every person.
Review desktop and phone displays, including a client other than Gmail if that matters to the audience. Use the layout editor’s device previews as a useful preliminary check, not as a substitute for the received test message.
Approve one final version and sending list
After corrections, test the revised version again where the change could affect delivery or personalization. Confirm that the real list excludes test-only addresses, unintended duplicates, and people who should not receive the campaign.
Check current sending capacity and keep a record of intended recipients. Do not assume an unsuccessful-looking send had no effect: inspect Sent and errors before retrying. Keep the campaign as a draft until the authorized sender approves the exact message and list. This review process does not require sending confidential recipient data to an external testing website.
Browse Gmail & Google Account help
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.