UTM tracking in Adobe Analytics
Adobe Analytics does not use the UTM convention natively the way GA does. Campaign attribution typically runs through the campaign tracking-code dimension, and UTM parameters from inbound links are captured into that dimension or into eVars using Processing Rules or the Web SDK. Knowing this mapping lets you reuse UTM-tagged links inside Adobe.
No native UTM, but a clear path
Adobe Analytics centres campaign attribution on the campaign dimension, usually populated by a tracking code, rather than the five UTM parameters GA expects. Because UTM is just a query-string convention, you can still tag links with utm_source and friends and map them into Adobe.
The common approach is to read the UTM query parameters and write them into the campaign variable or into eVars, either with Processing Rules, a marketing-channel processing setup, or the Adobe Web SDK / AppMeasurement configuration.
- Adobe uses a campaign tracking-code dimension, not native UTM
- Capture UTM via Processing Rules, eVars, or the Web SDK
- Marketing Channel rules can classify the captured values
Mapping and classification
Decide which UTM parameter drives the campaign tracking code (often utm_campaign) and which feed eVars (utm_source, utm_medium, utm_content, utm_term). Marketing Channel processing rules can then classify hits into channels using the captured query parameters.
Exact capture mechanics depend on your implementation (AppMeasurement vs Web SDK) and admin configuration, so the specific rule setup is marked partially verified — confirm it against your Adobe environment and current documentation rather than assuming one fixed recipe.
How it appears in analytics and logs
A populated campaign tracking-code value sourced from a UTM parameter means your capture rule read the inbound query string. An empty value means the rule did not match, the parameter was absent, or a redirect removed it before collection.
Diagnostic use case
Reuse UTM-tagged campaign links inside Adobe Analytics by mapping the parameters into the campaign tracking code or eVars, so cross-tool campaigns share one tagging scheme.
What WebmasterID can help detect
WebmasterID logs the inbound campaign hit server-side, giving an independent record of tagged arrivals you can reconcile against Adobe's campaign dimension when capture rules or redirects are in doubt.
Common mistakes
- Expecting Adobe to read UTM parameters automatically like GA does.
- Writing personal data into UTM values that then populate eVars.
- Capturing UTM into a tracking code without classification, leaving raw values in reports.
- Assuming one capture recipe works across AppMeasurement and the Web SDK.
Privacy and accuracy notes
Tracking codes and eVars built from UTM values describe the campaign, not the visitor. Keep personal data out of UTM parameters so it does not flow into Adobe dimensions, reports, or data feeds.
Related pages
- UTM in Google Analytics 4
Google Analytics 4 reads the standard utm_ query parameters and maps them to its session and traffic-source dimensions. The mapping is specific: utm_source, utm_medium, and utm_campaign feed the core dimensions, utm_id powers the manual campaign ID, and utm_source/medium combinations drive GA4's default channel grouping. Knowing the exact mapping prevents tags that look fine but land in the wrong channel.
- UTM parameters and default channel grouping
Analytics tools sort traffic into channel groups (Paid Search, Organic Social, Email, Referral, Other) using rules built mostly on utm_medium. Choose the wrong medium and good traffic falls into 'Other' or the wrong channel. This page explains how the mapping works and the medium values that keep channels correct.
- UTM and server-side tracking
Server-side tracking reads the UTM parameters from the incoming HTTP request on your server, rather than relying on a browser tag to capture them. This makes campaign attribution resilient to ad blockers, script failures, and consent-gated client tags. The trade-off is that the server sees the landing request but must be designed to persist the campaign context across the visit. This page covers the mechanics and limits.
- Attribution analytics
Reconcile tagged arrivals with Adobe campaign dimensions.
Sources and verification notes
- Adobe Experience League — Marketing channels and tracking codesAdobe campaign attribution uses tracking codes and marketing channels; UTM must be mapped in.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.