Mailchimp campaign history, next to the traffic it drove.
Mailchimp lists every campaign you’ve sent — but the sends live in Mailchimp, away from the traffic and sales they move. CoNote will put each send on one shared timeline, beside the spike it caused and the deploys from the same day.
Mailchimppublished a changeSent “Spring Sale” to 24,500 subscribers
Mailchimp· 09:00
Traffic spiked 4× — checkout held up
Uptime· 09:06
Finding your history
Your Mailchimp campaign history: today, and once CoNote is live
The manual way · inside Mailchimp
Where to find it today
It’s all there — in its own dashboard:
- 1
Sign in to Mailchimp
Open your account — sends are listed per audience, so multiple audiences mean multiple places to look.
- 2
Open the Campaigns view
Every sent campaign is listed with its name, the audience, and the date and time it went out.
- 3
Open a report
Each send has a report with opens, clicks, and revenue if e-commerce tracking is on — but it’s about that one send.
- 4
Check audience milestones
The Audience dashboard shows list growth, but milestones aren’t lined up against anything else.
- 5
Cross-reference the traffic by hand
Nothing lines a send up against your site traffic, sales, or deploys, so you switch to those tools and match timestamps yourself.
The CoNote way · coming soon
Where you’ll find it once it’s live
Connect Mailchimp once. After that it’ll be seconds:
- 1
Open your CoNote timeline
Every send will be waiting — no Mailchimp login, no audience-by-audience hopping, readable by anyone.
- 2
Jump to the moment traffic spiked
Scan the spike; the send that drove it will be stamped right there.
- 3
See it beside everything else
The send will sit next to that day’s deploys, other campaigns, and incidents — the cause is obvious.
Sound familiar?
Mailchimp knows the send — not its effect.
Sara09:30
Mia09:34
Sara09:37
Mia09:41
The send is in one tool, the spike in another.
It answers “what did we email, and how did it perform?” — never the question you actually have: “did this send move the traffic and sales I’m looking at?”
- Sends live in Mailchimp, traffic and sales live elsewhere
- Per audience — multiple lists mean multiple places to look
- Locked in its own dashboard, away from the rest of the company
- Never lined up against the deploy or other campaign from the same day
Once Mailchimp is connected, the send will already be on the timeline — “Sent ‘Spring Sale’ to 24,500 subscribers” at 09:00 — right beside the traffic spike, readable by anyone, on one page.
How it works
Connect once. Then it’ll log itself.
- 01
Authorize with Mailchimp
A two-click authorization — no code, no engineering sprint. CoNote will read your send activity, nothing else.
- 02
Every send logs itself
From then on, each campaign send lands on the timeline with its name and audience size — “Sent ‘Spring Sale’ to 24,500 subscribers” — the moment it goes out.
- 03
Read it in context
The send sits beside that day’s traffic spike, other campaigns, and deploys. When a number moves, you scan one page instead of three tools.
What lands on your timeline
- Every campaign send — its name and audience
- The number of subscribers it reached
- The moment it went out, to the minute
In your week
What teams will use it for.
The mystery traffic spike
Traffic jumps at 09:00. The “Spring Sale” send at 09:00 is right there on the timeline — the cause, without logging into Mailchimp.
Email, ads, or deploy — which moved sales?
When all three happened, they’re on one timeline in order, so you stop guessing which drove the bump.
Tie unsubscribes to the send that caused them
A spike in unsubscribes lines up with the send right before it — instead of opening every report.
One send log across every audience
Several audiences, one timeline. Every send lands in the same place, in order, the whole team can read.
Side by side
Native reports vs. your logbook.
See campaign sends
Mailchimp reports
CoNote
Lined up against traffic, sales, deploys
Mailchimp reports
CoNote
One feed across every audience
Mailchimp reports
CoNote
Readable by the whole company
Mailchimp reports
CoNote
Beside the spike it caused
Mailchimp reports
CoNote
Setup
Mailchimp reports
CoNote
On the timeline
The send in context.
A send on its own is an open rate. Next to the traffic spike it caused the same morning, it’s an explanation.
Tuesday, June 9
Sent “Spring Sale” to 24,500 subscribers
Mailchimp· 09:00
Traffic spiked 4× — checkout held up
Uptime· 09:06
Deployed sale banner (main → 5d9c2e1)
GitHub· 08:30
Questions
Mailchimp campaign tracking, answered.
Open the Campaigns view — every sent campaign is listed with its name, audience, and the date and time it went out, and each has a report with opens, clicks, and revenue if e-commerce tracking is on. Sends are organised per audience.
Not yet — it’s coming soon. You can start your CoNote logbook now and connect the tools that are already live; we’ll switch Mailchimp on automatically the day it ships.
A standard two-click authorization with read-only access to your send activity. It will never send emails or change your audiences.
Each campaign send as a plain-language entry — its name, the audience, and how many subscribers it reached — with the time it went out. CoNote logs the send, not your subscriber data.
The timeline focuses on the event — that a send went out, when, and to how many — so you can correlate it with traffic and sales. Detailed open and click stats stay in Mailchimp’s reports.
Mailchimp’s reports live in its own dashboard, per audience, away from your traffic and sales. CoNote will put your sends on a shared timeline right beside the spike they caused and the deploys from the same day.
Only your team. Every entry is scoped to your team, and connecting Mailchimp won’t expose your account to anyone outside it.
Keep digging
Track the rest of your stack.
Open the logbook.
Free plan, no card. The next time someone asks “what changed?”, the answer is one search away.
Start your logbook