Adobe Analytics uses tracking codes (s.campaign, often called CIDs) instead of UTM parameters by default, but it accepts custom query strings and can be configured to read utm_* tags via Processing Rules or Adobe Experience Platform Web SDK. Track Link generates UTM-tagged short URLs that survive any redirect chain, and Adobe Analytics can ingest those UTMs into eVars and props for full enterprise attribution. This guide walks through how to pass Track Link tracked URLs through Adobe Analytics, configure tracking codes, and use processing rules to map Track Link UTMs to Adobe's reporting variables.
Free plan: 25 links, 4K clicks/month, full analytics. No credit card required.
Why combine them
Adobe Analytics' default attribution variable is s.campaign (the tracking code or CID), which is read from a query parameter you configure (commonly cid or s_cid). Track Link can pass any query parameter through the redirect, so your existing Adobe tracking codes work unchanged — just generate the short URL with ?cid=<code> appended.
Adobe Analytics supports up to 250 eVars and 75 props, which is far more granular than GA4's custom dimensions. You can dedicate one eVar to Track Link campaign, one to source, one to medium, and one to the original short slug — giving you separate reportable dimensions for each piece of UTM context.
Processing Rules in Adobe Analytics can copy a query parameter into an eVar at the server side, no JavaScript change required. This means a single Processing Rule can capture utm_source from every Track Link click and populate eVar1 across your entire reporting suite.
Adobe's Marketing Channel Processing Rules let you classify traffic into channels (Email, Paid Search, Affiliate) based on URL patterns. Track Link's utm_medium directly feeds these rules, so tracked-link traffic flows into the correct channel without manual tagging on the Adobe side.
Adobe Experience Platform Web SDK (alloy.js) replaces the legacy s_code library and supports first-party data collection with consent-aware controls. Track Link's redirect-side click count is unaffected by SDK consent state, so you have a deterministic ground truth even when Adobe sessions are suppressed.
Adobe Analytics' Workspace and Customer Journey Analytics (CJA) can ingest Track Link click data via CSV import or via API into Adobe Experience Platform. This unifies offline click events (from Track Link's server-side count) with on-site behavior (from Adobe Web SDK) into a single Customer Journey for cross-channel attribution.
Step by step
A practical workflow for combining Track Link click data with Adobe Analytics.
Adobe Analytics implementations historically use ?cid=<code> as the tracking code parameter. If your implementation already uses cid (or s_cid), build Track Link short URLs with that parameter appended: https://gettrack.link/abc123?cid=email_spring2026. If you want to use standard UTM tags instead (recommended for cross-platform consistency with GA4), configure Adobe to read utm_source via Processing Rules — see step 3 below.
Use the Track Link tracking link generator and add either ?cid=<code> or the full UTM set (utm_source, utm_medium, utm_campaign, utm_term, utm_content) to your destination URL. Track Link preserves these query params through the redirect so they arrive at your destination page intact, where the Adobe Web SDK or s_code library can read them.
In Adobe Analytics > Admin > Report Suites > Edit Settings > General > Processing Rules, create a new rule. Set the condition to If query string parameter utm_source is set, then Overwrite value of eVar1 with query string parameter utm_source. Repeat for utm_medium (eVar2), utm_campaign (eVar3), utm_term (eVar4), utm_content (eVar5). Each Track Link click that resolves to your tagged page now populates these eVars automatically with no s_code change.
If your implementation uses the legacy s_code library, in your s.doPlugins (or the equivalent in Adobe Launch / Tags), assign s.campaign = s.Util.getQueryParam('cid') || s.Util.getQueryParam('utm_campaign'). This ensures every page load with a tracking code or UTM populates the s.campaign variable, which feeds the Tracking Code dimension in Adobe Workspace. Use the s.getValOnce plugin to prevent re-attribution within the same session.
In Admin > Marketing Channels > Marketing Channel Processing Rules, create rules that match query parameter utm_medium against values like email, social, cpc, organic. Each rule assigns the visit to a Marketing Channel (Email, Social, Paid Search, Organic Search). Track Link clicks now flow into the appropriate channel automatically, and you can compare channel performance in Workspace's Marketing Channels report.
Install the Adobe Experience Platform Debugger Chrome extension. Click a Track Link short URL in your browser and inspect the resulting Adobe Analytics beacon. Verify that the page view request includes the right c.utm_source, c.utm_campaign, and that the s.campaign variable is set. Then in Workspace, build a freeform report with the eVars you populated and confirm clicks from the Track Link short URL appear with the expected dimension values.
Need to build tagged URLs first? Use the UTM builder or the tracking link generator. Verify redirects with the redirect checker.
Use cases
Real situations where pairing Track Link with Adobe Analytics pays off.
Large organizations with multi-brand portfolios run dozens of campaigns simultaneously. Track Link short URLs with consistent UTM naming flow into Adobe Analytics' eVars, which can then be analyzed in Workspace by region, brand, and campaign simultaneously. The combination scales to hundreds of campaigns without the tracking-code sprawl that pure cid-based implementations suffer from.
Adobe Analytics customers often have multiple report suites (one per region, brand, or property). Roll-Up suites aggregate data, but tracking codes are not always consistent across child suites. By standardizing on Track Link UTMs and mapping them via Processing Rules in every child suite, you get a unified campaign dimension across the roll-up — useful for executive reporting where the question is, 'How did the spring campaign perform globally?'
Adobe's Attribution IQ in Workspace lets you apply different attribution models (first touch, last touch, linear, U-shaped, J-shaped, time decay, custom). The model applies to whichever dimension you choose — eVar3 (utm_campaign) is a natural fit. Track Link feeds eVar3 with consistent campaign names from every channel, so Attribution IQ can model each channel's contribution to converters across the journey, not just the last-touch source.
Track Link short URLs work as the entry point for offline campaigns (QR codes on print ads, NFC tags, in-store signage) where Adobe's pixel cannot fire until the user reaches a digital property. The UTMs survive the redirect, so when the user lands on your domain, Adobe's Processing Rules capture them and the campaign is attributed correctly — closing the loop on offline-to-online attribution.
Frequently asked questions
Common questions about using Track Link alongside Adobe Analytics.
Adobe's default attribution variable is s.campaign, which reads from a query parameter you choose (typically cid). It does not read utm_* tags out of the box. To use Track Link's UTMs, configure Processing Rules or your Launch/Tags property to copy query parameters like utm_source into eVars. Once configured, UTMs work as well as cid does, with the added benefit of cross-platform consistency with GA4 and other platforms.
Yes. Create a Data Element in Launch with type Query String Parameter and the parameter name utm_source (repeat for each UTM). Then in your Adobe Analytics extension, map these Data Elements to eVars and props. This is the modern equivalent of the s_code Processing Rules approach and is the recommended pattern for new implementations using Web SDK (alloy).
Adobe Analytics tracks the page view that results from a click — not the click itself. If a user clicks a tracked link but never reaches your tagged page (browser closed, redirect failed, ad blocker), Adobe sees nothing. Track Link counts the click at the redirect server, before the page load, giving you a deterministic baseline. The two together give you click-to-page-view conversion rates per channel.
Yes. AAM segments are built on visitor behavior captured via Adobe Analytics, the Web SDK, or DCS calls. Once Track Link UTMs flow into eVars, you can build AAM segments based on those eVars (e.g. visitors whose first eVar3 was Spring2026Campaign). The Track Link redirect itself does not need to integrate with AAM directly.
In Adobe's s_code, the getValOnce plugin stores a campaign value in a cookie for a configurable window (e.g. 30 minutes) and prevents the same value from being re-attributed within that window. When using Track Link, set s.campaign = s.getValOnce(s.Util.getQueryParam('utm_campaign'), 'utm_campaign_cookie', 30, 'm'). This ensures a refresh or re-click within the session does not double-count the campaign.
Yes. Export Track Link clicks as CSV from the dashboard or via API and load them into Adobe Experience Platform as a separate dataset. In CJA, define a connection that joins the Track Link click events with your Adobe Analytics dataset on a common key (e.g. utm_campaign and timestamp). This creates a unified Customer Journey including server-side click events, which is especially valuable for measuring channels where the Adobe SDK undercounts.
Yes. Web SDK reads query parameters via Data Elements just like Launch does. Configure utm_source, utm_medium, utm_campaign as Data Elements of type Query String, then map them to XDM fields in your Edge Configuration. The Track Link UTMs flow into your XDM event payload and into both Adobe Analytics and Customer Journey Analytics simultaneously.
Track Link's enterprise plan supports SSO via SAML 2.0 with providers including Okta, Azure AD, OneLogin, and Google Workspace. This matches the access controls most Adobe Analytics customers expect. Reach out via the contact page if your team needs SSO provisioned alongside the Adobe rollout.
Create a free Track Link account, generate tracked URLs, and start feeding richer click data into your Adobe workflows. No credit card, no setup fee, full analytics on the free plan.