Identity Resolution Without Cookies: Stitching the Customer Journey
Cookies are dead. Identity resolution without cookies requires causal inference, not guesswork.
Three platforms, three answers, one budget to defend. Your GA4 export already holds the answer, and the first finding is free and never leaves your browser. Get your first finding free
By Joris van Huët, Founder & CEOUpdated 5 min read
Run the numbers for your store: the free customer journey credit calculator.
Identity Resolution Without Cookies: Stitching the Customer Journey
Cookies are dead. The obituary was written the day Safari and Firefox blocked third-party trackers. Google’s 2024 phase-out of third-party cookies in Chrome just nailed the coffin shut. If your identity resolution still relies on cookies, you’re stitching a customer journey with duct tape and hope.
Here’s the truth: Identity resolution without cookies isn’t a technical tweak.
Why Cookie-Based Identity Resolution Was Always a Lie
Cookie-based identity resolution promised a unified customer view. It delivered a fragmented mess.
The lie wasn’t the technology. It was the assumption that a tiny text file could capture human behavior. Humans don’t behave in linear, cookie-sized chunks. They switch devices, delete data, use incognito mode, and log in and out of accounts. Cookies were never designed for that chaos. They were designed for static web pages, not dynamic, multi-touch, multi-device journeys.
The Cookieless Identity Resolution Playbook: What Doesn’t Work
1. Probabilistic Matching: Guesswork in a Fancy Suit
Probabilistic matching uses IP addresses, user agents, and timestamps to “guess” if two devices belong to the same user. It’s like playing Clue with half the board missing.
- A family of four on one Wi-Fi? Congrats, you’ve just merged four people into one “user.”
2. Deterministic Matching: The Walled Garden Illusion
Deterministic matching relies on logged-in data: emails, phone numbers, or social logins. It works great if you’re Meta or Google and own the login ecosystem. For everyone else?
- Problem: You’re solving identity resolution for the minority while ignoring the silent majority. That’s not a strategy. That’s surrender.
3. Universal IDs: The Privacy Nightmare
Universal IDs like UID2 or RampID promise a single identifier across the web. They’re also a privacy lawsuit waiting to happen.
- Plus, they don’t solve cross-device attribution: they just move the cookie problem to a different bucket.
See also: Building Your Attribution Stack Without Cookies: A Technical Blueprint
1. Stitch Journeys with Causal Inference, Not Identifiers
Causal inference doesn’t need a single identifier to stitch a journey. It looks for behavioral patterns that indicate the same person is behind multiple devices. For example:
- A user searches for “best running shoes” on mobile, then adds a pair to cart on desktop 2 hours later.
- A user watches a product video on YouTube, then visits the brand’s site via a direct search 3 days later.
These patterns aren’t random.
2. Use First-Party Data as a Signal, Not a Crutch
First-party data (emails, purchase history, CRM data) is valuable, but it’s not enough.
- Temporal patterns: Time of day, day of week, and latency between actions.
- Content affinity: The topics, categories, and products a user engages with.
- Channel behavior: How a user interacts with email, social, search, and direct traffic.
These signals create a behavioral fingerprint that’s unique to each user, even without a persistent identifier. It’s not about who the user is. It’s about what the user does.
3. Solve the Cross-Device Attribution Problem with Incrementality
Cross-device attribution isn’t about stitching devices. It’s about measuring incremental impact: the lift in conversions that wouldn’t have happened without a specific touchpoint. Here’s how causal inference does it:
- Define control and test groups based on behavioral patterns, not identifiers.
- Measure lift in conversions for users exposed to a touchpoint vs. those who weren’t.
- Attribute incrementality to the touchpoint that caused the lift, regardless of device.
This isn’t correlation. It’s causal proof. And it works even when devices aren’t stitched together.
The Future of Identity Resolution: Behavioral Graphs, Not Identity Graphs
The next evolution of identity resolution isn’t an identity graph. It’s a behavioral graph: a dynamic, privacy-safe map of how users interact with your brand across devices, channels, and time.
Here’s what a behavioral graph looks like:
- Nodes: Actions (clicks, views, purchases, searches).
- Edges: Causal relationships between actions (e.g., a search led to a view, which led to a purchase).
- Clusters: Groups of actions that belong to the same behavioral fingerprint.
Behavioral graphs don’t rely on cookies, logins, or universal IDs.
How to Implement Cookieless Identity Resolution Today
Ready to ditch cookies for good? Here’s your playbook:
Step 1: Audit Your Current Identity Resolution
- What percentage of your users are stitched via cookies?
- What’s your cross-device attribution accuracy? (If you don’t know, it’s probably bad.)
- How much revenue is misattributed due to identity gaps?
Benchmark: If your cross-device accuracy is below 50%, you’re leaving money on the table.
Step 2: Replace Probabilistic Matching with Causal Inference
- Stop guessing.
- Use behavioral patterns (temporal, contextual, channel) to stitch journeys.
- Layer first-party data with behavioral signals for higher match rates.
Step 3: Measure Incrementality, Not Attribution
- Shift from “who clicked?” to “what caused the conversion?”
- Run incrementality tests to measure lift from cross-device touchpoints.
- Attribute revenue to the touchpoints that drove real impact.
Step 4: Build a Behavioral Graph
- Map actions (nodes) and causal relationships (edges) across devices.
- Cluster actions into behavioral fingerprints.
- Use the graph to predict and influence future behavior.
Resource: Learn more about causal inference and behavioral graphs.
The Bottom Line: Identity Resolution Without Cookies Is Here
Cookies are dead. Identity resolution isn’t.
The tools exist. The proof is in the data. The only question is: Are you still stitching journeys with duct tape, or are you ready to build something that lasts?
FAQs
Is identity resolution without cookies GDPR-compliant?
Yes.
Ready to Ditch Cookies for Good?
See how it works for your brand.
Sources and Further Reading
Related Articles
Go deeper: Incrementality testing, explained.
Sixty-second versions of these ideas: Causality Engine on YouTube Shorts.
Have an audience of ecommerce operators? Earn 20% recurring commission by recommending the €99 read.
Keep reading
Terms in this article
- AttributionAttribution identifies user actions that contribute to a desired outcome and assigns value to each. It reveals which marketing touchpoints drive conversions.
- Causal InferenceCausal inference is the set of methods for estimating how much an outcome changes because of a cause, rather than alongside it. It works by comparing what happened with an estimate of what would have happened without the cause.
- Customer journeyCustomer journey is the path and sequence of interactions customers have with a website. Customers use multiple devices and channels, making a consistent experience important.
- Customer Journey MappingCustomer Journey Mapping is the process of visually representing the customer's path. It clarifies and improves the customer experience across all touchpoints.
- Direct TrafficDirect Traffic refers to website visitors who arrive by typing the URL directly into their browser or through bookmarks. They do not come from search engines or referrals.
- Identity ResolutionIdentity Resolution connects and matches customer data from various sources. It creates a single, unified view of each customer.
- IncrementalityIncrementality is the part of an outcome, such as orders or revenue, that a marketing activity caused: the extra results compared with what would have happened without it. It is a causal effect, not the number of conversions credited to a channel.
- Third-Party CookieThird-Party Cookie is a cookie set by a domain other than the one a user currently visits. These cookies track users across sites for advertising.