Skip to main content
UTM parameters are appended to the destination URL so Google Analytics, Adobe, or whatever you use can attribute a visit to a campaign. They are read by your analytics tool, not by Dashlink — Dashlink tracks the click regardless.

Adding them

Set utm_analytics_enabled=true, then supply the parameters:
A visitor is sent to:
Without utm_analytics_enabled=true the UTM fields are stored but not appended. This is the most common reason UTM tagging appears not to work.

The parameters

utm_content is what lets you A/B test: same campaign, different value per variant.

Consistency is the whole game

UTM values are matched as exact strings. Email, email and e-mail are three different mediums in your reports, and nothing warns you. Agree a convention and enforce it in code:
  • Lowercase everything
  • Hyphens, not spaces or underscores
  • A fixed vocabulary for utm_medium

Templates instead of convention-by-memory

A UTM template saves a set of values so everyone tags the same way without remembering the rules:
A template is a starting point copied at creation time. Editing it later does not rewrite links already made from it.

Reading the results back

Dashlink records the UTM values on each click, so you can break analytics down by them without leaving the API:
metric also accepts utm_medium, utm_campaign, utm_term, utm_content and utm_id.