What email UTMs should answer

An email link should let a report answer three questions: which sending program produced the visit, which initiative the message supported, and which link or creative earned the click. It should do that without embedding a recipient email, user ID, or private segment in a URL that can be copied and shared.

Email platforms often have their own click reporting. UTMs complement that reporting by carrying readable campaign context into the destination analytics system. They do not replace provider delivery, open, or unsubscribe metrics.

Use utm_medium=email consistently

The medium should represent the channel, so email is the clearest default for newsletters, lifecycle automation, announcements, and promotional sends. Avoid creating separate mediums such as newsletter, crm, and mail unless an established measurement model intentionally treats them as different channels.

Choose a useful email source

Source should name the sending program, provider, publication, or list—whichever level your team consistently compares. The best choice depends on the reporting question:

  • Publication or program: product_newsletter, customer_lifecycle, or weekly_digest stays meaningful if providers change.
  • Provider: mailchimp or hubspot is useful when vendor-level performance is genuinely compared.
  • List: prospect_list can help when lists are stable, non-sensitive categories with a clear reporting owner.

Do not alternate between these levels unpredictably. If program-level reporting matters, keep the provider in operational data rather than switching utm_source whenever the sending tool changes.

Map campaign and content to the message

utm_campaign
Name the durable initiative, such as 2026_autumn_launch, or a lifecycle program such as onboarding_series. Links across several sends can share a campaign when they support the same initiative.
utm_content
Name the CTA, placement, or creative variant: hero_button, feature_card_2, footer_text_link, or subject_a_hero.
utm_term
Usually omit it. If your team deliberately uses term for a non-sensitive audience category, document that exception and apply it consistently.

For the general field model, see what each UTM parameter means. Use the UTM naming guide to standardize case, separators, and controlled vocabulary.

Email UTM examples

Recurring newsletter

Primary article CTAhttps://example.com/report?utm_source=weekly_digest&utm_medium=email&utm_campaign=2026_week_35&utm_content=primary_article

Product launch email

Hero versus footer CTAhttps://example.com/launch?utm_source=product_newsletter&utm_medium=email&utm_campaign=2026_autumn_launch&utm_content=hero_button

Lifecycle onboarding message

Day-three setup linkhttps://example.com/setup?utm_source=customer_lifecycle&utm_medium=email&utm_campaign=onboarding_series&utm_content=day_3_setup_cta

When several CTAs lead to the same page, keep source, medium, and campaign identical and change only utm_content. The resulting report can compare placements without breaking the campaign into unrelated rows.

Common email UTM mistakes

  • Using the provider as medium. Values such as mailchimp describe a sender, not the email channel.
  • Putting recipient data in UTMs. Email addresses, account IDs, and narrow private segments do not belong in URLs.
  • Giving every send an unrelated campaign. Messages supporting one launch should group under a durable initiative when cross-send performance matters.
  • Reusing one content value for every CTA. If placement analysis matters, name the hero, card, and footer links distinctly.
  • Letting automatic tagging overwrite the convention. Check provider templates and link-rewriting settings before sending.
  • Testing only the original link. Send a real test message and verify the rewritten destination on desktop and mobile.

Pre-send workflow

  1. Assign the shared fields. Confirm one source, email medium, and campaign for the message.
  2. Inventory measurable CTAs. Add content values only where the difference will inform a decision.
  3. Build the URLs. Encode values and preserve existing destination parameters.
  4. Send a test. Click each rewritten link and confirm the landing page, query string, and fragment.
  5. Inspect analytics. Verify a controlled visit before the production audience receives the message.

Build the links before the send

Create one clean URL for each meaningful CTA variant. The free builder keeps existing query parameters, replaces duplicate UTM values, and safely encodes the result.

Build an email UTM link