Case Studies

Data that
delivers

Three projects. Three challenges. Measurable results. A look at how we work — from problem analysis to a complete tracking setup.

Case Study 01
E-Commerce 10 weeks GTM Server-Side · GA4 · Meta CAPI · Google Cloud

From Data Chaos to Triple ROAS

How an established e-commerce company made its ad spend significantly more profitable through server-side tracking (measured ROAS increase: approx. 3×) — while reducing data loss from 42% to under 5%.

Background & Challenge

An established e-commerce company with seven-figure annual revenue was fighting an increasingly severe data loss problem: Safari ITP, iOS ATT and widespread ad blockers were causing 42% of all tracking events to disappear — without GA4 giving any indication. The result was campaign decisions made on incomplete data and a ROAS that was structurally reported too low.

  • 42% data loss due to ad blockers and Safari ITP
  • Over 60 outdated tags in the GTM container, some firing before the consent signal
  • No first-party data strategy — all cookies set as third-party
  • Meta CAPI not implemented — conversions were massively under-reported
  • GA4 and Google Ads showed >30% divergence on conversion figures

Our Approach

1

Analysis & Audit (Week 1–2)

Complete inventory of the existing GTM container, all tags and tracking endpoints. Quantification of data loss from ad blockers and ITP across all browsers and devices.

2

Server-Side Infrastructure (Week 3–4)

Setup of the GTM Server Container on Google Cloud. Configuration of the first-party cookie domain and SSL certificate for reliable data capture.

3

GA4 & Meta CAPI Migration (Week 5–6)

Step-by-step migration of all events to the server container. Parallel operation to validate data quality before cutting over completely.

4

Consent Mode v2 & Validation (Week 7–8)

Clean integration of CMP signals into the server layer. QA with DebugView, GA4 Realtime and Meta Test Events to confirm full compliance and accuracy.

5

Go-Live & Handover (Week 9–10)

Production cutover, deactivation of old client-side tags, documentation and handover to the internal team with full training.

Key Learnings

  • Server-side tracking is not a luxury for e-commerce above CHF 1M revenue — it is a necessity
  • The biggest lever is often not a new tool but improving the data quality of existing ones
  • Parallel operation (client + server) is essential for a safe migration without data gaps
  • Consent Mode v2 must be initialised before all GTM tags — sequence is everything
  • GTM audits regularly uncover privacy risks that no one had on their radar

Project Overview

Industry E-Commerce
Duration 10 weeks
Team 2 people
Technology GTM Server-Side · GA4 · Meta CAPI · Google Cloud

Results after 10 weeks

ROAS increase
-42% data loss reduced
<3% divergence GA4 & Ads
-15% CPA reduced

"rhyn.digital showed us how much money we were wasting based on incorrect data. After the implementation we could finally optimise our campaigns on real signals."

Sonam W. · Marketing Lead, E-Commerce
Case Study 02
B2B SaaS 8 weeks GA4 · GTM · HubSpot CRM · Data Studio · Google Ads

Making the Lead Pipeline Visible

A Swiss B2B SaaS provider didn't know which marketing channels were truly bringing customers. After 8 weeks they had a complete picture of their lead journey — and halved their CPL.

Background & Challenge

A Swiss B2B SaaS provider with a growing inside sales team faced a classic problem: marketing was investing budget in SEO, Google Ads, LinkedIn and content — but which channel was actually bringing paying customers remained unclear. Three different tools produced three different numbers. Budget allocation decisions were made on gut feeling, not reliable data.

  • Three different analytics tools producing contradictory conversion figures
  • Form events only partially captured — up to 40% of demo requests went untracked
  • No CRM integration: offline conversions and opportunity data never fed into analysis
  • LinkedIn Ads and Google Ads had separate attribution — no cross-channel view
  • CPL optimisation was impossible without reliable lead source attribution

Our Approach

1

Analytics Audit & Data Inventory (Week 1–2)

Full analysis of all existing tracking implementations, form events and conversion goals. Identification of data gaps per channel and tool.

