Link Tracking in Adobe Analytics: A Practical Guide
Adobe Analytics handles campaign attribution differently from GA4, and tagged links need to be structured with that difference in mind. Here is how it actually works.
Priya Nair
Senior Marketing Analyst
Enterprise & Compliance Blueprint Guide
Adobe Analytics attribution starts from a different concept than UTM parameters
Google Analytics 4 was built around utm_source, utm_medium, and utm_campaign as its native campaign attribution model. Adobe Analytics predates that convention and uses its own concept: the tracking code (often abbreviated as a query string parameter like cid= or a custom parameter your implementation defines), which then gets classified into a campaign hierarchy inside Adobe's admin console.
This matters practically because a link tagged purely with standard UTM parameters does not automatically populate Adobe's campaign reports the way it would in GA4. Adobe needs its own tracking code parameter present in the URL, or an explicit mapping process, to attribute traffic correctly.
How the Adobe tracking code actually works
In a typical Adobe Analytics implementation, a URL includes a parameter (commonly cid, though the exact name depends on your implementation) whose value is the tracking code, for example cid=email_spring_promo_2026. Adobe's Analytics implementation captures this value and, depending on configuration, either uses it directly as a campaign identifier or runs it through 'classification rules' that map the raw code to structured, human-readable campaign attributes.
This classification step is genuinely different from GA4's model, where the campaign, source, and medium are typically three separate parameters read directly. In Adobe, a single tracking code string is often the only thing captured at click-time, with the breakdown into channel, campaign name, and other dimensions happening afterward through classification rules configured by your analytics admin.
Combining UTM parameters with Adobe tracking codes on the same link
Many organizations running Adobe Analytics still want to preserve UTM parameters on their links, either for legacy reasons, for compatibility with other tools that expect UTM structure, or because they also run GA4 in parallel for specific properties. This is workable: a single URL can carry both a cid= tracking code parameter for Adobe and standard utm_ parameters for any other tool reading them, since they are independent query string parameters that don't conflict with each other.
The discipline that matters here is consistency: decide on a single source of truth for the actual campaign name and structure it identically whether it appears in the Adobe tracking code or the UTM parameters, so the two systems don't drift into reporting different numbers for what should be the same campaign.
Classification rules: the step most teams get wrong
Adobe's classification rules are what turn a raw tracking code string into structured, reportable dimensions like campaign channel or campaign name. If these rules are not set up, or not updated as new campaigns launch, tracking codes pile up as an unclassified list that is nearly impossible to analyze at scale, this is a distinct failure mode from GA4, where utm_medium and utm_source are read directly without a separate classification step.
Practically, this means launching a link tracking effort in Adobe Analytics requires coordinating not just with whoever creates the links, but with whoever owns classification rule maintenance, since a beautifully tagged link is still unreadable in reports until it's classified.
eVars, props, and where campaign data actually lands
Beyond the tracking code itself, Adobe Analytics implementations typically map campaign data into an eVar (a persistent variable that can carry value across a visit) for attribution reporting. Which eVar number is used for campaign tracking varies entirely by implementation, since Adobe doesn't reserve a fixed eVar the way GA4 has fixed campaign dimension names. Confirm with your Adobe Analytics admin which eVar is designated for tracking codes before assuming any tagged link will 'just work' in reporting.
This implementation-specific quality is one of the biggest practical differences from GA4: two different companies' Adobe Analytics setups can handle the identical tagged URL completely differently depending on how their eVars and classification rules were configured years ago.
Multi-touch attribution differences worth knowing
Adobe Analytics has historically offered more attribution model flexibility out of the box, allowing last-touch, first-touch, linear, and custom attribution models across the reporting suite, whereas GA4's attribution modeling, while improved over time, has generally been more constrained. If your organization needs to compare a link's performance under multiple attribution models simultaneously, Adobe's setup is often the more natural fit, but only if the underlying tracking codes are structured cleanly enough to support that analysis.
This makes clean, consistent tagging even more valuable in an Adobe context, since messy or inconsistent tracking codes undermine any of the more sophisticated attribution modeling Adobe otherwise supports.
A common mistake: assuming a tracking code works the moment it's created
Teams new to Adobe Analytics link tagging frequently assume that once a tracking code is embedded in a URL and the link goes live, campaign data will simply appear in reports the way it would in a UTM-native platform. In practice, a tracking code with no matching classification rule doesn't fail loudly, it simply shows up as an unclassified raw string sitting outside the structured campaign hierarchy, which is easy to miss entirely if nobody is specifically checking the unclassified codes report during a campaign's first days.
The practical fix is to treat classification rule setup as a required step in the campaign launch checklist, not an optional cleanup task to handle later. Before a tagged link goes live in any customer-facing channel, confirm with whoever owns classification rules that the new tracking code's naming pattern is already covered by an existing rule, or that a new rule has been added to handle it. Checking the unclassified codes report a day or two after launch, rather than waiting until a monthly reporting cycle, catches this gap early enough to fix it without losing meaningful attribution data for the length of the campaign.
A practical workflow for tagging links destined for Adobe Analytics
Agree on the tracking code naming convention with your Adobe Analytics admin before creating any links, since the classification rules depend on a predictable, parseable format (many teams use an underscore or pipe-delimited structure like channel_campaign_content). Generate short links carrying both the Adobe tracking code and, where useful, standard UTM parameters for cross-tool compatibility. Confirm new tracking codes get added to classification rules promptly, ideally on a routine cadence rather than reactively when someone notices a campaign missing from a report.
This mirrors the naming-convention discipline covered generally in utm governance as a team grows, applied specifically to Adobe's tracking code and classification model rather than GA4's flatter parameter structure.
When to also read the GA4 integration guide
If your organization runs both Adobe Analytics and GA4, whether during a migration or permanently across different properties, see connecting a link shortener to Google Analytics for the GA4-specific mechanics, since the two systems genuinely differ enough that a single tagging strategy needs deliberate translation, not just reused conventions, between them.
Review features for how link creation and export support both tagging models, and confirm with your Adobe implementation team which specific parameter name and eVar mapping your organization actually uses before rolling out a new tagging convention broadly.
Frequently Asked Questions
Do UTM parameters work automatically in Adobe Analytics?
Not the way they do in GA4. Adobe typically relies on its own tracking code parameter and classification rules to attribute campaigns, so UTM parameters alone won't populate Adobe's campaign reports without additional configuration.
What is a classification rule in Adobe Analytics?
A configuration that maps a raw tracking code string captured from a URL into structured, reportable dimensions like campaign name or channel. Without classification rules set up, tracking codes remain an unreadable list of raw strings in reports.
Can one link work for both Adobe Analytics and GA4?
Yes, a single URL can carry both an Adobe tracking code parameter and standard UTM parameters simultaneously, since they are independent query string values that don't conflict with each other.
Which eVar should campaign tracking use in Adobe Analytics?
This varies by implementation and is not standardized the way GA4's campaign dimensions are. Confirm with your own Adobe Analytics admin which eVar is designated for tracking codes in your specific setup.
Join 14,000+ marketing growth leaders
Receive our bi-weekly breakdown of campaign analytics setups, attribution rules, naming tactics, and link-stitching blueprints. Direct to your inbox.
Continue reading blueprints
All ArticlesConnecting a Link Shortener to Google Analytics
A tagged short link and a correctly configured GA4 property need to agree on the same parameters. Here is the technical setup, step by step.
Social Media Link Compliance for Pharma Marketers
Pharma social media has to balance genuine audience engagement against strict regulatory constraints on claims, disclosures, and link presentation.