Mailchimp bills per audience, so anyone on two or more audiences costs you two or more times. This scans every audience and finds the duplicates, so you can archive the extras and stop over-paying.
⚷ your API key is used in-memory for this run and never reaches our servers · save it in Settings to skip re-enteringPaste an admin API key. Used only for this run and never stored on our servers. Save it in Settings if you would rather not re-enter it every run.
Find it under Account & billing → Extras → API keys.
Each duplicate below is being billed once per audience it sits on.
One CSV of every duplicated email and which audiences it's on, so you know exactly what to archive.
Read-only. We only read your audiences to find duplicates, and never change anything. Not affiliated with Mailchimp or Intuit.
Mailchimp bills per audience, so a contact on two audiences is billed twice. This scans every audience and finds the duplicates so you can archive the extras and stop over-paying. Read-only.
It runs on your own Mailchimp data, in your browser session, against Mailchimp's official API. There is no middle layer holding your records and there is no migration to anywhere. You run it, you get the result, you carry on with your day.
It is a CSV, which is the point. Mailchimp will happily show you the numbers on a screen you cannot do anything with. This gives you the file, and the file goes wherever you need it.
The column names stay the same run to run, so if you build a Power BI report or a Sheets formula on top of it, re-running next month will not break what you built.
It will not touch anything you did not ask it to. It does not store your API key, it does not keep a copy of your data, and where an action cannot be reversed you get told that before you press the button, not after.
No. The key is held in memory for the length of the run and is gone when the tab closes. It is never written to our database and never appears in a log. You can revoke it in Mailchimp the moment you are done and nothing here breaks.
It is a plain CSV, so anything that reads a CSV will read it. Open it in Excel or Google Sheets, pull it into Power BI or Looker Studio, or load it into a warehouse table. The headers are clean and they do not change between runs, so a scheduled refresh will not break on you.
It streams the results as they arrive rather than holding everything in memory, and it respects Mailchimp's rate limits instead of hammering the API. Large accounts take longer, but they finish.
Yes, and you should. Every run starts with a preview of the exact records involved, and a CSV backup you can keep. Nothing is written until you say so.
Read the tool's own note above, because it differs by action. Where a change cannot be undone we say so plainly on the button itself rather than in the small print.
That is the whole question, and we do not have a good answer either. It is a gap that has been open for years, it is on the forums, and it never gets shipped. So we shipped it.