ConversionEX
Services
WorkReviewsAboutContact
Zurich

Analytics, Tracking & Data in Zurich

A measurement layer that survives two currencies, three languages, two privacy regimes and payment methods your analytics has never seen.

Delivered remotely for brands across Zurich and Switzerland.

Scale · Zurich

Why Zurich brands come to us for this

  • Server-side GTM on a first-party subdomain, with browser-to-server deduplication verified rather than assumed
  • Market, language and presentment currency as first-class GA4 dimensions, not guessed from URL patterns
  • TWINT and invoice payment return paths tested so purchase events fire for methods the default setup misses
  • Consent mode v2 wired to your CMP, satisfying revised Swiss data protection expectations and GDPR together
  • Daily reconciliation to Shopify order data in one agreed reporting currency, so finance and marketing stop arguing

A Zurich store's reporting is wrong in a specific, predictable way. Revenue arrives in francs and euros and gets blended at whatever rate a tool decided, so the year-on-year comparison moves with the exchange rate rather than the business. Orders paid on invoice through a third-party provider complete outside the flow the standard pixel expects, so a payment method that is entirely normal here is systematically under-counted. And traffic is split across three language storefronts that no one configured as separate reporting dimensions, so nobody can say whether French is working.

We rebuild the layer underneath: server-side tracking through a first-party subdomain resilient to blockers and ITP, Conversions API and Enhanced Conversions with correctly hashed and normalised identifiers, deduplication between browser and server events done properly, and a documented GA4 event schema where market, language and currency are dimensions rather than something you infer from a URL.

Then consent, which in Switzerland means two regimes at the same time. The revised Swiss data protection law applies to your domestic customers, GDPR applies to your EU ones, and the practical answer is a consent management platform wired to consent mode v2 with modelling, plus Shopify's customer privacy API respected in every custom script. Built once, documented once, and reported honestly — including the share of sessions you can no longer see.

Daily reconciliationreporting layer checked against Shopify order data every day
EMQ 8+event match quality target for Conversions API and Enhanced Conversions
Consent mode v2wired to your CMP with modelled conversions and documented scope
Local context

Two currencies, two privacy regimes, and payment paths the pixel does not know about

Reconciliation is the whole job here. Shopify holds the truth in the order's presentment currency and your accounting sits in francs, so a reporting layer that does not fix the conversion basis will produce numbers your finance team refuses to accept — and once that happens the dashboard stops being used. We define a single reporting currency, keep presentment currency and market as dimensions so market-level performance stays readable, and reconcile daily against Shopify's own order data. The payment layer needs the same attention: TWINT and buy-on-invoice both route through providers whose return path has to be verified to fire a deduplicated purchase event, because a missing event is not just a reporting gap, it is a bidding signal your ad platforms never receive. And on privacy, treating Switzerland as if GDPR simply applies is a shortcut that works commercially but not legally; we build to the stricter of the two operationally and make sure the documentation says what is actually happening.

Scope

What Analytics & Data includes

The same standard of work we run for every client — applied to a Zurich brand’s realities.

Full service detail
01

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.

02

Server-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.

03

Conversions API Integration

Meta CAPI, Google Enhanced Conversions and TikTok Events API with hashed identifiers, targeting event match quality of 8 or above.

04

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.

05

Consent Mode & Privacy

Consent mode v2 wired to your CMP with modelled conversions, plus Shopify's customer privacy API and regional compliance handled correctly.

06

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 Zurich store

We do not work off a rate card. Every Zurich 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 scoped
How it runs

From kickoff to results

01

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.

02

Specification

A written measurement plan: events, parameters, identifiers, consent states and destinations. Signed off before implementation begins.

03

Implement

Server-side container, CAPI, enhanced conversions and consent mode built in a staging environment and validated event by event.

04

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.

05

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
Engagement Paid growth audit → migration → paid media retainerTimeframe 6 months
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, 2026
FAQ

Analytics & Data in Zurich — your questions

Pick one reporting currency, apply a consistent conversion basis, and keep presentment currency as a dimension so market performance is still readable. The mistake we see most is a dashboard converting at live rates while the accounts convert at a booking rate, which makes the two disagree permanently. Agreeing the basis with your finance team before building the dashboard takes an hour and prevents the argument that otherwise kills adoption.

It changes documentation and transparency more than mechanics. You need an accurate account of what you collect, why, and who processes it, plus a privacy notice that reflects reality rather than a template. Most Swiss stores already run a CMP for their EU traffic, so the practical work is making sure the domestic experience and the documentation match what the tags actually do. We are implementers, not lawyers, and we scope it so your counsel is reviewing something concrete.

Usually a combination of three things: consent rejection rates that differ by market, cross-border orders completing through a payment or checkout path that fires no browser event, and sessions attributed to the wrong storefront because language markets were never separated in the property. We quantify each contribution during the audit rather than guessing, since the fix is different for each and only one of them is a tagging problem.

That is the executive layer: blended marketing efficiency, contribution margin by market, new versus returning revenue and cohort LTV, on one page, reconciled to Shopify and refreshed daily. For a Swiss brand we usually add a domestic-versus-export split, because those two businesses have different margins and different growth constraints and a blended number hides both.

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 Zurich 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.