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.
Paris
Analytics, Tracking & Data in Paris, France
Measurement built for a market where a large share of visitors decline tracking and the reporting still has to be usable.
Delivered remotely for brands across Paris and France.
Scale · Paris
Why Paris brands come to us for this
- Consent mode wired to your consent platform with modelled conversions, built for a market where a large share of visitors decline
- Server-side tracking on a first-party subdomain with correct browser-to-server deduplication, so permitted events actually arrive
- Reporting split by market so France, the French-speaking neighbours and the English international market each stand on their own
- Margin measured after returns and refunds, because a statutory withdrawal right makes returns structural rather than exceptional
- Delivery-method economics tracked separately for pickup point and home delivery, including failed-delivery cost
French consent enforcement is among the strictest in Europe in practice as well as on paper: refusing has to be as easy as accepting, and a substantial share of visitors refuse. That is the single most important fact about analytics for a Paris store, and most stores respond to it by ignoring it. GA4 quietly under-reports, the ad platforms see a partial picture, the numbers stop reconciling with Shopify, and the weekly meeting becomes an argument about the data rather than a decision about the business.
The response is not a workaround. It is building for the constraint. Consent mode wired properly to your consent platform so denied traffic still sends cookieless signals and modelled conversions restore a directional picture. Server-side tracking through a first-party endpoint so the events you are permitted to collect actually arrive rather than being lost to blockers on the way. A documented GA4 event schema so a report means the same thing in six months. Then a reconciliation against Shopify order data across a full week, because a screenshot of a tag firing proves nothing.
And the reporting has to answer the questions a cross-border French store actually has, which are not the ones a single-market dashboard answers. What does France contribute versus Belgium versus the international English market. What is the margin after returns rather than before them, in a market with a statutory withdrawal right and categories like fashion where the return rate is the number that decides profitability. What does an order actually cost to deliver once pickup point and home delivery are separated. Those belong on the same screen as revenue.
Local context
Reporting that separates markets, delivery methods and returns
A blended European number is the most comfortable and least useful figure a Paris brand can look at. It hides a domestic market carrying an export market that loses money on every parcel, and it hides a return rate that varies enormously by destination and by category. So we build the reporting layer to split three ways that generic dashboards do not. By market, so France, the French-speaking neighbours and the English international market each stand on their own with their own acquisition cost and their own contribution. By delivery method, because pickup point and home delivery have materially different costs and failure rates and the mix is something you influence at checkout. And by margin after returns and refunds rather than gross revenue, since the statutory fourteen-day withdrawal right means returns are a structural feature of the P&L rather than an exception to be footnoted. Add the VAT treatment differing by destination and the number that looks like revenue in a platform dashboard can be some way from the number that reaches the business. We reconcile to Shopify, and we show the gap rather than smoothing it.
Scope
What Analytics & Data includes
The same standard of work we run for every client — applied to a Paris 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 Paris store
We do not work off a rate card. Every Paris 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 Paris — your questions
Yes, once it is built for that reality instead of against it. Consent mode sends cookieless signals for denied traffic which feed modelled conversions, so you keep directional trends and channel comparisons even where you cannot process individual data. Server-side collection protects the consented events from being lost to blockers. What you should stop expecting is a complete user-level picture, and any vendor promising you one in this market is describing something you would not want to be doing.
By separating them at every layer, which usually has to be built rather than switched on. Market dimension on the GA4 events, campaign structure that does not blend countries, shipping cost and failed-delivery cost attached per destination, returns attributed to the market that generated them, and VAT treated per destination rather than at a single rate. Most stores we audit discover one export market has been quietly subsidised by the domestic one for a year.
In fashion and leather goods, absolutely, because it is the number that decides whether a campaign was profitable at all. A statutory fourteen-day withdrawal right plus a category where fit is uncertain means gross revenue and net contribution can diverge sharply, and by the time returns land the campaign that generated them has already been scaled. We report revenue net of returns as the headline and show the gross figure alongside it rather than the other way around.
In most cases yes, and we would rather integrate correctly with the one you have than sell you a replacement. What we check is whether it genuinely blocks tags before consent, whether refusal is as easy as acceptance, whether the consent state is passed to the tags and to the server container rather than only to the banner, and whether the record of consent is retrievable. Plenty of installed banners look compliant and are wired so that nothing downstream ever reads the answer.
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 Paris 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.