2

GA4 Rebuild & Complete Form Tracking (Week 3–4)

Clean GA4 implementation with comprehensive capture of all lead forms, demo requests and trial sign-ups via a structured GTM data layer.

3

CRM Integration & Offline Conversions (Week 5–6)

HubSpot CRM connected via API. Lead status and deal stage fed back into GA4 and Google Ads as offline conversions — enabling true end-to-end attribution.

4

Multi-Channel Attribution & Data Studio Dashboard (Week 7)

Unified reporting across all channels in a single Data Studio dashboard — from first impression to closed deal, including CPL trends per channel.

5

Team Handover & Training (Week 8)

Documentation, handover to the marketing team and training of internal users for independent work with the dashboard and new reporting structures.

Key Learnings

  • CRM integration is the decisive step: only when offline data flows back does a complete attribution picture emerge
  • Cross-channel attribution starts with clean single-source tracking — not an expensive attribution tool
  • Consistent form tracking in GA4 is what makes real conversion optimisation possible
  • B2B SaaS benefits disproportionately from Smart Bidding once offline conversions are correctly passed through
  • A single dashboard used by all stakeholders is more valuable than ten specialised views

Project Overview

Industry B2B SaaS
Duration 8 weeks
Team 2 people
Technology GA4 · GTM · HubSpot CRM · Data Studio · Google Ads

Results after 8 weeks

more attributed leads
-35% cost-per-lead
100% form capture rate
1 unified dashboard

"Before, we had three different tools giving us three different numbers. Now we have a single source of truth — and for the first time we know exactly what our marketing investments deliver."

Raphael O. · CEO, B2B SaaS
Case Study 03
Agency 12 weeks GTM Server-Side · Google Cloud · GA4 · Jentis · Data API

Scalable Tracking Infrastructure for an Agency

How a Swiss performance agency standardised and automated its tracking quality across 12 client accounts — with a white-label tracking stack that deploys in hours rather than weeks.

Background & Challenge

A Swiss performance agency was managing 12 client accounts simultaneously — with steadily growing coordination overhead. Every new client required manual GTM configuration, server-side tracking setup from scratch and a fresh Consent Mode integration. That consumed 3–4 weeks per onboarding, tied up resources and produced inconsistent data quality across accounts. At the same time, there was no central monitoring: tracking errors often went unnoticed for weeks.

  • 3–4 weeks of effort for tracking onboarding of every new client
  • No standardised GTM container — every implementation was individual and hard to maintain
  • No central monitoring infrastructure: errors in one account often went undetected for weeks
  • Inconsistent Consent Mode implementations increased GDPR risk across all client accounts
  • Team overloaded by manual maintenance work: 40% of capacity absorbed by legacy upkeep

Our Approach

1

Infrastructure Analysis & Template Design (Week 1–3)

Inventory of all 12 accounts. Derivation of shared requirements. Design of a white-label GTM template container with standardised tags, triggers, variables and consent logic.

2

Server-Side Tracking Platform Build (Week 4–6)

Setup of a central GTM Server Container infrastructure on Google Cloud with multi-tenant routing logic — one infrastructure serving all current and future client accounts.

3

Template Rollout Across All 12 Accounts (Week 7–9)

Step-by-step migration of all existing accounts to the template container. Parallel operation for validation without data loss. Per-account customisations remain possible.

4

Automated QA & Account Monitoring (Week 10–11)

Automated checks via GA4 Data API: alerts for traffic anomalies or conversion drops across all 12 accounts simultaneously — proactive rather than reactive.

5

Documentation & Team Enablement (Week 12)

Complete technical documentation, a client onboarding playbook and training of the agency team for independent use, development and future client onboarding.

Key Learnings

  • Standardisation is the biggest lever for agencies: one template container beats 12 individual solutions in both efficiency and quality
  • Central server-side tracking reduces not only costs but also privacy risks across all clients
  • Automated monitoring is the difference between reactive error correction and proactive quality assurance
  • Onboarding playbooks pay for themselves after just the second new client
  • Multi-tenant infrastructure is economically superior from 5 parallel accounts onwards

