Track UTM Parameters in Amplitude: A Practical Setup Guide
Amplitude shows how people use a product, but it does not reliably record where they came from. Adding UTM parameters and channel data lets you break signups, activation, retention and revenue down by campaign instead of guessing which marketing work produced valuable users.
Why origin data changes the diagnosis
Channel is a useful proxy for intent. Someone who searched for a solution is usually closer to the problem than someone who clicked an ad while browsing socially, even if both complete the same signup form and receive the same onboarding emails. In the captured example, Organic Search visitors reached activation at nearly twice the rate of Paid Social visitors. Without origin data, that gap can look like an onboarding failure and lead a team to redesign flows when the real issue is signup quality.
Pre-flight checklist
Before installing anything, check the full chain: every paid and bespoke campaign carries consistent UTM values; the attribution snippet loads on the site; the first-touch data survives navigation to a different signup page; the data is submitted with the signup event; and Amplitude reports can group by channel, campaign and landing page. If any link is missing, reports will understate or misattribute results.
Four steps to get attribution data into Amplitude
Add UTM values to search, social and bespoke campaigns so origin can be identified. Install the attribution snippet in the site header through the CMS settings or a tag manager, following the provider's instructions for your platform. On each visit the snippet examines device, referrer and UTM data, assigns a channel such as Paid Search or Organic Social, and stores that result in a browser cookie. Storing it matters because the landing page and signup page are often different; without persistence, parameters present on arrival are lost by the time a form is completed.
Pass the data on signup, then report by channel
Choose the handoff that matches your signup flow. Hidden form fields work when users submit a form: the stored values travel with name, email and other submitted details. A small script that reads the cookie is needed when social login buttons let users sign up without a form. After either handoff, build Amplitude reports that split signups, activated users, customers and retention by channel and campaign, and add landing page and landing page category to see which site sections and individual pages drive valuable outcomes.
What structured attribution adds beyond raw UTMs
Raw UTM capture alone misses visitors who arrive without parameters, including Organic Social, Direct and Referral traffic. Channel grouping also solves a reporting problem: raw referring domains can split Organic Search across dozens of Google domains, making one channel look like many. A structured channel field gives one comparable line per channel. Landing page capture adds a second dimension, so content performance can be judged on signups and customers rather than visits alone.
Try it on your own site
Before trusting campaign reports for budget or product decisions, run a test campaign through the full chain: a tagged landing page, navigation to a separate signup page, a completed signup, and a report grouped by channel and campaign. Confirm that the expected channel, campaign and landing page values appear on the resulting user record. If your plan includes a trial period, check the current terms on the signup page rather than assuming a length.
| Signup flow | Recommended handoff | Why it fits |
|---|---|---|
| Standard form signup | Hidden fields submitted with the form | Attribution values travel with the submitted user details. |
| Social login signup | Script reads stored cookie data and passes it to Amplitude | No form exists to carry hidden fields. |
| Multi-page journey | Cookie persistence from first landing page | Parameters survive navigation to a separate signup page. |
Choose based on how users actually sign up; social-login flows bypass forms.
Frequently asked questions
Does Amplitude capture UTM parameters automatically?
No. Product analytics records behaviour after arrival, but campaign origin is not reliably captured by default. Without UTM and channel data, you cannot segment signups, activation, retention or revenue by the campaign that brought each user.
How should stored attribution data be passed to Amplitude?
Use hidden form fields when signup requires a form, because the stored attribution data can be submitted with the user's details. Also read the stored data with a small script when signup happens through social login buttons that bypass a form.
Why group traffic into channels instead of using raw domains?
Raw referring domains fragment one channel into many lines - for example, many Google country domains for Organic Search. Grouping visitors into channels such as Paid Search, Organic Search and Paid Social produces cleaner comparisons.
Can landing page data be included as well?
Yes. Capture the first landing page and its category alongside channel data. That lets you compare, for example, blog-driven signups with paid campaign signups, and drill into individual posts.