Why cookie-based personalization broke
The identity-tracking stack has been losing its substrate for years: Safari and Firefox block third-party cookies outright, tracking prevention truncates first-party cookie lifetimes, ad blockers strip the tags, and privacy regulation makes the consent cost of cross-site identity higher every cycle. Personalization built on "recognize this person from their trail" degrades with each of those — quietly, which is worse, because the segments keep firing on the shrinking share of traffic they can still see.
What replaces the cookie
Behavior, read live. The current session's signals — pages, scroll, dwell, sequence — are enough to score intent and choose an experience, and none of them require knowing who the visitor is or where else they've been. The signal is generated on your site, used on your site, and dies with the session.
Taken to its limit, this architecture supports zero-PII operation: AXO's passive mode disables every PII-ingesting path server-side while anonymous scoring, personalization, and holdout measurement keep working — a configuration regulated industries can pilot without a data-protection fight.
QUESTIONS PEOPLE ASK
Does cookieless personalization work in Safari?
Yes. Because it does not depend on third-party cookies or long-lived identifiers, in-session behavioral personalization is unaffected by Safari's Intelligent Tracking Prevention and similar browser protections. The signals it uses are generated during the current visit, which no tracking-prevention mechanism removes.
Is cookieless personalization the same as contextual targeting?
No. Contextual targeting adapts to the content of the page — showing running-shoe ads on a running article — and treats every visitor to that page identically. Cookieless personalization adapts to the individual visitor's behavior within their session, so two visitors on the same page can see different experiences based on what each has actually done.
How does cookieless personalization affect consent requirements?
Collecting less lowers the stakes: with no third-party cookies, no cross-site tracking, and optionally zero PII, there is far less for a consent framework to govern. Specific obligations depend on jurisdiction and configuration, so consent decisions belong with your counsel — but the review starts from "we read anonymous in-session behavior" rather than "we build identity profiles," which is a materially easier conversation.