If FormMerge says the mail merge was sent but Gmail recipients did not receive it, split the problem into two questions: did the message leave the sheet workflow correctly, and did the recipient mailbox accept or hide it?
This flow keeps you from guessing. Start with the recipient column, then confirm the test send, then inspect the sheet status and the Gmail path.
The row may contain several address-like fields. Make sure FormMerge is reading the exact recipient column you intended.
Shared inboxes, school domains, and company mail systems often filter automated messages more aggressively than a personal Gmail account.
Delivery can still be delayed by filters or downstream mail routing even when the merge run completed.
A successful batch summary is not the same as proving the exact recipient, body, and sender behavior with one test row first.
FormMerge is built for practical operational email, with preflight checks, test sends, and row-level status so you can verify the mail path before real recipients depend on it.
Check the recipient column, subject, body, and merge tags before the batch runs.
Send one row to your own inbox and confirm the message arrived where expected.
Compare the send report against the row that should have gone out.
Review sending limits before a larger operational batch.
Check whether the email hit spam, a quarantine folder, or a filtered shared inbox before changing the template.
Yes. A test send catches recipient-column mistakes and merge-tag problems before any real batch leaves the account.
Review Gmail limits, then inspect the recipient mailbox filters and the row-level send report.
No. It is a spreadsheet-based operational email tool, not a newsletter or marketing automation platform.
Install FormMerge when the spreadsheet already contains the recipient list and you want a test-first path for row-based email delivery.