Study first
Review the ideas behind the questions
Review the tracking setup that has to exist before email results can be trusted. Focus on UTM naming, click tracking, third-party tracking, and revenue-data prerequisites.
Name campaign links consistently
UTM values should identify the campaign without splitting one effort into several rows because of naming drift.
- Campaign URLs should include source, medium, and campaign parameters for email traffic.
- Parameter values are case sensitive, so naming changes can split reporting.
- Different content values can distinguish two call-to-action links in the same email.
In Practice
Lowercase is a reporting control
If one sender uses Email and another uses email, the campaign can fragment in Analytics even when the destination page is the same.
Content values belong to link differences
Use the content parameter when the business question is which link or creative inside one message received the click.
Common mistakes
Changing capitalization between emails and treating the report split as a real audience change.
Normalize parameter names before launch because Analytics treats different capitalization as different values.
Q&A
Which three values should be checked on a basic email campaign URL?
Check the source, medium, and campaign values before the email is sent.
Why can two names for the same campaign be a problem?
Analytics can treat different parameter values as separate rows, especially when capitalization or spelling changes.
Separate built-in clicks from outside analytics
Mailchimp click reports and Google Analytics tracking are different layers. Turning one setting on or off does not automatically prove the other layer is ready.
- Mailchimp click tracking records tracked link clicks in the email report when click tracking is enabled.
- Third-party tracking options are separate from Mailchimp open and click tracking settings.
- Google Analytics data for marketing emails and automation flows with GA4 enabled is viewed in the Google Analytics account.
In Practice
One checkbox is not all tracking
If built-in click tracking is off, still review any enabled third-party tracking choices separately.
GA4 means leaving Mailchimp for those stats
When GA4 tracking is enabled on Mailchimp emails, the analyst should expect those statistics in Google Analytics, not inside the Mailchimp report.
Common mistakes
Disabling Mailchimp click tracking and assuming Google Analytics tracking was also disabled.
Review third-party tracking options separately because they are independent of Mailchimp open and click tracking.
Q&A
Where should GA4 email tracking statistics be reviewed?
Review them in the Google Analytics account when GA4 tracking is enabled for the email or automation flow.
Know what revenue and imports require
Revenue and imported campaign cost data depend on upstream setup. A report cannot show data that was never connected, tracked, or matched.
- Mailchimp revenue reporting requires a connected e-commerce store for e-commerce data in reports and dashboards.
- Campaign data import combines external campaign data with revenue and events already measured in Google Analytics.
- Imported campaign source, medium, campaign, and date values must exactly match the values users logged.
In Practice
Revenue needs store data
If no store is connected, do not treat a missing campaign revenue report as proof the email failed to sell.
Imports need matching keys
Before importing campaign data, verify that the source, medium, campaign, and date values match what Analytics collected from links.
Common mistakes
Uploading campaign cost rows with slightly different campaign names than the email links used.
Match imported campaign names and other key values exactly to the values collected from the email URLs.
Q&A
What should be checked before judging missing email revenue in Mailchimp?
Check whether the e-commerce store is connected and whether the report surface can receive revenue data.
What must match for Google Analytics campaign data import?
The imported source, medium, campaign, and date values must match the values Analytics collected from users.