Identity-first personalization has nothing to say to the anonymous 90% of your traffic. You don't need to resolve who someone is to act on what they're doing right now.
The dominant story in martech for fifteen years has been identity. Build the profile. Stitch the devices. Resolve the anonymous visitor to a known person, ideally before they convert, so you can personalize against everything you know about them.
It's an appealing story. It's also why most personalization projects stall for eighteen months before they show a dollar of return — and why a huge share of your traffic never gets personalized at all.
Most of the people on your site are anonymous. They haven't logged in, they aren't in your CRM, and the cookie that was supposed to follow them around is increasingly being eaten by the browser before you can use it. The identity-first stack has almost nothing to say to these visitors, because its whole model depends on first answering who is this?
But here's the thing: you don't actually need to know who someone is to know what they're doing. Someone who lands on a comparison page, scrolls slowly, hovers on pricing, and bounces to the FAQ is telling you something useful right now — regardless of their name, email, or lifetime value. The behavior in this session is the signal. Identity is a slower, more expensive proxy for it that often arrives too late to matter.
Strip out the jargon and it's simple. Instead of asking "what do we know about this person from the past," you ask "what is this person showing us in the present." You score the behavior as it happens — pages, dwell, sequence, intent signals — and you decide what to show based on that. No profile required. No identity graph. No warehouse query.
This isn't a worse version of identity-based personalization. For anonymous traffic, it's the only version that works, because there's no identity to resolve in the first place.
A fair question: if behavior in-session is enough, why did the industry build the CDP / identity-graph / data-warehouse cathedral?
Two honest reasons. First, some use cases genuinely need it — lifecycle email, loyalty, anything that spans sessions and channels over time. That's real. Second, and less flattering: the heavy stack is sold by people whose business model is the heavy stack. A multi-month identity-resolution implementation is a much bigger contract than "drop a tag, start deciding." The complexity isn't always for your benefit.
So the question to ask isn't "do I need a CDP?" It's "do I need a CDP for this?" For converting anonymous in-session traffic — which is most of your traffic — the answer is usually no. You're being sold a cross-session identity solution for an in-session behavioral problem.
AXO does in-session behavioral decisioning and nothing about identity. There's no CDP to stand up, no identity graph to maintain, no data warehouse on the critical path. A lightweight tag scores behavior client-side and decides what to show, in the session, for the anonymous visitor you'd otherwise have ignored.
That's a deliberately small footprint. It means AXO won't run your loyalty program — and isn't trying to. It means the time-to-first-value is measured in days, not quarters, because there's no identity scaffolding to build before anything works.
If you take one thing from this: separate the cross-session, known-customer problems from the in-session, anonymous-visitor problems. They want different tools. Buying the cathedral to solve the second one is how good teams spend a year and a seven-figure budget personalizing for the 10% of traffic they already had figured out.
Yes. Most personalization for anonymous traffic does not require knowing who the visitor is — it requires reading what they are doing. In-session behavioral signals (pages viewed, scroll depth, dwell time, sequence) are enough to score intent and decide what to show, with no login, no CRM record, and no cookie-based identity.
Not for in-session personalization of anonymous traffic, which is most traffic. A CDP solves cross-session, known-customer problems: lifecycle email, loyalty, multi-channel orchestration. Converting the anonymous visitor currently on your site is an in-session behavioral problem, and a CDP adds months of implementation without improving that decision.