Why do Mailchimp and GA4 report different email revenue?

Because they measure differently, not because one is broken. Mailchimp attributes orders to a send within its own conversion window and model, while GA4 attributes sessions under yours — different windows, different last-touch rules, different handling of a customer who opens on mobile and buys on desktop. The fix is not to reconcile them to the digit but to declare one source as the reporting truth per client and note the other as directional.

How should agencies tag Mailchimp campaigns?

With one convention applied consistently across every channel, set in the agency's standard rather than per-send. The common failure is letting Mailchimp's auto-tagging run alongside a manual convention, which splits the email channel across several source/medium rows in GA4. Pick one, disable the other, and record which on the client's tracking map so the next person on the account inherits the decision.

Does Phloz send email or manage lists?

No — Phloz is not an email marketing tool and does not send client campaigns. It models Mailchimp as part of the client's tracking infrastructure: which audience, what it is connected to, which convention its links follow, and whether the setup is still healthy. Client campaign email stays in Mailchimp; Phloz's own messaging is agency-to-client communication, which is a different thing entirely.

Mailchimp integration for digital marketing agencies

Email is usually a client's highest-ROI channel and the one most often mis-measured. Mailchimp campaigns carry their own link tagging, its audiences sync outward to ad platforms for retargeting and lookalikes, and its e-commerce connector claims revenue that a client's analytics may attribute differently — three separate places where the numbers can diverge from what the agency reports. When an agency runs email alongside paid and organic, an untagged campaign or a silently-stopped audience sync does not just lose a channel report; it distorts every other channel it leaks into.

How Phloz models Mailchimp

Every Mailchimp concept that matters for digital marketing agency operations is a typed object in the tracking map. Health state per node, audit cadence, and graph relationships to every other tracking-system node it touches — so a broken tag or misconfigured property is findable in seconds across your full book of clients.

Mailchimp as a typed email-platform node: audience identity, connected store/site, the account owner, and health status
Edges to the GA4 property that measures its traffic and to any ad platform receiving its synced audiences, so the retargeting dependency is visible rather than assumed
The client's campaign UTM convention recorded on the node — the reference the team tags against, so "which utm_source do we use for newsletters?" has one documented answer
Verification cadence plus cross-client view: which clients run Mailchimp, how each is wired, and which audience syncs are overdue for a check

Common Mailchimp configuration gotchas

The configuration mistakes agencies most often make with Mailchimp, surfaced here as a checklist agencies can run at every client onboarding. Honest, useful, not gated behind a sales pitch — these are real and you should audit for them regardless of whether you use Phloz.

Mailchimp's auto-tagging colliding with the agency's convention: Mailchimp can append its own UTM parameters, which frequently disagree with the naming standard the agency uses everywhere else (utm_source=Mailchimp vs newsletter, campaign names that differ per send). GA4 then splits one channel across several rows. Pick one convention, disable the other, and record the decision on the node.
Audience sync stopping silently after a permission change: when a connected ad account's token expires or a permission is revoked, the sync stops without an obvious failure, so retargeting audiences quietly go stale and shrink for weeks. Treat the sync as a monitored dependency with a re-check date, not a set-and-forget connection.
Revenue double-counting between Mailchimp's e-commerce reporting and the client's analytics: Mailchimp attributes orders with its own window and model, so its revenue number will not match GA4 or the ad platforms. Decide which source is the reporting truth for the client before the first report, and say so in the report itself.

At launch (V1)

Mailchimp appears as a typed email-platform node: audience/list identity, the connected store or site, tagged campaign URLs, and health status — linked to the GA4 property and ad platforms that receive its traffic and audiences.

Coming (V2)

Pull campaign UTM conventions and audience-sync status automatically, so a broken list sync or an untagged send is flagged by the audit rather than discovered in a monthly report.

Why we built the integration this way

Most agency CRMs treat third-party tools as text fields: "GA4 Property ID" goes in a custom column on the client record. That works at one or two clients and breaks at five. With every Mailchimpobject as a typed tracking node, the agency can answer questions like "which clients have a misconfigured Mailchimpsetup?" or "which Mailchimpconfigurations changed last quarter?" from a single graph query.

The V1 surface is intentionally manual — agencies enter the configuration at onboarding rather than auto-importing. This forces explicit verification at the exact moment the agency takes over the client's tracking, catching most of the commonGotchas listed above before they become production issues. V2 will add API-based sync where the underlying platform supports it; we won't add sync where the underlying API doesn't expose the right data.

When to use this in your client onboarding flow

The standard pattern for digital marketing agencies running Phloz: at every new client onboarding (see the client onboarding audit use case), spend 30 minutes documenting the client's Mailchimpconfiguration as Phloz nodes — pixel IDs, tracking-code installations, conversion-action setup, the relationships to other systems. Verify each one fires by triggering a test event. Set the "verified at" timestamp on each node. Schedule a quarterly verification task on the agency engineer who owns tracking.

The 30 minutes at onboarding catches 90 percent of the tracking issues that would otherwise surface during the first month of campaign optimisation — when finding them would mean a refund conversation. See the broader tracking infrastructure map use case for the agency-wide pattern.

Frequently asked questions

The three questions agencies ask most often about Phloz's Mailchimp integration. Honest answers — same data we'd give a friend evaluating the integration.

Why do Mailchimp and GA4 report different email revenue?: Because they measure differently, not because one is broken. Mailchimp attributes orders to a send within its own conversion window and model, while GA4 attributes sessions under yours — different windows, different last-touch rules, different handling of a customer who opens on mobile and buys on desktop. The fix is not to reconcile them to the digit but to declare one source as the reporting truth per client and note the other as directional.
How should agencies tag Mailchimp campaigns?: With one convention applied consistently across every channel, set in the agency's standard rather than per-send. The common failure is letting Mailchimp's auto-tagging run alongside a manual convention, which splits the email channel across several source/medium rows in GA4. Pick one, disable the other, and record which on the client's tracking map so the next person on the account inherits the decision.
Does Phloz send email or manage lists?: No — Phloz is not an email marketing tool and does not send client campaigns. It models Mailchimp as part of the client's tracking infrastructure: which audience, what it is connected to, which convention its links follow, and whether the setup is still healthy. Client campaign email stays in Mailchimp; Phloz's own messaging is agency-to-client communication, which is a different thing entirely.

Start your free trial

14 days free · No credit card · Starter tier free forever