SERVICE FILE · ECOMMERCE ATTRIBUTION · FILED BY BARIS ASA, LONDON · REVIEWED
Ecommerce attribution tracking consultant, London, UK.
If GA4 files your paid sales under Direct, PayPal or Unassigned, the campaign data was lost between the ad and the order. Only fixes that keep that data intact put the label back: redirects, domains, the payment return, consent. Server-side sends add click IDs the browser lost but can't rebuild a stripped UTM. Models, tools, surveys and lift tests share credit between visits that were recorded.
I'm Baris Asa, a London tracking specialist. I fix sales credited to the wrong channel, for ecommerce brands and the agencies behind them. I find the step where the campaign data is lost (a redirect, the payment page, a second domain) and fix it there. If a tracking problem has been named but not located, email me what you saw.
Options for fixing broken ecommerce attribution, and the order to do them in
Most broken attribution is data lost between the ad and the order, and each loss has a fix at source. Find your symptom; the fix is next to it. In order:
- Paid traffic under Direct or Organic: keep the UTMs and the click ID (gclid, the ID Google Ads adds to each click) through every redirect to the landing page (F-204).
- Your own checkout domain under Referral: cross-domain measurement, so one visit crosses the step (F-204).
- PayPal or Klarna under Referral: add them to GA4's unwanted referrals list (F-205).
- Campaigns in Unassigned or the wrong channel: one UTM convention that matches GA4's channel rules.
- Paid sales lost when visitors decline cookies: Consent Mode v2 wired to the banner, with URL passthrough on (same-domain links, with a gclid or dclid in the landing URL).
- Meta sales with no ad attached: server-side purchases sent with Meta's click ID (F-401).
A model, an attribution platform or an incrementality test comes after this. Your agency or marketing team decides the credit model; fixing the data that feeds it is a separate job. Redirects, domains, the payment return and consent are the measurement part, and that part is mine. What I fix and what your agency owns.
Email me what you saw and I'll say where the data is probably lost.
Doing it yourself? The order to work in gives a test and a done-when for every step. Weighing GA4 settings, server-side, attribution software, surveys, lift tests and mix models against each other? Eight options compared.
The quickest check
UTMs are the tags on a campaign link (such as utm_source). The query string is everything after the ? in the address. Three steps, no ad click needed:
- Take your landing page URL, add
?gclid=test123&utm_source=test&utm_medium=test, and open it through the route your ads use (the old domain, the shortener, the country page). - When the page loads, both should still be in the address bar. This tests redirects only. The payment return and a second domain need a test order.
- In GA4, open Reports › Acquisition › Traffic acquisition, last 28 days. Look for direct stepping up on a set date, a payment provider or your own domain among the referrals, and rows in Unassigned.
What you see tells you where to look:
- Parameters gone from the address bar: a redirect problem, usually a small developer fix.
- A payment provider in referrals: a GA4 setting, then a test order.
- Unassigned rows with a source and medium filled in: naming. A UTM convention fixes it from the next campaign.
- Direct up on the day of a redesign, a new checkout or a new banner: a fault, worth tracing. Some direct is always real.
Sales credited to the wrong channel: the faults I fix
- Paid traffic under Direct or Organic Search. The gclid or the UTMs never reach the landing page. A badly configured redirect drops the query string (a domain move, a country redirect, a link shortener), or the site rejects parameters it doesn't know. Direct or organic depends on whether the referrer survived (F-204). Doc ↗
- Facebook ads under Organic Social, or campaigns in Unassigned. GA4 files traffic by fixed channel rules. A medium like social_paid or fb_ads doesn't count as paid, so a Facebook ad lands in Organic Social. The rules ignore case; in my experience the report rows don't, so Meta and meta can show up as separate rows. Doc ↗
- PayPal, Klarna or Stripe under Referral. The shopper comes back from the payment page with the provider as referrer, and GA4 can credit the purchase to it. If the payment took longer than the session timeout (30 minutes by default), a new session also starts. The fix is the unwanted referrals list, then a test order (F-205). Doc ↗
- Your own checkout or booking domain under Referral. A step on another root domain, without cross-domain measurement, gets its own cookie: a new user and a new session. With it set, the _gl parameter carries the IDs across, unless a redirect strips it, the page navigates by script rather than from the click, or another script blocks the click event (F-204, F-205). Doc ↗
- Fewer paid sales from visitors who decline cookies. With ad_storage denied, the click ID isn't stored in a cookie. URL passthrough adds it to links within the same domain instead, when the landing URL carries a Google click ID and the tag is consent-aware. It doesn't cross to another domain. Modelling covers part of the rest, where volume allows (F-201). Doc ↗
- Meta sales with no ad attached. Server-side purchases go to Meta without fbc, the value that carries Meta's click ID. Meta recommends sending it with every event. With no _fbc cookie, build it as fb.1.<timestamp in ms>.<fbclid>, with the fbclid exactly as it arrived: it is case-sensitive, so a lower-casing rule must not touch it. Doc ↗
- A gap left after all of that. Collection is browser-only. Ad blockers and Safari's cookie limits lose the click, so the sale lands without its channel. I measure the gap first, then add a server path where it pays (F-401).
The coded ones are on record in the fault index, with how they're found and fixed.
What I fix, and what your agency owns
- Mine: the data between ad and order. Redirects, domains, payment return, UTM convention, consent, server-side click data.
- Your agency's or marketing team's: how credit is shared (the model), an attribution platform, a post-purchase survey, a lift test or a mix model. They read the same UTMs, click IDs and orders, so they inherit whatever was lost.
- The ceiling: your store's orders. Count a week of orders in the store, then the same week in GA4. Attribution can only share out sales that were recorded, and sending purchases from a server or through Measurement Protocol doesn't restore a UTM that was stripped before the landing page.
I have no partnership or commission arrangement with any tool, so none is named here. The full comparison says what each option can and cannot fix.
Example: paid clicks filed as organic and direct (illustrative numbers, not a client)
- A store moves to a new domain and redirects the old one. Google Ads still sends its clicks to the old address. The redirect drops the query string, so the gclid never reaches the new page. In GA4, Paid Search falls the week of the move, and Organic Search and Direct rise by about the same amount between them.
- The fix: the redirect keeps the query string, and the ads point at the new domain. One tagged test visit is followed to an order before anyone reads the channel report again.
Is this the help you need?
Probably, if
- direct is your biggest channel and grew on a date you can name;
- PayPal, Klarna, Stripe or your own domain sits among your referrals;
- campaigns land in Unassigned, or one platform shows up as several sources;
- the ad platforms claim sales GA4 gives to direct, and nobody can say which is right.
Another page covers it, if
- the channels look right but the totals don't match the store: that's GA4 reconciliation;
- you want to choose an attribution model or a media mix: that sits with your agency;
- you want the whole set-up checked, Meta and consent included: a tracking audit;
- the store is on Shopify and purchases themselves are missing or doubled: Shopify tracking.
Questions to ask anyone fixing your attribution
- 01 How will you prove it?
You want one test visit followed from a tagged ad URL to the order, with the campaign and click ID checked at each step, and the order's session source then read in GA4's Traffic acquisition report.
- 02 Will you fix it at source?
The answer should be: at the redirect, the link, the domain list, the consent set-up. Not a custom channel group that relabels lost traffic after the fact.
- 03 What stays with our marketers?
The UTM convention is written down and handed over, so new campaigns don't undo the fix the next month.
How attribution should be kept, ad to order
These six settings cover most of it. This is what I set:
| Setting | What gets set | Why |
|---|---|---|
| Campaign tags | One written UTM convention: lower case, one source per platform, one medium per channel | One campaign is one row, in the right channel. |
| Click IDs | Auto-tagging on; the whole query string kept through every redirect (gclid, gbraid, wbraid, fbclid) | The ad keeps the sale, not search or direct. |
| Domains | Cross-domain measurement for every other root domain in the purchase path | One visit stays one visit across the step. |
| Payment return | Payment providers on the unwanted referrals list | New sessions stop crediting the provider. Earlier ones keep their source. |
| Consent | Consent Mode v2 with URL passthrough (same-domain links, with a gclid or dclid in the landing URL) | The click stays with the visit on your own domain when cookies are declined. |
| Server events | fbc sent with server-side purchases | Meta can tie a server-sent sale to the ad click. |
Consent, in short: URL passthrough keeps the Google click ID with the visit, page to page on your own domain, for shoppers who decline cookies. Modelling covers part of the rest, where volume allows. Banner and tag set-up: Consent Mode v2.
Campaign parameters for Meta ads go in the ad's URL parameters field (Meta's help page). Server-side Meta events: Meta Conversions API. When the browser alone isn't enough: server-side tracking.
A wider read on one symptom: direct traffic jumped after the redesign.
Who you'd be working with
I'm Baris Asa. I've spent eight years setting up and fixing tracking for ecommerce brands and the agencies behind them. Measurement only: I don't run or judge your campaigns. The faults I look for are public: 19 documented in the fault index. The ones I check first when sales land in the wrong channel: F-204 (attribution lost in transit), F-205 (split sessions at a subdomain or payment step) and F-201 (Consent Mode mis-wired). I've spoken on this at HeroConf, PPC Live and Search 'n Stuff.
Attribution repair for UK agencies
I fix attribution for UK agencies, named or white-label, inside the client's own GA4, GTM, Google Ads and Meta. Agencies usually call when the client's sales and the channel report disagree.
- What you receive. Each step that lost data, what changed and when, a UTM convention for your team, and a report that can carry your agency's name.
- Who holds what. Campaigns and the attribution model stay with you. Accounts stay in the client's name.
- Terms. An NDA if you need one. Client contact only if you ask.
How agency work is arranged and billed: white-label tracking for agencies.
Questions about ecommerce attribution
- What are the best options for fixing broken ecommerce attribution?
- Fix the measurement first, because only it puts a lost campaign label back; models, attribution tools, surveys and lift tests only share credit between visits that were recorded. The order to work in is in the order-to-work-in note and the eight options are weighed in the options note.
- Why are my sales showing as direct in GA4?
- Usually the campaign details never arrived: a redirect dropped the gclid or the UTMs, and the referrer went with them. The quickest check on this page shows whether that's happening on your site.
- Why do PayPal or Klarna show as a referral source?
- The shopper returns from the payment page with the provider as referrer, and GA4 can credit the purchase to it. Add the provider in Admin › Data collection and modification › Data streams › Web › your stream › Configure tag settings › Settings › Show all › List unwanted referrals (Editor role or above, up to 50 conditions per data stream). It applies to events collected after you save it; sessions already recorded are not rewritten as far as Google documents, and a shopper whose earlier visit came from it can still be credited to it for a while, under last non-direct click.
- Consultant, agency or freelancer: who should do this?
- Your agency runs the campaigns and decides how credit is shared between them. Keeping campaign and click data intact from ad to order is a measurement job, and measurement is all I do. I'm a freelance consultant and I do the work myself, for brands directly or alongside their agencies.
- Do you work with agencies, inside our clients' accounts?
- Yes, for UK agencies, named or white-label, inside the client's own GA4, GTM, Google Ads and Meta. Campaigns stay with you. Terms: synctag.co.uk/white-label.
- What access is needed?
- Editor on the GA4 property and publish access to GTM. Whoever on your side can change auto-tagging in Google Ads and the URL parameters on your Meta ads, or access at a level that allows those two changes. Plus whoever can change redirects and the payment settings, and a test order on the live site.
- How is attribution repair priced?
- There is no published rate card. Brands get a quote after a short scoping call, fixed once agreed. What moves the number: how many domains and payment providers sit in the purchase path, how many redirects there are, and whether the fix needs a developer on the site.
Sources, read 5 and 19 Nov 2026: Google Ads: about auto-tagging (gclid) · GA4: default channel group rules · GA4: collect campaign data with custom URLs (UTMs) · GA4: set up cross-domain measurement (_gl) · GA4: identify unwanted referrals · GA4: about Analytics sessions · GA4 and Universal Analytics sessions compared · Google Ads: iOS campaign measurement (gbraid, wbraid) · Google: consent mode, URL passthrough · Meta: fbp and fbc parameters.
Related services
- GA4 reconciliation: why GA4, the store and the ad platforms report different totals.
- Tracking audit: what a full check of GTM, GA4, Google Ads, Meta and consent covers.
- GA4 consultant: who sets up and repairs the GA4 property itself.
- Google Tag Manager consultant: who builds and looks after the GTM container.
- Consent Mode v2: who sets up and repairs Consent Mode v2.
- Google Ads conversion tracking: online sales counted once, at the right value.
- Meta Conversions API: setting up CAPI with the Pixel, deduplicated.
- Server-side tracking: who sets up and repairs server-side GTM.
- Shopify tracking: GA4, Google Ads and Meta on a Shopify store.
- GA4 ecommerce tracking: purchase events built and sent correctly, off Shopify.
- Offline conversion tracking: phone and CRM sales imported into Google Ads.
- White-label for agencies: tracking work under your agency's name.
- How I work: how a job is scoped and run.
Email what
you saw.
The site, whether the parameters survived the test URL, and the channel that looks wrong, with the date it changed if you know it. I'll tell you where the data is probably lost. I reply myself.
Example example.co.uk · gclid gone after the redirect · direct up since the new checkout in March · PayPal in referrals
[email protected]