# UTM tags for newsletters

Updated 27 October 2026 · https://kanavoi.com/en/guides/utm-newsletters

Newsletter traffic often shows up in GA4's Direct channel, because email clients do not say where the visitor came from. With UTM tags, you can see the results of every send and even every link.

## Why tag your newsletter links

When a visitor clicks a link in an email client or a phone's mail app, the browser usually gets no information about where the link was opened. GA4 then records the visit in Direct, together with typed-in addresses and bookmarks.

Tagged links show you how much traffic and sales your newsletter brings, which send worked best and which link was clicked.

## The right values

| Parameter | Value | Note |
|---|---|---|
| `utm_source` | `newsletter` | Or the list name, for example `customer_newsletter` |
| `utm_medium` | `email` | Decides the channel, always the same |
| `utm_campaign` | `newsletter_2026_10` | One value for each send |
| `utm_content` | `hero_image` | Where the link sits in the message |

The medium `email` puts the traffic in the Email channel:

GA4 channel when the source is newsletter and the medium email: **Email**. The source or medium is email.

```
https://shop.example.com/fall-sale?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_2026_10&utm_content=hero_image
```

The hero image link in the October newsletter.

## The most common mistake: medium newsletter

GA4 only recognizes email from the values `email`, `e-mail`, `e_mail` and `e mail`. A medium like `newsletter` (or the Finnish `uutiskirje`) matches no rule, and the traffic lands in Unassigned:

GA4 channel when the source is newsletter and the medium newsletter: **Unassigned**. None of the rules of GA4's default channel group match, so the traffic shows up in reports without a channel.

The source can be anything, but the medium must be `email`. If your reports already have traffic like this, the guide [Why GA4 shows traffic as Unassigned](https://kanavoi.com/en/guides/ga4-unassigned#channel-group) explains how to sort the old data correctly.

## Campaign and content

**The campaign identifies the send.** Give every send its own campaign, for example `newsletter_2026_10`, or by topic, `fall_sale_2026`. When the same offer also runs on social and in ads, use the same campaign name everywhere. Then you see the campaign's total result and the channels within it.

**The content identifies the link.** If a message has several links to the same page, `utm_content` tells them apart:

```
...&utm_content=hero_image
...&utm_content=button
...&utm_content=footer_text
```

This shows you whether people click the image or the button, and you can adjust your next message accordingly.

## Automatic tags in your email service

Many email services have a setting that adds UTM tags to the links in a message automatically. It is handy, but check which values the service uses:

- The medium is usually `email`, which is correct.
- The source and campaign may be the list or message name as it is, with capital letters and spaces.

Choose one approach. Either adjust the service's settings to match your naming rules, or turn off automatic tagging and add the tags yourself.

> **Note:** **If a link already has its own tags**, the service may leave them as they are or replace them. Check your service's documentation to see which happens before you use both.

## Other emails

The same rules work for all email: order confirmations, reminders and links in email signatures. The medium is always `email`, and the source tells the type of message:

GA4 channel when the source is signature and the medium email: **Email**. The source or medium is email.

## Checklist

- The medium is `email` in all emails.
- Every send has its own campaign.
- Links in the same message are told apart with content.
- Your email service's automatic tagging is either adjusted or turned off.

[Try it yourself: Open the generator with this guide's example values.](https://kanavoi.com/en/?url=shop.example.com/fall-sale&source=newsletter&medium=email&campaign=newsletter_2026_10&content=hero_image#try)
