Gmail mail merge: the four ways people do it, and where each one breaks

2026-10-21 · 9 min · by Yixiu Liu

Add to Chrome - free or get Pro

Mail merge in Gmail sounds trivial until the list passes a few hundred people. Then deliverability, personalisation errors and Gmail's own sending ceiling all arrive at once. This is a map of the four ways people actually do it, and what breaks in each.

1. CC and BCC: fine for fifteen people, never for fifty

Put everyone in BCC, write one message, hit send. It works, and for a team update to a dozen people it is the right answer.

It stops being the right answer the moment the message is commercial:

• Everyone gets identical text. No name, no company, no "you mentioned X".
• Deliverability drops. A large BCC list is one of the loudest bulk signals Gmail reads. There is no unsubscribe link, which is a legal problem in the US under CAN-SPAM and in the EU under GDPR and the ePrivacy Directive.
• No follow-up, no reporting. You cannot tell who opened, who replied, or who should get a second touch.

2. Google Sheets plus Apps Script: free, and honest about being a script

The classic approach: a Sheet with columns for email, first name, company; an Apps Script that calls GmailApp.sendEmail() in a loop. It is free, it is yours, and it personalises properly.

What bites:

• Quotas are per day, per user, and easy to hit. Consumer @gmail.com accounts get roughly 100 recipients per day through Apps Script; Workspace accounts get around 1,500. Google changes these numbers without notice, so check the current quota page before you plan a campaign.
• It runs as you. Close the laptop mid-loop and you have a half-sent campaign with no record of where it stopped.
• No stop-on-reply. A script will happily send follow-up 2 to someone who already answered, which is the fastest way to look like a robot.
• Tracking is up to you. Adding a pixel is ten lines of code; interpreting it correctly is the hard part (see why open rates are inflated).

3. A Gmail add-on: convenient, and priced per seat

Extensions like GMass, Mailmeteor, Mailtrack and Streak add a panel inside Gmail and handle merge, sequences and tracking. This is the category OutReach Pilot belongs to, so treat the rest of this section with the appropriate suspicion.

What actually differs between them is not the feature list — they all merge and track. It is:

4. Send through your own Gmail with a tool that keeps the data local

This is the setup OutReach Pilot implements, and it is worth understanding the mechanism even if you use something else: Gmail accepts authenticated SMTP from an app password. That means a tool can send as you, from your own account, without OAuth review and without a relay — while the recipient list stays on your machine.

The trade-off is explicit: Gmail's ceiling applies (500 recipients/day on @gmail.com, 2,000 on Workspace), and you have to create an app password once. In exchange, deliverability is your own reputation rather than a shared pool's, and the data never leaves.

Before you send: a five-minute checklist

• Verify the addresses. Bad syntax, disposable domains and domains without an MX record should be dropped before the first send, not after the bounce.
• Send to yourself first. Check the merge fields resolve, the link works, and the unsubscribe link renders.
• Put a real physical address and an opt-out in the footer. Required in the US, expected everywhere else.
• Cap the batch. 50-100 a day from a personal mailbox, warmed over a couple of weeks, behaves very differently from 400 in one afternoon.
• Decide the stop condition in advance. If someone replies, stop. If someone clicks the pricing link, stop. Write it down before the sequence exists.

Written by the maker of OutReach Pilot, a Gmail mail merge and sequence tool that runs on your own machine. Numbers quoted are Gmail's published limits as of October 2026 and change without notice.

← All posts · OutReach Pilot · Comparisons