Where attribution disappears: six hops from the ad click to the order, and who keeps each one
Filed
Baris Asa, Synctag, tracking specialist, London · Last checked:
Attribution disappears at one of six hops between the ad click and the order: the link, the redirects, the landing page, your own second domain, the payment return and the order itself. Direct that jumped after a redesign is usually a redirect or a new template dropping the tags (hop 2 or 3). PayPal, Klarna or Stripe under referrals means the payment return isn’t on GA4’s unwanted referrals list (hop 5). The sale is real; only the label is lost.
Marketers own the link. A developer owns the redirects. Whoever runs the tracking owns the landing page, your own domains and the order. The GA4 admin owns the payment return. A redesign, a new domain, a new payment method or a new link tool usually breaks one.
This chapter is the route map: what each hop must do, who keeps it and what to re-check after a change. The notes linked from each hop do the repair, and the order to fix it in sets out which repair comes first.
Which hop is it, and who do I send it to?
Three readings in GA4, Reports, Acquisition, Traffic acquisition, using the report’s default channel group dimension:
- Direct by week: a line that steps up on one date and stays there, with paid spend unchanged, is a hop that broke that week.
- Referrals (switch to Session source / medium): your own checkout or booking domain, or a payment provider, is a journey split at a hop.
- Unassigned: usually links tagged with a medium name GA4 doesn’t recognise. Send it to marketers.
Exhibit A: what you see, which hop, who fixes it, where the repair is
| What you see | Hop | Who fixes it | Repair |
|---|---|---|---|
| Direct steps up on a launch date | 2 or 3 | Developer, then tracking | Direct after a redesign |
| Own checkout or booking domain in referrals | 4 | Tracking and developer | Cross-domain |
| PayPal, Klarna or Stripe in referrals | 5 | GA4 admin | Payment referral |
| Paid social in Organic Social, campaigns in Unassigned | 1 | Marketers | Unassigned |
| Your own banner credited with sales | 1 | Marketers | Internal UTMs |
| GA4 right, Google Ads or Meta short of orders | 6 | Tracking | Click IDs |
What are the six hops, who owns each, and how is the loss filed?
Exhibit B: route register for a UK online shop with a separate checkout domain and two payment providers (illustrative, not a client). It sits with the tracking documentation, beside the campaign naming sheet.
| Hop | Correct state | Owner | Filed as |
|---|---|---|---|
| 1. Link | Auto-tagging on, UTMs to one written convention | Marketers | F-204 |
| 2. Redirects | Every route keeps the full query string | Developer | F-204 |
| 3. Landing page | Tag and click-ID storage on every template | Tracking | F-204 |
| 4. Own domains | One visit across domains, _gl arrives | Tracking and developer | F-205 |
| 5. Payment return | Every gateway listed as unwanted referral | GA4 admin | F-205 |
| 6. Order | Purchase in the same session, click IDs sent | Tracking | F-204 |
F-204 is the source lost in transit. F-205 is one journey split in two at a hop inside your own purchase path, with the hop credited as the source. When the split also strips the ad click ID, both apply.
Hop 1: does the link carry a source GA4 can read?
A link with no tag, or a tag GA4 can’t read, loses the source before anyone clicks.
For Google Ads, auto-tagging adds a click ID, the gclid, to every ad click. Google says GA4 gives auto-tagging priority over manual tagging, with no override, so hand-written UTMs on Google ads don’t decide the channel (auto-tagging or manual UTMs).
Every other paid, email and social link needs utm_source, utm_medium and utm_campaign. GA4 sorts sessions into channels by fixed rules, checked in order. Paid Social needs a social source and a paid medium, such as cpc or one starting paid. A social source with a non-paid medium usually lands in Organic Social; the Display and Cross-network rules are checked first. A session that matches no rule is Unassigned. Channel rules ignore case, but reports don’t, so Meta and meta become two rows.
Keep the convention in writing: lower case, one source name per platform, one medium per channel. No UTMs on links between your own pages.
Breaks when: a new channel launches, someone new builds the links, or an email or social tool starts adding its own tags.
Hop 2: does the query string survive every redirect?
Between the click and the landing page there is often a redirect: an old URL, a link shortener, http to https, a country or language page, a “clean URL” rule. If any of them drops the part of the address after the ?, the UTMs and the gclid go with it, and GA4 sees a visit with nothing to read.
Google’s instruction for Ads is plain: make sure the gclid is passed to the final landing page. Google also notes that a small share of sites don’t accept extra URL parameters and show an error page.
The rule for the developer: every redirect keeps the full query string, not just the path. The test is a tagged address through each route your ads and emails use, checking the parameters are still in the address bar when the page loads. Include a page your cache or CDN serves, since a caching rule that ignores or strips the query string does the same damage.
Breaks when: a redesign or migration adds old-URL redirects, the site moves domain, or a CDN, caching or hosting rule is added.
Hop 3: is the source read and stored on the landing page?
The UTMs don’t need to stay in the address all the way to checkout. GA4 reads the source when the session starts and the session carries it; only a hop to another root domain needs help (hop 4). What the landing page must do is read it and store it.
So the Google tag needs to be on every page template, including campaign pages built in a separate tool. A session that starts on a page without the tag starts somewhere GA4 never saw.
The ad click ID has to be stored too. In Google Tag Manager (GTM), the Conversion Linker tag finds ad click information in the landing page URL and stores it in first-party cookies on your domain. Google recommends the All Pages trigger, because a visitor can land anywhere.
When a visitor declines advertising cookies (ad_storage denied), that cookie isn’t written. URL passthrough can carry the click ID from page to page in the address instead, but Google’s conditions include consent mode on the page and a link to the same domain, so it doesn’t cross to a second domain. Consent wiring is chapter 03.
Breaks when: a new template, landing page builder or theme ships without the container, or the Conversion Linker is moved off All Pages.
Hop 4: does one visit stay one visit across your own domains?
If checkout or booking lives on a different domain, GA4 sees two visitors unless the two sites pass an ID between them.
Subdomains are usually fine: by default the Google tag sets its cookies on the highest-level domain it can, so shop.example.co.uk and www.example.co.uk share them. Google still recommends cross-domain set-up where subdomains use different cookie domains.
A separate root domain, such as a hosted checkout, gets its own cookies. Without cross-domain measurement, Google says the same person counts as two users and two sessions; in practice your first domain then shows up as a referral on the second. With it, the visitor’s IDs travel in a _gl parameter added to the link. Every page on both domains needs the same tag ID from one web data stream. Google lists what stops _gl arriving:
- a redirect, or a destination that drops extra parameters;
- navigation triggered by script rather than a click;
- a script that stops the click event.
Booking widgets and forms in an iframe run on the provider’s domain and are their own case (iframes and booking widgets).
Breaks when: a checkout, booking or second shop domain is added, or a button is rebuilt to navigate by script.
Hop 5: does the payment return keep the original source?
You can’t tag PayPal’s or Klarna’s pages, so cross-domain doesn’t apply. The visitor leaves to pay and comes back, and if the return is read as a new source, the gateway gets the sale. A GA4 session times out after 30 minutes of inactivity by default, so a slow payment step can also start a new session.
The setting is the unwanted referrals list: Admin, Data collection and modification, Data streams, your web stream, Configure tag settings, Show all, List unwanted referrals. Google says GA4 then marks matching events so the referrer isn’t used as a traffic source. It needs the Editor role and allows 50 entries per data stream. Google’s example shows sessions recorded before the change keep the old source, so date it.
Breaks when: a new payment method is added. Each one brings a hostname that isn’t on the list yet.
Hop 6: does the order keep the source it earned?
Hops 1 to 5 deliver the visitor to the order confirmation page with the source intact. Hop 6 records the sale against it.
For GA4, the purchase event fires on the confirmation page in the same session as the rest of the visit. For Google Ads and Meta, the click ID stored at hop 3 has to reach the conversion: the Google Ads tag uses the click information the Conversion Linker stored, and Meta recommends that server-sent events carry the fbc value built from the fbclid. A click ID can drop out in six places between landing and order; do gclid and fbclid survive your checkout? lists them, with a test order that shows which.
Breaks when: the checkout platform or confirmation page changes, or tracking moves server-side and the click IDs aren’t passed on.
What does the shape of Direct tell you?
GA4 files a session as (direct) / (none) when it arrives with no UTMs, no click ID and no referrer. Google’s help says a session that starts by direct entrance is credited to the source already on record for that visitor, so a returning customer often keeps their earlier channel. The shape then points at the hop:
- A slow rise alongside brand searches, emails opened in apps and links pasted from AI assistants: normal.
- A step on one date that holds: hop 2 or 3, sent to the developer first.
- Direct that grows with checkout volume, not with visits: hop 4 or 5.
Which changes should trigger a re-check?
Any change to how people reach the site or how they pay.
Exhibit C: re-check schedule
| Change | Hop at risk | Check |
|---|---|---|
| New channel, agency or link tool | 1 | Source and medium of the first week’s sessions |
| Redesign, migration, new redirect or cache rule | 2, 3 | Tagged click through every route |
| New landing page tool or template | 3 | Tag and Conversion Linker in GTM Preview |
| New checkout, booking or second domain | 4 | _gl on the link, one session in DebugView |
| New payment method | 5 | Test order, its source by transaction ID |
| Server-side move, checkout change | 6 | Test order in Google Ads and Meta |
The test is one tagged visit taken through to a test order, with its source read by transaction ID in an Exploration. Run it after every change in the table, and once a month on the full route. These checks need GTM and GA4 admin access: it is the part to hand to whoever runs your tracking.
What doesn’t a clean route recover?
Sessions already recorded keep the source they were given; a fix works from the day it goes live, so date every change. A clean route also doesn’t decide how credit is shared between channels. That is the attribution model, and it is your marketers’ call; the options compared sets out what each method can answer. Two losses sit outside the route: visitors who decline advertising cookies, a consent question for chapter 03, and browser cookie limits on returning visitors, on file at F-401 .
Also filed as
- where does attribution get lost between ad click and purchase
- how to keep UTM parameters from landing page to checkout
- who to ask when paid traffic shows as direct in GA4
- who owns UTM and attribution tracking on an ecommerce site
- what to re-check after a redesign or new checkout so GA4 keeps the source
- attribution route map ad click to order GA4
Faults explained here
- F-204 Attribution lost in transit Traffic that clearly drove sales piling up under "direct / none", or your own payment processor sitting in the top referrals. Real channels get no credit.
- F-205 Self-referrals & session fragmentation Your own site or your payment gateway sits in your referral report (shop.example.com "referring" www, or paypal.com / referral), and one journey is counted as two sessions at the hop.
Sources
- Google Ads: About auto-tagging (make sure the GCLID is passed to the final landing page; some sites don't allow arbitrary URL parameters and show an error page; in GA4 auto-tagging is prioritised over manual tagging with no override; test by clicking your ad; checked 16 Nov 2026)
- Analytics: Default channel group (rules on source and medium; Direct is source (direct) with medium (none) or (not set); rules evaluated in order, with Cross-network and Display before Paid Social and Organic Social; Unassigned when no rule matches; channel definitions aren't case sensitive; checked 16 Nov 2026)
- Analytics: Collect campaign data with custom URLs (utm_source, utm_medium, utm_campaign; parameter values are case sensitive; checked 9 Nov 2026)
- Tag Manager: Conversion linker (stores ad click information from landing page URLs in first-party cookies and local storage on your domain; All Pages trigger; linking across domains; checked 16 Nov 2026)
- Google tag platform: Set up consent mode on websites (URL passthrough when ad_storage is denied; conditions include consent mode on the page and an outgoing link to the same domain; gclid, dclid, gclsrc, _gl and wbraid may be appended; checked 16 Nov 2026)
- Google tag platform: Configure and customise cookies (automatic cookie domain; cookies set on the highest level of domain possible; subdomains measured without extra configuration; checked 16 Nov 2026)
- Analytics: Set up cross-domain measurement (two root domains count as two users and sessions without it; _gl; recommended for subdomains with different cookie domains; redirects, script navigation and stopped click events break it; same tag ID from one web data stream; checked 16 Nov 2026)
- Analytics: Identify unwanted referrals (ignore_referrer so the referrer isn't displayed as a traffic source; Admin path; Editor role; 50 per data stream; earlier sessions keep their attribution; checked 16 Nov 2026)
- Analytics: About Analytics sessions (a session times out after 30 minutes of inactivity by default; session_start carries the attribution of the session; checked 16 Nov 2026)
- Analytics: Scopes of traffic-source dimensions (Traffic acquisition uses session-scoped dimensions and the paid and organic last click model; sessions initiated by direct entrance are attributed to the values already on record for that user; checked 16 Nov 2026)
- Meta for Developers: fbp and fbc parameters (fbc built from the fbclid; recommended on every Conversions API event; checked 9 Nov 2026)
Baris Asa, a London tracking specialist working as Synctag, takes one tagged visit through all six hops to a test order, fixes the tracking hops alongside your developer, and hands over the route register. For ecommerce brands and the agencies behind them.
Ecommerce attribution tracking →