Tracking Audit & Reconciliation
A full event inventory across GA4, Meta, Google Ads, Klaviyo and Shopify, reconciled against order data to quantify exactly where and how much data is lost.
London, UK
Analytics, Tracking & Data in London
Measurement for London brands who need to know which market is actually profitable once duty and returns are in the number.
Delivered remotely for brands across London and United Kingdom.
Scale · London
Why London brands come to us for this
- Server-side tagging so events survive browser restrictions, with deduplication across Meta, Google and GA4
- GA4 built with market as a primary dimension, so UK and EU performance are never averaged together
- Contribution by market modelled with duty, cross-border shipping and returns included, not revenue alone
- UK GDPR and PECR consent implemented with a real reject option and Consent Mode configured honestly
- A written data map and event dictionary, so the setup is explainable long after the person who built it moved on
Most London stores can tell you revenue by country and almost none can tell you contribution by country. That gap is where cross-border businesses lose money slowly. An EU order carries duty you may have absorbed, a higher shipping cost, a longer transit and a return that has to come back across a customs line — so a market that looks profitable in GA4 can be losing money in the ledger while everyone celebrates growth.
So we build the measurement layer to answer the question that matters. Server-side tracking through a tagging server, so events survive browser restrictions and ad blockers and your platforms get consistent data. GA4 configured with market as a first-class dimension rather than an afterthought. Shopify order data joined to shipping cost, duty treatment and returns so a report can show contribution per market rather than top-line revenue.
And it has to be consent-correct from the start. Under UK GDPR and PECR, non-essential cookies need consent before they fire, a consent management platform has to offer a genuine reject, and Consent Mode has to be implemented so modelling is legitimate rather than a fig leaf. We implement that properly, document what fires when, and give you a written data map — because the version of this that gets you in trouble is the one nobody can explain six months later.
Local context
The number that matters is contribution by market, after duty and returns
Measurement for a London brand has to reconcile three ledgers that rarely agree: the ad platforms, Shopify, and the actual bank position after carriers, duty and returns. We build server-side event collection with proper deduplication so the platforms are working from the same events, then join Shopify order and refund data to shipping and duty cost so each market gets a contribution figure rather than a revenue figure. UK returns behaviour is part of that model, since the statutory 14-day cancellation right means a predictable return volume that has to sit in the unit economics, not in a surprise column at quarter end. Consent is handled under UK GDPR and PECR with a documented data map, and because reporting arrives from a seven-hour time difference we build it as a dashboard you read at 8am with the commentary already written, rather than a call where someone talks you through a screen.
Scope
What Analytics & Data includes
The same standard of work we run for every client — applied to a London brand’s realities.
Full service detailServer-Side Tracking
Server-side GTM on a first-party subdomain, resilient to ad blockers and ITP, with deduplication between browser and server events done properly.
Conversions API Integration
Meta CAPI, Google Enhanced Conversions and TikTok Events API with hashed identifiers, targeting event match quality of 8 or above.
GA4 Event Schema
A documented, consistent eCommerce event and parameter specification across every surface, so reports mean the same thing in six months as they do today.
Consent Mode & Privacy
Consent mode v2 wired to your CMP with modelled conversions, plus Shopify's customer privacy API and regional compliance handled correctly.
Executive Reporting Layer
One dashboard for blended MER, contribution margin, cohort LTV, new-versus-returning revenue and channel payback. Reconciled to Shopify, refreshed daily.
Scoped and quoted for your London store
We do not work off a rate card. Every London engagement starts with a fixed statement of work — named deliverables, named dates, one number — written after we have looked at your store, not before. If a smaller first step would serve you better, we will say so.
Get this scopedHow it runs
From kickoff to results
Audit & Quantify
We measure the gap between platform-reported and actual orders per channel. Most stores we audit are losing 15-30% of conversion signal before we start.
Specification
A written measurement plan: events, parameters, identifiers, consent states and destinations. Signed off before implementation begins.
Implement
Server-side container, CAPI, enhanced conversions and consent mode built in a staging environment and validated event by event.
Validate
Order-level reconciliation against Shopify for a full week, plus match-quality checks in each platform. We do not sign off on a screenshot of a tag firing.
Report & Maintain
Dashboards built, team trained, and monitoring in place to alert on event volume anomalies before someone spots them in a monthly report.
Proof
Analytics & Data results
Anonymised under NDA. Figures pulled from the client’s own analytics.
Consumer Electronics & Accessories
~$9M/yr, 210 SKUs, US + AU · Shopify Plus (migrated from BigCommerce)
Meta ROAS had slid from 3.6x to 1.9x in a year and the team had spent twelve months buying new creative to fix it. The real cause was measurement: the BigCommerce checkout dropped 22% of purchase events and the Conversions API had never been installed, so both ad platforms were optimising on incomplete data. The named constraint: peak season was 14 weeks out, and the replatform had to be live and stable well before Black Friday traffic arrived.
1.9x → 3.4xMeta ROAS, once the 22% event gap closed60 days after server-side tracking went live, spend up 18%. Most of that is signal we recovered, not performance we invented — the honest number is the blended CAC below, which is measured against Shopify orders
-32%customer acquisition cost$44 to $30 blended across Meta and Google
4.1s → 1.7smobile LCPdesktop went 2.9s to 1.2s over the same window
+47%peak-season revenueBlack Friday through Cyber Monday, year over year
In their words
Clients on this work
GA4/Shopify gap 14% → under 2%
“Paid audit, and worth every dollar. Forty pages on where our measurement was lying to us — duplicate purchase events, CAPI never configured, GA4 and Shopify off by 14% — each one ranked by the revenue it was hiding. No pitch deck at the end. We fixed six of the items ourselves before we ever signed a retainer.”
FounderHome goods brand, ~$3M/yr · Denver, CO
Verified client, 2026FAQ
Analytics & Data in London — your questions
By modelling cost to serve per market rather than reading revenue. That means duty treatment, cross-border carrier cost, transit-related support contacts and return rate joined to the order data, then compared against contribution rather than ROAS. Most brands find one or two EU markets are genuinely strong and one is being carried by the others, which is an actionable finding that a country revenue chart will never surface.
A consent management platform that blocks non-essential tags until a choice is made, gives reject the same prominence as accept, records the choice, and passes that signal to Google and Meta through Consent Mode and their consent APIs. Server-side tagging does not exempt you — the same consent basis applies to a server-side event. We document which tags are treated as essential and why, because that judgement is the part regulators ask about.
Because they measure different things and count differently: attribution windows, view-through, consent-driven modelling, and currency conversion timing across markets all diverge. The goal is not to make them match, which is impossible, but to have one source of truth — Shopify order data — and to understand the size and direction of each platform's bias so you can read them as steering instruments rather than accounts.
It complicates it, and it catches people out. Orders placed in euros are converted for reporting, and depending on where the conversion happens you can get drift between GA4, Shopify's reports and your accounts. We standardise on one reporting currency, use Shopify's presentment and settlement values consistently, and note conversion treatment in the data map so a discrepancy is explainable instead of alarming.
Browser tracking loses 15-30% of conversions to ad blockers, ITP and consent rejections. Server-side sends events from your own infrastructure, which recovers most of that signal. Better signal means better algorithmic bidding, so it usually pays for itself in media efficiency within a quarter.
Four to six weeks for a typical Shopify store, including the validation week. Complex setups with subscriptions, multiple markets or a headless front end run six to ten. The audit and specification phase takes about a third of that and is the part that determines quality.
Yes. We use Shopify's Web Pixels API and customer events for checkout tracking, which is the supported path since checkout.liquid was retired. Order-level data comes through the server side, so checkout tracking no longer depends on scripts Shopify will not let you inject.
Next step
Analytics & Data for your London brand.
Thirty minutes with the strategist who would actually run your account. We screen-share your store, read your data live, and tell you the three highest-value things we can see from the outside.
Shopify or Shopify Plus stores doing $150k/mo or moreFounder, CEO or eCommerce lead on the callNo deck and no pitch — we open your store instead
Prefer to write it out? [email protected] gets a real reply the same business day, Mon-Fri, 9am-6pm MT.