Case study

Server-side attribution restoring closed-loop pipeline visibility

Server-side attribution

Executive summary
An organisation investing heavily in demand generation had lost trust in its numbers. Browser privacy changes, ad blockers, and ITP had broken client-side tracking, making it impossible to connect first-touch activity to pipeline and revenue with confidence. We implemented a server-side attribution architecture that restored closed-loop visibility.

The challenge

  • Significant drop in tracked conversions and event fidelity
  • Marketing and sales could no longer agree on which channels or workflows actually produced opportunities
  • Optimisation decisions were being made on incomplete or misleading data
  • Existing pixel-based setup was fragile and non-compliant with evolving privacy expectations

The system we built

  1. Server-side capture — Critical conversion and behavioural events moved to server-side GTM / equivalent pipelines.
  2. First-party identity — Consented identifiers and first-party data used to stitch sessions and touches where possible.
  3. CRM / pipeline join — Events connected to opportunity and revenue data for true closed-loop reporting.
  4. Governance — Clear data contracts, documentation, and privacy controls so the system remained maintainable and compliant.

Results

  • Event fidelity recovered to 90%+ of expected volume
  • First-touch and multi-touch attribution became visible again
  • Marketing and sales shared a single, more trustworthy view of pipeline contribution
  • Reduced reliance on brittle third-party pixels
  • Cleaner foundation for ongoing optimisation of both campaigns and the lead-ops workflows themselves

Why it matters
Accurate attribution is the measurement layer that lets a Workflow-as-a-Service system improve over time. Without it, process innovation cannot be proven or compounded. This work restored the feedback loop that makes scalable lead operations possible.

← All case studiesBuild something similar ↗