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.
Berlin
Analytics, Tracking & Data in Berlin
Measurement built for a market where a large share of your traffic never consents to being measured at all.
Delivered remotely for brands across Berlin and Germany.
Scale · Berlin
Why Berlin brands come to us for this
- Your actual consent rate measured and reported, so everyone knows what share of traffic the dashboards never saw
- Consent Mode wired from the consent platform into the tag layer, protecting EEA advertiser features as well as analytics
- Server-side collection configured in an EU region, with retention and IP handling set for a DPO to sign off
- Every channel number reconciled against Shopify order data, which is complete regardless of consent
- Reporting built on contribution after returns, because a fourteen-day withdrawal right makes gross revenue optimistic
German ecommerce analytics starts from an uncomfortable fact: a meaningful share of your visitors decline tracking, that share is not random, and every dashboard in your business is quietly reporting on the remainder as if it were the whole. Most Berlin stores we audit have never measured their own consent rate, which means nobody in the company knows the size of the gap between what happened and what was recorded. Fixing that is the first job, because it changes how every other number is read.
Then the plumbing. Consent Mode has to be implemented properly rather than declared — signals wired from your consent platform into the tag layer so denied states are actually respected and Google's modelling has something to work with, instead of a banner that blocks scripts and leaves you with a hole. Server-side collection through a container you control gives you durable, deduplicated events and one place to enforce consent state, rather than six vendor scripts each making their own decision in the browser.
The output has to survive a conversation with your finance team. Shopify's order data is complete regardless of consent, so it is the anchor: channel numbers get reconciled against it, discrepancies get explained rather than averaged, and reporting is built to contribution margin rather than to platform-reported ROAS. In a market with a fourteen-day withdrawal right and high category return rates, revenue that has not survived the return window is not revenue, and a reporting layer that ignores that will overstate every channel you run.
Local context
Consent, data residency and numbers that hold up in a German boardroom
Working under GDPR and German telecoms-privacy rules is not a compliance footnote here — it determines the architecture. Storage of and access to information on a user's device requires consent, so the consent platform is upstream of everything and the tag layer has to obey it rather than negotiate with it. We implement against the major German-market consent platforms, set data retention and IP handling conservatively, and configure server-side collection in an EU region so the data path is something your DPO can actually approve. Consent Mode matters more than in most markets for a practical reason too: Google requires consent signals for advertiser features in the EEA, so a badly implemented banner does not just cost analytics accuracy, it degrades remarketing and audience capability across the ad accounts. And because German buyers are unusually likely to research on one device and purchase on another, and because invoice payment means an order can be placed days before it is paid, the reporting layer has to model that lag rather than treat it as noise. We build to the numbers your Geschäftsführung will be asked about — contribution after returns, blended acquisition cost, owned versus paid share — and document what each one excludes.
Scope
What Analytics & Data includes
The same standard of work we run for every client — applied to a Berlin 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 Berlin store
We do not work off a rate card. Every Berlin 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 Berlin — your questions
That is the first thing we measure, and the answer varies more than people expect by category and traffic source. Once you know it, you know how to read every other report — and you can compare consented and non-consented behaviour indirectly through Shopify order data to see whether the two groups differ. Guessing at this number is how businesses end up making budget decisions on a systematically biased sample.
In an EU region, as a default rather than as an upgrade. It keeps the collection path inside a jurisdiction your data protection officer can assess, shortens the argument in a privacy review, and costs no more to run. We document the data flow, the fields collected and the retention settings so the whole implementation can be handed to your DPO or your Steuerberater's advisers without an archaeology project.
Yes, and this is the part that usually gets attention. Google requires valid consent signals for advertiser features in the EEA, so a banner that blocks tags without passing proper consent state degrades remarketing audiences and conversion modelling as well as reporting. We treat the consent platform, the tag layer and the ad accounts as one implementation rather than three, because they fail as one.
By modelling the lag rather than ignoring it. An order paid on invoice is placed at one moment and paid at another, sometimes days later, and a small share is never paid at all. If your dashboard counts the order at placement and your accounting counts it at payment, the two will never agree and someone will spend a week finding out why. We define which event each report uses, state it on the report, and reconcile both against Shopify.
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 Berlin 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.