Project Overview

Industry Agency
Duration 12 weeks
Team 3 people
Technology GTM Server-Side · Google Cloud · GA4 · Jentis · Data API

Results after 12 weeks

-70% tracking maintenance effort
2h client onboarding (vs. 3–4 weeks)
12/12 accounts migrated to server-side
100% standardised data quality

"The tracking infrastructure rhyn.digital built has completely freed up our team. We onboard new clients in hours rather than weeks — and at higher data quality than ever before."

Lena B. · Head of Digital, Performance Agency
Case Study 04
Publishing / Media 3 weeks GTM · GA4 · Consent Mode v2 · CMP (Usercentrics)

Consent Mode v2: Privacy Without Data Loss

How a Swiss media company increased its analytics coverage from 58% to over 95% through correct Consent Mode v2 implementation — without compromising nDSG compliance.

Background & Challenge

An established Swiss media company had implemented a CMP following the introduction of the nDSG, considering their data privacy obligations covered — or so they thought. What nobody had noticed: Consent Mode v2 had never been correctly integrated into GA4 and GTM. The result was a silent data loss of around 40%, which triggered no alerts and no error messages. Campaign decisions, content analyses, and reach measurements were based on structurally incomplete data for months.

  • ~40% data loss due to missing Consent Mode v2 signals
  • GA4 received no consent_status parameters from the CMP
  • GTM tags fired before the CMP callback — incorrect firing order
  • Modelled data in GA4 not activated due to missing prerequisites
  • GA4 and Google Ads showed >25% divergence in conversion figures

Our Approach

1

Audit & Diagnosis (Week 1)

Full analysis of the GTM container and CMP setup. Identification of the incorrect tag firing order and missing dataLayer integration between Usercentrics and GTM.

2

Consent Mode v2 Implementation (Week 2)

Correct integration of default and update commands via GTM. Ensuring the CMP callback executes before all tracking tags. Activation of Advanced Consent Mode in GA4.

3

Validation & Go-Live (Week 3)

QA using GTM Preview, GA4 DebugView, and the Consent Mode Debugger. Review of modelled conversions in GA4. Documentation and handover to the internal team.

Key Learnings

  • Consent Mode v2 is not optional — mandatory since March 2024 for Google Ads conversion modelling
  • A CMP alone is not enough: the technical integration into GTM and GA4 is what matters
  • Tag firing order in GTM is the most common and most invisible misconfiguration
  • Advanced Consent Mode enables GA4 modelling — but only with correct signal transmission
  • Data loss from incorrect consent setup never appears as an error — it shows up as a silent gap

Project Overview

Industry Publishing / Media
Duration 3 weeks
Team 2 people
Technology GTM · GA4 · Consent Mode v2 · CMP (Usercentrics)

Results after 3 weeks

+38% recovered data points
<5% GA4 modelling gap
100% nDSG-compliant implementation
3 wks implementation time

«We thought we were fully compliant from a data privacy perspective — until rhyn.digital showed us we'd been losing nearly 40% of our measurement data at the same time. The difference after implementation was immediately visible.»

Markus F. · Head of Digital, Swiss Media Company
Our Methodology

What all projects have in common

Despite different industries and challenges, all our projects follow the same core principles.

Audit before implementation

We build nothing until we understand what's already there and why it isn't working. A thorough audit saves time and prevents repeating old mistakes in a new form.

Measurement plan first

What should be measured? Why? And what decisions should the data enable? We answer these questions together — in writing, before the first tag is set.

Validation after every step

Every implementation is fully validated before going live. No assumptions — measurable confirmation that the data is correct.

Handover & documentation

Every project ends with complete documentation and a handover training. Your team should understand, maintain and further develop the implementation.

Ready to become the next success story?

Free introductory call — we'll show you exactly where your potential lies and how we would solve your specific challenge.

Book a free call →