Cookieless is not a future state you prepare for — it is the current state for a significant portion of your audience. Safari and Firefox have blocked third-party cookies by default for years. Consent rejection rates in CMP-heavy markets mean even Chrome users are often untracked. The tactics in this article are not hedges against a hypothetical future: they are fixes for measurement that is already broken today.
First-Party Data: The Foundation
First-party data is information collected directly from interactions with your own properties: CRM records, form submissions, newsletter sign-ups, purchase histories, logged-in user behaviour. Unlike third-party data sourced from external brokers or cross-site tracking, first-party data is collected with clear consent from a direct relationship — making it both the most legally defensible and the most durable signal available to marketers.
For B2B marketers, strengthening first-party data means building or improving the mechanisms that convert anonymous visitors into known contacts: gated content, product demos, free tools, webinar registrations, and any interaction that gives a prospect a reason to identify themselves. The quality of your first-party data — accuracy, recency, completeness — becomes a direct competitive advantage as third-party signals degrade.
A consistent data model is critical. First-party data siloed across a CRM, an email platform, a web analytics tool, and an ad platform produces fragmented signals that are hard to act on. A customer data platform (CDP) or even a well-structured data warehouse can unify these streams around a single customer identifier. For a comparison of CDP options suited to B2B, see our guide to the best CDPs for B2B.
Zero-Party Data: Direct Signals from Intent
Zero-party data refers to information a prospect or customer voluntarily and explicitly shares with you — not inferred from behaviour, but stated directly. Examples include preference surveys, "what are you looking for today" flows, product recommendation quizzes, or explicit feedback forms asking about purchase intent and timeline.
This category of data has grown in importance precisely because it bypasses the inference problem: you do not need to guess whether someone is in-market for a product when they have told you so directly. The challenge is designing collection mechanisms that feel valuable to the user rather than extractive. Useful exchange is the key: the user shares context in return for a more relevant experience, a personalised recommendation, or a resource matched to their stated needs.
Server-Side Tagging: Reclaiming Signal
Traditional client-side tracking relies on JavaScript tags running in the user's browser, where they are vulnerable to ad blockers, browser privacy settings, ITP, and tag failures caused by slow connections. Server-side tagging moves data collection to a server you control — typically a cloud environment or a managed container provided by a tag management vendor — before forwarding signals to ad platforms and analytics tools.
The practical benefits are significant: server-side tags are not blocked by browser-level restrictions, they reduce page load overhead by consolidating third-party scripts, and they give you control over what data is sent to which vendor. You can strip personally identifiable information before forwarding to platforms that do not need it, reducing data sharing exposure.
Implementation requires more technical investment than dropping a pixel on a page, but server-side containers from Google Tag Manager (via a cloud-hosted sGTM container) and other tag management platforms have made this progressively more accessible. The measurement gains — particularly in capturing conversions that would otherwise be lost to ad blockers or consent rejection — make it one of the highest-return cookieless investments for most advertisers.
Google Consent Mode v2 and Modeled Conversions
Google Consent Mode v2 is now required for EEA traffic in any Google Ads or Google Analytics 4 setup. When a user declines consent through your CMP, Consent Mode fires cookieless pings — tags that do not set cookies or read identifiers — and Google's models use these signals along with aggregated patterns from consented users to estimate the conversions that occurred in the non-consenting population.
The result is that your reported conversion volumes in Google Ads and GA4 are higher than what pure cookie-based tracking would show — and closer to reality. Advertisers who have not implemented Consent Mode v2 see a deflated conversion count that makes their campaigns appear less efficient than they are, leading to bidding decisions that under-invest in what is actually working.
Modeled conversions are not a perfect replica of deterministic measurement, but they represent a meaningful and practically accessible improvement over having no signal at all for non-consenting users. The accuracy of the model improves with scale, so higher-volume advertisers tend to see better modeled results.
Data Clean Rooms: Matching Without Sharing
Data clean rooms are secure environments where two or more parties can run queries against matched datasets without either party being able to see the other's raw data. In an advertising context, this allows an advertiser to match their CRM records against a publisher's or platform's user data to measure reach, frequency, and outcomes — without exposing customer PII to the platform or vice versa.
Google Ads Data Hub, Amazon Marketing Cloud, and similar clean room offerings from major platforms provide this capability within their ecosystems. Independent clean room solutions allow cross-platform matching. For B2B marketers, clean rooms open up measurement of campaigns running on platforms like LinkedIn where deterministic match rates using third-party cookies were always limited — and offer a path to understanding cross-platform customer journeys without depending on shared cookies.
Clean rooms are not a day-one implementation for most teams, but understanding how your measurement strategy might incorporate them is increasingly relevant as first-party data becomes the primary currency of digital advertising.
Putting It Together
No single tactic replaces everything third-party cookies provided. The cookieless measurement stack is an ensemble: Consent Mode v2 handles the consented/non-consented split in Google's ecosystem, server-side tagging recovers signal lost to client-side blocking, first and zero-party data build the CRM foundation that underpins your owned measurement, and clean rooms enable cross-platform attribution where appropriate. For a structured approach to setting up attribution across these layers, see our guide to attribution without cookies. For a deeper look at what these methods replace, our pillar on marketing attribution explained covers the fundamentals.
Frequently Asked Questions
Is server-side tagging GDPR compliant?
Server-side tagging is a data collection architecture, not a legal basis for processing. You still need valid consent for cookies and tracking under GDPR (or equivalent regulations). What server-side tagging changes is where data flows and how resistant collection is to browser blocking — not the legal framework that governs it. This article does not constitute legal advice.
What is the difference between first-party and zero-party data?
First-party data is observed or inferred from user behaviour on your own properties (page views, clicks, purchase history). Zero-party data is explicitly volunteered by the user — survey answers, stated preferences, self-declared intent. Both are collected in a direct relationship, but zero-party data carries higher stated certainty because it is not inferred.
Do I need a CDP to implement cookieless tactics?
No — many cookieless improvements can be made without a CDP. Consent Mode v2 and server-side tagging are implementation changes to your tag setup. A CDP becomes valuable when you have enough first-party data volume and sources that unification and activation require dedicated tooling.
Audit your cookieless readiness
Hatch's free plan tool helps you identify which cookieless tactics are highest priority for your specific setup — from Consent Mode gaps to server-side tagging opportunities.
Free Plan Tool