Use this banner section for site-wide announcements, news updates, big changes and more.
.svg){kind=logo}
.png)
If your Google Ads dashboard is showing fewer conversions than you know are happening, you are not imagining it. The analytics infrastructure that B2B PPC relied on for a decade is quietly breaking, and the gap between what your tracking reports and what is actually happening in your pipeline grows every quarter.
The hard number: B2B marketing teams relying solely on client-side tracking are now losing 20–40% of their attribution data to browser restrictions, ad blockers, and consent decline. That is not a rounding error. For a business spending £50,000 a month on paid search, it is the difference between knowing which campaigns are driving pipeline and which are wasting money.
The solution is a combination of first-party data strategy and server-side tracking, two terms that often get discussed separately but only work properly when they are built together. This guide covers both: what is happening to your data, why server-side tracking fixes it, how to implement it in a UK-compliant way, and what a realistic rollout looks like for a B2B marketing team.
Key takeaway: Server-side tracking achieves approximately 95% data accuracy versus the 60–80% ceiling of client-side implementations alone, according to 2026 benchmarks. The B2B teams that act now will have a lasting measurement advantage over those still waiting.
Here is what this guide covers:
Client-side tracking works by firing JavaScript tags in the user's browser and sending that data to platforms like Google Ads or GA4. For years, this was good enough. It is no longer good enough, and three forces have converged to make that true simultaneously.
Ad blocker usage has reached 1.77 billion users globally as of 2025, according to Backlinko and GWI research. On desktop specifically, more than 40% of users now run some form of ad blocking. These tools filter standard tracking paths, URLs like /gtag/, /collect/, and /matomo.php are blocked by default in most ad blocker rulesets. The result is that a meaningful portion of your B2B audience, often the most technically literate segment, is entirely invisible to your client-side tags.
Safari's Intelligent Tracking Prevention (ITP) caps first-party cookies set via JavaScript at just seven days. Mobile Safari accounts for roughly 27% of mobile traffic globally. Any prospect who visits your site, leaves, and returns after a week is effectively treated as a new, unattributed user by your client-side tracking. Research from Stape documents a 13% conversion loss attributable to Safari ITP alone.
Chrome, despite retaining third-party cookie support after Google ended the Privacy Sandbox programme, is increasingly overlaid with privacy settings and user-level blocking that erode signal quality regardless of formal deprecation.
UK and EU privacy regulations require explicit consent before most tracking cookies fire. On legally compliant cookie banners with a genuine reject option, the numbers are stark:
This means that on a fully compliant banner, the majority of your site visitors are opting out of tracking before a single tag fires. The consent rate is declining year-on-year. Client-side tracking cannot recover this data; server-side tracking, combined with Google's Consent Mode v2 modelling, can partially compensate through behavioural modelling for non-consenting users.
The combined effect is significant. A B2B SaaS company with 10,000 monthly visitors might realistically have accurate data on only 5,000–6,000 of them when ad blockers, ITP, and consent decline are all factored in. The campaigns that look underperforming may simply be underreported.
First-party data is information collected directly from your own audience through your own channels, with their explicit consent. It includes website interactions, form submissions, email engagement, CRM records, demo requests, event registrations, and any other touchpoint your business owns.
This matters because first-party data is not subject to the browser restrictions and third-party cookie deprecation that are eroding client-side tracking. It is owned, consented, and durable.
First-Party Data
Third-Party Data
The Salesforce State of Marketing, 9th Edition, which surveyed 4,850 marketing decision-makers across 29 countries, found that 84% of marketers now use first-party data as one of their primary data sources. Yet only 31% reported being fully satisfied with their ability to unify that data across platforms. Collecting first-party data is one challenge. Making it useful across your ad platforms is another.
For B2B marketers running Google Ads or LinkedIn Ads, first-party data unlocks several capabilities that third-party data cannot reliably provide:
The critical point for B2B: Most B2B conversions are not a single event. A prospect clicks an ad, reads a case study, attends a webinar, talks to sales, and converts six weeks later. First-party data, properly structured and fed back into your ad platforms, is the only way to attribute that journey accurately. Client-side tracking captures a fragment of it. Server-side tracking with first-party enrichment captures most of it.
Server-side tracking moves event processing from the user's browser to infrastructure you control. Instead of a JavaScript tag firing in the browser and sending data directly to Google or Meta, your server receives the event first, processes it, and then forwards it to your ad platforms via secure server-to-server APIs.
The architecture has three distinct layers:
analytics.yourdomain.com) rather than to Google or Meta directly
Because the initial request goes to your own subdomain rather than to a known ad tech URL, ad blockers do not recognise it as a tracking request. The cookie is set server-side from your own domain, which means Safari ITP treats it as a genuine first-party cookie with a full duration of 90–400 days rather than the seven-day cap applied to JavaScript-set cookies.
The data quality improvement is substantial. According to the JENTIS Server-Side Tracking Report 2026, average data quality improves by 41% after migration to server-side tracking. Ad blocker bypass rates approach 95% because requests originate from your own domain. Teams typically recover 18–40% of previously lost conversion data within the first quarter.
Client-Side Tracking
Server-Side Tracking
Where server-side tracking becomes genuinely transformative for B2B is in the enrichment step. Because events pass through your own infrastructure before reaching ad platforms, you can append data from your CRM at the server layer. A form submission event can be enriched with the lead's company size, industry, and CRM lead score before it is sent to Google Ads as a conversion signal.
This means your Smart Bidding campaigns stop optimising for "any form fill" and start optimising for "form fills that match your ICP." The distinction is significant for B2B teams where lead quality varies enormously and volume-based optimisation often drives the wrong results.
Server-side tracking is not a mechanism for bypassing consent requirements. This is a critical misconception that needs addressing directly. Moving tracking to your own server does not change your legal obligations under UK GDPR or the Privacy and Electronic Communications Regulations (PECR). What it does is give you better tools to enforce consent architecturally rather than relying on browser-level scripts that users can circumvent.
The Data (Use and Access) Act 2025 took effect on 5 February 2026 and introduced the most significant change to UK analytics compliance since GDPR. Under the Act, analytics cookies can now operate without prior consent under specific conditions:
This does not apply to advertising cookies or any tracking used for ad platform attribution. For Google Ads and Meta conversion tracking, full Consent Mode v2 compliance remains mandatory in the UK and EEA.
Google's Consent Mode v2 has been mandatory for EEA and UK advertising since March 2024. It works by passing consent signals to Google's systems, which then use modelling to fill gaps in measurement data for users who decline tracking. For B2B marketers, this means:
Warning: According to Secure Privacy's 2026 analysis, 67% of Consent Mode v2 implementations are not fully compliant. An incorrect implementation can suppress conversion data as badly as having no server-side tracking at all.
A properly configured server-side setup enforces compliance at the infrastructure level:
The practical benefit of this architecture is that compliance becomes a property of the system rather than a policy document. You are not relying on marketing teams to configure tags correctly every time; the server enforces the rules automatically.
Server-side tracking is a technical project, but it does not have to be a six-month one. For most B2B marketing teams, a phased rollout over four to eight weeks is realistic. The key is sequencing correctly so you do not break existing tracking while building the new infrastructure in parallel.
Before touching any tags, understand what you currently have.
tracking.yourdomain.com to your server container using an A-record (not a CNAME, which Safari ITP treats with suspicion). DNS propagation takes 24–48 hours
With the infrastructure in place, migrate your highest-value tracking first.
Realistic timeline: Most B2B marketing teams working with a developer or specialist agency complete this in four to eight weeks. ROI typically materialises within three to six months as improved conversion data feeds Smart Bidding and attribution accuracy improves.
Setting realistic expectations matters here. Server-side tracking is not a magic number inflator. It recovers data that was always there but invisible to your reporting. The improvement you see depends on how much data you were losing to begin with.
Based on data from the JENTIS Server-Side Tracking Report 2026 and industry implementations:
This is the part most coverage misses. The benefit of server-side tracking is not just better reporting. It is better campaign performance over time. Google's Smart Bidding algorithms learn from conversion signals. When those signals are incomplete, Smart Bidding makes suboptimal decisions: it bids on keywords and audiences that appear to convert but actually do not, and undervalues the ones that do convert but were previously invisible.
When you restore full conversion signal quality, Smart Bidding recalibrates. The improvement in data quality compounds into improved ROAS over the weeks and months that follow implementation. This is why the ROI timeline is typically three to six months rather than immediate.
Not every server-side implementation delivers these results. The most common failure modes are:
Server-side tracking solves the measurement problem. But the B2B teams building a genuine competitive advantage are going further: they are treating first-party data as a strategic asset, not just a tracking fix.
Every touchpoint your business owns is an opportunity to collect consented, durable first-party data. For B2B, the highest-value collection points are:
It is worth being honest about the limits of server-side tracking. According to Refine Labs research, there is a 90% gap between what software attributes and what self-reported attribution credits. In one documented case, podcasts were credited with 53% of closed-won revenue via self-reported attribution but 0% by software analytics.
Server-side tracking recovers the data that browser restrictions were hiding. It does not solve the dark funnel problem: the brand touchpoints (LinkedIn posts, word of mouth, podcast mentions, community discussions) that influence B2B buying decisions but leave no measurable footprint.
The implication for B2B marketers is that server-side tracking should be one layer of a broader attribution approach, not the entire answer. Combining it with self-reported attribution (asking prospects "how did you hear about us?" at key moments), CRM-based pipeline analysis, and periodic marketing mix modelling gives a far more complete picture than any single tracking method.
The JENTIS 2026 report positions the UK as a steady adopter, ahead of Southern and Eastern Europe but behind the DACH region and Nordics. Larger enterprises are moving fastest. Mid-market B2B companies, which describes most of the businesses running serious paid search programmes, show a mixed picture: some are accelerating adoption to gain competitive advantage, while others are still operating on client-side-only infrastructure.
The window for early-mover advantage is still open in the UK mid-market. Server-side tracking adoption among SMBs sits at 20–25% currently, with 70% adoption projected by 2027. The B2B teams that build this infrastructure now will have 12–24 months of cleaner data, better-trained Smart Bidding models, and more accurate attribution before their competitors catch up.
The gap between what your tracking reports and what is actually happening in your pipeline is not going to close on its own. Browser restrictions are tightening, consent rates are declining, and the ad blocker install base keeps growing. Every quarter you delay is another quarter of Smart Bidding learning from incomplete data.
The practical starting point for most B2B teams is a tracking audit: understanding what you are currently losing before building the infrastructure to recover it. That means pulling your current conversion data, checking your Consent Mode v2 implementation, and mapping the journey from ad click to CRM record to identify where attribution breaks down.
The businesses that will win on paid search in 2026 and beyond are not those with the largest budgets, they are those with the cleanest data feeding their campaigns. First-party data and server-side tracking are how you build that foundation.
If you want help auditing your current tracking setup and building a roadmap for server-side implementation, Lever Digital's B2B PPC team works with SaaS and tech businesses across the UK on exactly this. The conversation starts with understanding what you are currently missing.
Lever Digital is proud to be a 2026 UK Paid Media Awards finalist, recognised for outstanding performance-led paid media campaigns across B2B and SaaS.
.png)
