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.
Amsterdam
Analytics, Tracking & Data in Amsterdam
Measurement for Amsterdam brands who have to be both GDPR-clean and able to tell whether Germany is actually making money.
Delivered remotely for brands across Amsterdam and Netherlands.
Scale · Amsterdam
Why Amsterdam brands come to us for this
- Consent rate measured by market and device first, so nobody draws conclusions from a filtered sample without knowing it
- Consent Mode v2 implemented and verified, because in the EEA it affects the ad accounts as much as the reports
- Server-side tagging run in a European region with a parameter set your legal position can actually support
- Reporting in a base currency with market splits, so an exchange-rate move is not mistaken for a performance trend
- Refunds and returns modelled into the same revenue table, since the withdrawal right reverses revenue after it is booked
European measurement has a constraint the American playbook does not account for: a meaningful share of your visitors will not consent to tracking, and that is the law working as intended rather than a bug to engineer around. The consequence is that any decision made from client-side analytics alone is made on a filtered sample, and the filtering is not random. We start every Dutch engagement by establishing what proportion of sessions are measurable, whether that proportion differs by market and device, and how far the gap between the tag and the Shopify order record actually runs.
Then we make the order data the source of truth. Shopify knows every order, every market, every currency and every refund regardless of consent, and reconciling GA4, the ad platforms and the Shopify record against each other is what turns four contradictory dashboards into one number people will act on. Consent Mode v2 gets implemented properly so that modelled conversions and remarketing signals behave as Google expects in the EEA, and server-side tagging is set up in a European region with the parameters your legal position allows rather than everything the tag could possibly send.
The reporting layer is where the cross-border reality bites. A blended ROAS across four countries hides the two that are subsidising the other two. So the executive view is contribution margin by market, after cost of goods, after outbound and inbound freight, after payment costs that differ by method, and after returns. That last one reorders the picture more than anything else in an apparel account, because the market with the best-looking ROAS is frequently the one with the worst return rate, and nobody had put the two numbers on the same page.
Local context
Consent, currency and returns: three things that break a European dashboard
Three specifics recur in Dutch accounts. First, consent: the banner is often implemented in a way that either suppresses far more than it needs to or fires tags before consent in a way nobody wants to defend, and both are fixable once someone actually reads what the CMP is doing rather than trusting the app's marketing page. Consent Mode v2 is not optional for EEA ad personalisation, and a missing implementation degrades the ads accounts, not just the reports. Second, currency: a store selling in euros, pounds and Swiss francs needs a base-currency reporting layer or every trend line is partly an exchange-rate artefact. Third, returns. The fourteen-day withdrawal right means revenue recognised today can be reversed inside the reporting period, so we build the refund and return data into the same table as the revenue rather than leaving it in a separate operations export. A Dutch brand that reports gross revenue by market is reporting a number that will change after the fact, and always in the same direction.
Scope
What Analytics & Data includes
The same standard of work we run for every client — applied to a Amsterdam 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 Amsterdam store
We do not work off a rate card. Every Amsterdam 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 Amsterdam — your questions
It is used across Europe, and using it responsibly is a configuration and governance question rather than a switch. That means consent obtained before non-essential tags fire, IP handling and data retention set deliberately, no personal data pushed into custom dimensions, and a data processing position your DPO or adviser has actually seen. We implement to that standard and document it. Where a brand's legal advice pushes toward a European-hosted analytics tool instead, we will implement that and keep Shopify as the commercial source of truth either way.
The share varies a lot by traffic mix, and the honest answer for your store is a measurement, not an industry figure. Server-side tagging improves durability and data quality for the events you are permitted to collect; it does not create permission you do not have, and anyone selling it as a way to track non-consenting users is selling you a problem. What genuinely closes the gap is reconciling to Shopify order data and using modelling where the platforms support it.
By reporting net of VAT in a single base currency, with the VAT rate held per market so the conversion is correct rather than approximate. Gross revenue comparisons across EU markets are misleading because the tax component differs by country and by product category. We build the reporting layer to strip VAT, convert at a consistent rate, then apply cost of goods, freight and payment costs so what you compare between the Netherlands and Germany is contribution, not turnover.
We can see it, and we are careful about how much weight we put on it. Cross-market journeys are more common than most brands expect, particularly for buyers who browse in English and check out in their own market, and a naive market attribution will credit the last storefront. We set the market dimension from the order rather than the session, keep the session-level path available for diagnosis, and judge channel performance on incrementality tests rather than on any single attribution model.
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 Amsterdam 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.