Link tracking

Link tracking adds campaign labels to eligible links in your marketing emails. When a customer follows a tagged product link, those labels travel to the destination URL. Your website's analytics can use them to identify campaign traffic.

For a coffee announcement, you might use spring-launch as the campaign, maxclicks as the source and email as the medium. Set the workspace's source and medium once, then choose the campaign on each email. Verify the final URL and your website's analytics before interpreting the result as attributed traffic or revenue.

Separate URL tagging from email click metrics

Evidence	What it describes	Where to inspect it
`utm_campaign`, `utm_source`, `utm_medium`	Labels included in a destination URL.	The prepared email's link and the destination URL.
Email click activity	Click events reported by the email provider and recorded against an email.	The email's Activity and campaign or workspace metrics.
Website visits or purchases	What your website analytics and business data record after the destination is reached.	Your analytics and order or product system.

The workspace's UTM switch does not turn provider click reporting on or off. An email can have click activity without these added labels. A tagged link does not prove a visit was recorded, a purchase occurred, or the campaign caused that purchase. See email results for the distinction between delivery, clicks and your customer outcome.

Configure workspace tagging

Open Settings → Link Tracking. The setting applies across the space, rather than only to the email currently open. The screen is reachable by space members, but saving workspace tagging changes requires admin permission. Editing the email's campaign requires write permission.

Enable marketing-email tagging
Turn on Tag links in marketing emails. The switch is off by default. Source and Medium appear when it is enabled.
Choose source and medium
Enter the values your reporting convention needs, such as maxclicks for Source and email for Medium. These become utm_source and utm_medium. Empty fields remain unset; the displayed placeholders are not saved default values.
Check the saved settings
Edits save automatically. Wait for the saving status to settle and inspect any error in the page header. The example under A link in your next campaign illustrates the current fields; it is not evidence that an email was sent or that analytics received a visit.

Source and medium are optional trimmed strings, and neither field automatically becomes the placeholder when left blank. Use consistent explicit values across campaigns when your reporting needs a common source and channel. Turning the switch off prevents automatic tagging on subsequent preparation; it does not remove tags already authored into your links or change delivered emails.

Set the campaign on an email

In the email composer's setup controls, find Link tracking and enter Campaign. This value becomes utm_campaign. The field appears when workspace tagging is enabled and the email uses Marketing sending mode.

Leave Campaign empty to derive a name from the owning broadcast, reusable template or workflow step. A workflow uses the Send Email step's label, falling back to the workflow name. The fallback is lowercased, accents are normalized, and punctuation or spaces become hyphens: Spring coffee launch becomes spring-coffee-launch.

An explicit campaign value is used as the saved text rather than converted into that owner-name slug. URL encoding handles characters that need escaping. Use a stable value when later title edits should not change the campaign label.

An empty campaign and an unnamed owner can leave utm_campaign absent. A name that produces no letters or digits also has no fallback. Set Campaign explicitly when that label is required for your reporting.

The composer shows the workspace source and medium and offers Change them to open workspace settings. Those controls change the whole space. Existing email-level source or medium values, when present, take precedence over workspace defaults; the current composer exposes the campaign field rather than separate source and medium editors.

For a workflow email, draft changes take effect after workflow publication. Existing runs keep their published email configuration. See workflow versions. For reusable content and the composer, see templates and the email editor.

Understand which links change

Automatic tagging resolves the campaign, source and medium while preparing the final email. It changes absolute http:// and https:// links in the rendered HTML body. It does not create a website analytics integration.

Link or setting	Result
External absolute HTTP or HTTPS link	Receives each nonempty resolved UTM value.
Existing `utm_campaign`, `utm_source` or `utm_medium`	Replaced only when that key has a nonempty resolved value.
Existing UTM key with no resolved value	Its authored value remains. Blank settings do not remove it.
Other query parameters or a fragment	Preserved, including values such as `variant=espresso` and `#details`.
maxclicks app, API or platform-domain links and their subdomains	Excluded from automatic tagging. This includes maxclicks-managed unsubscribe and preference links.
Relative, malformed, `mailto:` or `tel:` link	Left unchanged.
Transactional email or disabled workspace switch	No automatic UTM tagging. Existing authored URL parameters remain.

The link's label does not determine exclusion. An external preference or unsubscribe URL is still an eligible HTTP(S) link if its host is outside the platform exclusions. Inspect any custom preference links rather than assuming text such as “unsubscribe” makes the link exempt.

Automatic tagging happens after rendering. A personalized or Liquid-generated destination must resolve into a valid absolute HTTP(S) link to receive the tags. The final plain-text body is generated from the tagged HTML, including its link destinations.

Inspect an example URL

With tagging enabled, Campaign set to spring-launch, Source set to maxclicks, and Medium set to email, this authored link:

https://shop.example/products/coffee?variant=espresso#details

becomes:

https://shop.example/products/coffee?variant=espresso&utm_campaign=spring-launch&utm_source=maxclicks&utm_medium=email#details

If the original already contained utm_source=old, the nonempty resolved source replaces it with maxclicks. An unrelated utm_content=button remains. If no source is resolved, the old authored source remains instead. Query-parameter order or URL encoding can change without changing those values.

Verify a prepared marketing email

An editor preview checks the content and destinations. Send test sends the supplied preview HTML as a transactional test; it does not run automatic marketing UTM resolution. A test email can retain tags you authored, but it is not proof of the production tagging path.

Use a narrowly scoped marketing send to contacts you control when you need to check final automatic tagging. Sending still requires a verified sender, eligible recipients and available sending allowance. Follow sending your first email.

Check the configuration
Confirm the workspace switch, explicit source and medium, email sending mode, and campaign value or owner name. Inspect a representative rendered link, including any existing query parameters.
Inspect the actual email
Open the prepared or sent email's details and inspect its destination link. Confirm the expected UTM values and preserved product parameters. Provider tracking can wrap the link; inspect the destination reached as well.
Check the destination evidence
Follow the intended link and inspect the landing URL. Check whether your website analytics receives the expected labels. Read email Activity separately when checking the provider's click event.

Broadcast preparation captures the resolved UTM settings in the send revision. A later workspace setting change does not rewrite that captured revision or delivered content. Workflow and reusable-template sends retain their prepared artifact for safe recovery. Verify the actual email rather than assuming today's settings describe every earlier message.

Find a missing or unexpected label

What you find	What to inspect
Workspace settings failed to save	Admin permission and the page's saving error. Being able to open the page does not grant permission to update it.
No added tags	Workspace switch, sending mode, absolute HTTP(S) destination and excluded platform hosts. Check whether you inspected a preview or transactional test.
No campaign label	Explicit Campaign, owning item's name and whether its fallback produces a nonempty slug.
An old source or medium remains	A blank resolved value preserves an authored key. Check existing email-level values before workspace defaults.
A recent change is absent from an email	Its captured broadcast revision, published workflow version or already prepared artifact.
Tags reach the page but reporting differs	The destination's redirects and analytics setup, plus the exact labels received. URL tagging alone does not establish successful attribution.

Correct the relevant saved setting or authored URL, then inspect newly prepared content. Changing settings does not edit an email already delivered. Do not resend a customer campaign solely to repair reporting labels; use the existing email and destination evidence when assessing what happened.

Email editor: content, sending mode and campaign controls.
Broadcasts: audience, preparation and delivery state.
Templates: reusable email configuration and sends.
Workflow management: published versions and existing runs.
Email results: provider activity and business-outcome limits.