GPT for Google Sheets, Docs AI, Slides, Forms

Apps Script Mail Merge vs Gmail Add-on

Compare Google Apps Script mail merge with a Gmail and Google Sheets add-on: setup time, personalization, attachments, tracking, quotas, and maintenance.

Apps Script Mail Merge vs. a Mail Merge Add-on for Gmail & Google Sheets

You can build a Gmail mail merge with Google Apps Script, or you can use a ready-made add-on. The right choice depends on whether you want to maintain code or simply send personalized campaigns from a Sheet. Mail Merge for Gmail and Google Sheets is for teams that prefer the second path.

Skip the script and send from your Sheet →

The two ways to mail merge from a Sheet

A Google Sheets mail merge usually works in one of two ways:

  1. DIY Apps Script. You write or copy a script that reads rows from a Sheet and sends Gmail messages with placeholders.
  2. Mail merge add-on. You install a tool that connects Gmail and Sheets, fills merge fields from your columns, sends a test, sends campaigns, and tracks results.

Both can be legitimate. The difference is the amount of setup, testing, error handling, and ongoing maintenance you want to own.

Option A: Google Apps Script mail merge

Apps Script is powerful because it runs inside Google’s ecosystem and can read your Sheet, build messages, and call Gmail services. It can be a good fit when:

  • you are comfortable editing JavaScript-like code;
  • the campaign is simple and one-off;
  • you do not need a polished UI for teammates;
  • you are willing to troubleshoot permissions, quotas, triggers, and edge cases;
  • tracking and follow-up logic can stay manual.

The hidden cost is maintenance. A copied script may need changes for HTML templates, attachments, aliases, limits, bounced rows, opt-outs, logging, and errors. If the person who understands the script leaves, the workflow can become fragile.

Option B: a Gmail and Google Sheets mail merge add-on

A focused add-on is built for people who want the campaign shipped without maintaining custom code. With Mail Merge for Gmail and Sheets, the practical workflow is:

  1. Put recipients and personalization fields in Google Sheets, with the four columns Launch creates in A–D: Email, First Name, Last Name and Mail Merge.
  2. Write the email as a Gmail draft.
  3. Use placeholders that match your headers exactly, such as {{First Name}} and {{Company}}. There is no mapping step.
  4. Check the Sheet for empty cells, because an empty cell becomes empty text in the email.
  5. Click Send Test Email: one message goes to you, filled with row 2’s data.
  6. Launch a controlled campaign, then click Refresh Email Status to see opens and clicks.

Run your first no-code mail merge →

Side-by-side comparison

Decision point Apps Script mail merge Mail merge add-on
Setup time Fast if you already know Apps Script; slower if you are copying and debugging Designed for a few-click setup after install
Skills needed Code editing, permissions, testing, quota awareness Spreadsheet and Gmail workflow knowledge
Personalization Flexible, but you build the placeholder logic Built around Sheet columns and merge fields
Attachments Possible, but requires careful scripting and file matching Draft attachments go to everyone; per-recipient Drive files on paid plans
Tracking You usually build or skip tracking Open and click tracking on every plan, shown in the Mail Merge column
Follow-ups Often manual unless scripted Manual: pick unopened rows by status and send a new draft to them
Maintenance You own bugs, API changes, and teammate handoff Product handles the core workflow
Best fit Developers or highly custom internal workflows Operators, marketers, recruiters, sales, and small teams

When the script is genuinely fine

Choose Apps Script when you need a highly custom internal automation, have a technical owner, and can accept script maintenance. It is also reasonable for a very small one-time send where tracking, attachments, follow-ups, and teammate usability are not important.

Do not use a script simply because it looks free. The real cost is the time spent debugging and the risk of sending the wrong message to the wrong list.

When the add-on pays for itself

Use a mail merge add-on when the campaign matters and the sender is not a developer. Common examples include:

  • sales outreach from a qualified Sheet;
  • recruiting messages with role-specific personalization;
  • customer onboarding or updates;
  • event invites and webinar reminders;
  • small-business email marketing from Gmail;
  • campaigns that need test sends, open and click tracking, attachments, or scheduled sends.

A no-code workflow keeps the list, copy, personalization, and status visible to the people responsible for the outcome.

Migrating from a script to an add-on

If you already use an Apps Script mail merge, you can usually migrate by cleaning the Sheet:

  1. Keep one row per recipient.
  2. Put Email, First Name, Last Name and Mail Merge in columns A–D (Launch creates them), then add clear headers such as Company, Role, and Custom Line.
  3. Remove opted-out contacts, or type SKIP in their Mail Merge cell so the add-on leaves them out.
  4. Save your old script as a backup, then test the add-on with a small segment.
  5. Compare the test email with what your script produced before sending the full campaign.

Sending-quality cautions

Whether you use a script or an add-on, send only to consented or clearly relevant contacts, respect Gmail and Workspace limits, include opt-out language where appropriate, test before sending, and avoid misleading personalization. The tool does not replace sender responsibility.

Apps Script vs add-on FAQ

Is Google Apps Script mail merge free?

Apps Script itself is available in Google Workspace, but the workflow is not always cost-free. You still spend time setting up code, debugging, handling quotas, and maintaining the script.

Is a mail merge add-on better than Apps Script?

It depends on the workflow. Apps Script is better for developers who need custom automation. A mail merge add-on is better when you want a ready Gmail and Sheets workflow without maintaining code.

Can Apps Script handle attachments and tracking?

Apps Script can be extended, but attachments, tracking, logging, and follow-ups require additional code and testing. A productized add-on is usually simpler for non-developers.

Do both options still follow Gmail limits?

Yes. Google controls Gmail and Workspace sending limits. Mail Merge for Gmail and Sheets itself runs on Apps Script, so it has the same quota as a script: about 100 recipients a day on @gmail.com, 1,500 on Google Workspace, and 6 minutes per run. Both need clean lists and limit-aware batching.

Choose the path that matches your team

If your team wants a one-off custom automation and has a technical owner, Apps Script can work. If you want to send personalized campaigns from Sheets without owning code, use Mail Merge for Gmail and Sheets.

Try Mail Merge for Gmail and Sheets →