Conversion tracking that gives your campaigns the data they need
We build the measurement infrastructure that connects your ad spend to your revenue — server-side GTM, enhanced conversions, CAPI, Consent Mode v2, and offline conversion imports, implemented properly.
Why tracking is a strategic problem, not a technical one
Every pound you spend on paid media is optimised by an algorithm. Google's Smart Bidding, Meta's delivery system, Taboola's audience model — they all learn from the conversion data you feed them. If that data is incomplete, delayed, or inaccurate, the algorithm optimises for the wrong outcomes. Better tracking doesn't just give you better reporting — it gives you better campaigns.
In 2026, browser-based tracking captures somewhere between 60% and 80% of actual conversions, depending on the audience and platform. Ad blockers, Safari ITP, Chrome's evolving privacy controls, and iOS ATT have all eroded the reliability of client-side tags. If you're still running a standard Google Analytics setup with browser-side GTM, you're making optimisation decisions with incomplete data and feeding your ad platforms an inaccurate picture of performance.
The solution is a properly implemented server-side tracking infrastructure — not as a nice-to-have, but as a foundational requirement for any serious paid acquisition programme.
What we implement
Server-side Google Tag Manager
We deploy a server-side GTM container — typically on Google Cloud Platform — that receives a single measurement hit from your website and distributes conversion data to Google Analytics 4, Google Ads, Meta (via CAPI), and any other destination platforms. This provides faster page load times (fewer client-side tags), better data accuracy (server-to-server communication), and improved privacy compliance (first-party context).
Enhanced conversions
Enhanced conversions send hashed first-party data (email address, phone number, name) alongside conversion events, allowing Google and Meta to match conversions to ad interactions more accurately. This is particularly important for cross-device conversions and for users on browsers with restricted cookie lifetimes. We implement enhanced conversions through the server-side container for maximum data quality.
Meta Conversions API (CAPI)
CAPI sends Meta conversion events server-to-server, providing redundancy against browser tracking failures and improving signal quality for Meta's delivery algorithm. We implement CAPI through the server-side GTM container alongside the Meta Pixel, with deduplication configured to prevent double-counting.
Consent Mode v2
We implement Consent Mode v2 to ensure your tracking complies with GDPR, PECR, and Google's data requirements. Tags adjust their behaviour based on user consent — firing in a limited mode when consent is denied, and in full mode when granted. Google's modelled conversions fill the gap, giving you directionally accurate data even from users who decline cookies.
Offline conversion imports
We build the pipeline that sends downstream CRM data — appointments, sales, revenue — back to Google Ads and Meta, tied to the original click IDs. This is the single most impactful thing you can do for your paid lead generation performance. It transforms your campaigns from optimising for cheap form fills to optimising for real customers.
What's included
- Tracking audit and gap analysis
- Server-side GTM container deployment
- GA4 configuration and event setup
- Enhanced conversions implementation
- Meta CAPI integration
- Consent Mode v2 setup
- Offline conversion import pipeline
- GCLID / FBCLID capture configuration
- Cross-domain tracking (if applicable)
- Data validation and QA testing
- CRM field mapping
- Documentation and handover
Impact of proper tracking
Across our enterprise clients, implementing server-side tracking with offline conversion imports has consistently been the highest-ROI investment in their acquisition stack.
25–40%
More conversions attributed
7+
Markets instrumented
2–4 wks
Typical implementation
FAQs
Frequently asked questions
What is server-side tracking and why does it matter?
Server-side tracking sends conversion data from your server to analytics and advertising platforms, rather than relying on JavaScript tags in the user's browser. This bypasses ad blockers, browser privacy restrictions (Safari ITP, Chrome Privacy Sandbox), and iOS tracking limitations. For enterprise lead generation, the impact is significant: we typically see a 25–40% increase in attributed conversions after implementing server-side tracking via Google Tag Manager's server-side container. This additional data fundamentally improves how your ad platforms' algorithms optimise your campaigns.
What is Consent Mode v2 and do we need it?
Consent Mode v2 is Google's framework for adjusting how Google tags behave based on a user's cookie consent choices. Since March 2024, it's been required for any business using Google Ads or GA4 that targets users in the EEA, UK, or Switzerland. Without it, you lose the ability to use Google's audience features and remarketing. We implement Consent Mode v2 as standard, ensuring your tracking is compliant while still capturing the maximum amount of conversion data through Google's modelled conversions.
How do offline conversion imports work?
Offline conversion imports (OCIs) allow you to send downstream outcome data — such as appointments booked, appointments attended, and sales closed — back to Google Ads and Meta. When a user clicks an ad and fills in a form, we capture the platform's click ID (GCLID for Google, FBCLID for Meta). When that lead progresses through your sales funnel, we import the conversion event back to the ad platform, linked to the original click ID. This tells the platform's algorithm which clicks led to real business outcomes, enabling it to optimise for customers rather than just form fills.
How long does a tracking implementation take?
A standard server-side GTM implementation with enhanced conversions, CAPI, and Consent Mode v2 typically takes 2–4 weeks from kick-off to go-live. This includes scoping, GTM container configuration, server-side container deployment, testing across all conversion events, and validation against your CRM data. More complex implementations — involving multiple domains, CRM stitching, or custom offline conversion pipelines — can take 4–8 weeks. We provide a detailed timeline during the scoping phase.
Do we need to change our CRM to work with your tracking setup?
Usually not. We work with your existing CRM — Salesforce, HubSpot, Dynamics, or custom systems. What we do need is the ability to capture and store tracking parameters (GCLID, FBCLID, UTM data) alongside each lead record, and a mechanism to export or push conversion events back to the ad platforms. If your CRM doesn't currently capture these fields, we'll configure that as part of the implementation. If you need a custom API integration for offline conversion imports, we'll build it.
Related services
Google Ads Lead Generation
Search and Performance Max campaigns that leverage your tracking data for better optimisation.
Lead Generation Reporting
Power BI and Looker Studio dashboards built on the data your tracking infrastructure collects.
Meta Lead Generation
CAPI integration and offline conversion imports for Meta campaigns.
Ready to talk about conversion tracking?
Tell us what you're working on. We'll respond within one working day.
Start a conversation