Connect Mailchimp to Google Sheets
Pull campaign performance, audience summaries and subscriber lists out of Mailchimp on a schedule. Opens, clicks, bounces and unsubscribes land as flat columns, ready to chart or join against revenue.
What you can pull from Mailchimp
Mailchimp exposes 3 objects you can pull, each as its own job. Every run pulls the records into a flat table, so nested fields arrive as ordinary columns that Google Sheets can sort, filter and total without further work.
Campaign reports
One row per sent campaign, with the opens, clicks, bounces and forwards blocks flattened into columns.
| Column | Type | Notes |
|---|---|---|
| id | string | The stable upsert key |
| campaign_title | string | — |
| subject_line | string | — |
| send_time | datetime | — |
| emails_sent | integer | — |
| open_rate | float | A fraction, not a percentage: 42% arrives as 0.42 |
| unique_opens | integer | — |
| clicks_total | integer | — |
| hard_bounces | integer | — |
| soft_bounces | integer | — |
| unsubscribed | integer | — |
Audience summaries
One row per audience - size, growth and engagement. Omit list_id for every audience at once.
Subscribers
Members of one audience, filtered by status. list_id is required.
Options you can set
- resource
- Which Mailchimp data to pull — defaults to
campaign_reports - since_send_time
- Only campaigns sent at or after this
- member_status
- subscribed, unsubscribed, cleaned, pending, transactional or all — defaults to
subscribed - max_members
- Cap on subscribers per run, up to 50,000 — defaults to
5000
How it lands in Google Sheets
Google Sheets accepts append and overwrite writes. Overwrite replaces the target range, which suits a snapshot; append adds rows underneath, which suits a log you are accumulating. There is no upsert here, so rows are added or replaced rather than merged.
- Append adds rows below existing content; overwrite replaces the target range.
- No upsert: a spreadsheet has no primary key, so there is nothing to merge on. Use Airtable or Postgres if rows must be updated in place.
- Google caps a spreadsheet at 10 million cells across all tabs. Filter before writing rather than after.
Authentication
You connect Mailchimp once through OAuth and the credential is stored server-side, never pasted into a cell or a formula. Only the scopes the connector actually calls are requested — the table below lists each one and what it is for.
Keeping runs incremental
Yes. since_send_time for campaigns, since_last_changed for subscribers, so a run fetches only what moved.
Because Google Sheets has no upsert, decide what a re-run should mean before you schedule it. Overwrite keeps a current snapshot; append accumulates history and will grow without bound.
Limits and pacing
These are the provider-side ceilings that shape a schedule, not ours. Knowing them up front is the difference between a job that runs quietly every morning and one that starts failing the week your data grows.
| Limit | Value | Applies to |
|---|---|---|
| Pages per run A safety net; each resource also stops on a short page. | 200 | Mailchimp |
Common gotchas
Most of what goes wrong with a scheduled sync is not a bug — it is a detail of how one side behaves that nobody wrote down. These are the ones that come up for this pair.
open_rate is a fraction
A 42% open rate arrives as 0.42. Store it as a percent field and let the destination format it, or multiply by 100 - but not both, or a client dashboard ends up reporting 4,200%.
Campaign stats keep moving after send
Opens and clicks trickle in for roughly 72 hours. Upsert on the campaign id so the row updates, rather than appending a new snapshot every run.
Some report blocks are deliberately excluded
industry_stats, list_stats, ab_split, ecommerce and delivery_status are outside the reporting scope, and timeseries/timewarp are lists of dicts that would break a tabular shape outright.
An open-ended range beats a padded one
Writing to A2:D is better than A2:D1000 for appends: the padded form reserves rows you may not need and makes the append boundary ambiguous.
Set it up in four steps
- 1
Connect Mailchimp
Connect your Mailchimp account once. Mailchimp's API is per-account - each sits on its own datacenter endpoint - and the connection resolves that for you.
- 2
Connect Google Sheets
Connect your Google account once. Paste a spreadsheet URL or ID.
- 3
Shape the data
Select the columns you want, filter rows, cast types and add computed fields. Everything else is dropped before it reaches the destination.
- 4
Schedule it
Run once, or on a cron. Every run refreshes Google Sheets with the latest Mailchimp data.
Do I need an add-on or extension for this?
No. The job runs server-side and writes into Google Sheets through its API, so there is nothing installed in the spreadsheet itself. It keeps running when nobody has the file open, and a copy of the file does not need anything installed to work.
How often does the data refresh?
On whatever schedule you set with a cron expression — hourly, daily, or a specific time on specific days. Each run pulls the latest from Mailchimp.
Do I need to write any code?
No. You connect both sides, map the fields in a wizard and set a schedule. Computed fields accept small expressions — abs, round, min, max, len — but there is nothing to host or maintain.
Why is my open rate showing as 0.42?
Mailchimp returns rates as fractions. Format the destination column as a percent, or multiply by 100 - but not both, or the number comes out as 4,200%.
Can I pull more than one audience at once?
For audience summaries, yes - omit the list ID and you get one row per audience. Subscriber lists are per-audience and need a list ID.
Do I have to give access to my whole Google Drive?
No. Only the spreadsheets scope is requested. The Drive scope that most spreadsheet tools ask for is a restricted scope granting read access to every file you own; it is deliberately not requested here, which is why you paste a spreadsheet URL rather than browsing Drive.
Will this keep working if I copy the sheet?
The job writes to a specific spreadsheet ID, so a copy will not receive data until you point a job at it. Nothing is installed in the file itself, though, so copying never breaks the original.
Is the Mailchimp connector free to use?
You can connect Mailchimp and start syncing on the free plan.
Other sources into Google Sheets
Related reading
Export Stripe data to Google Sheets
Stripe's dashboard exports are manual and stale the moment you download them. Here is how to keep customers, invoices and charges fresh in a sheet instead.
Import a CSV from a URL into Airtable
Point a job at a CSV link and it re-reads it on your schedule — no download, no manual import. Here is the setup, and the field-type trap to avoid first.
Get data into Google Sheets without an add-on
Every major Sheets data tool is an add-on you install, authorise and keep updated inside the spreadsheet. Here is how to schedule the same imports without one.