The Cookie Didn’t Die. Your
Audiences Still Need Better Data.

Picture of Sarah Hunt
Sarah Hunt

Sr. Director, Data Licensing & Platform Partnerships

For six years, media buyers were told the third-party cookie was about to disappear. It didn’t. Google kept cookies in Chrome, retired most of the Privacy Sandbox and moved on.
Then, in September, Apple did something nobody had on the 2026 planning calendar. With iOS 27, every browser on iPhone and iPad, Safari, Chrome, Edge and Firefox alike, began blocking domains used by some of the industry’s best-known identity and ad tech companies.
The cookie survived, but the signal underneath it keeps getting thinner. The question media buyers should be asking was never whether cookies would live or die. It’s whether the audiences you buy are built on something real.

So here’s the honest state of play: the cookie survived, but the
signal underneath it keeps getting thinner. The question media
buyers should be asking was never whether cookies would
live or die. It’s whether the audiences you buy are built on
something real.

Path2Response is a data company that builds audiences from
what people actually buy. Our data comes from 3 billion+ real
transactions across 280+ million U.S. consumers, updated
weekly.  I joined because media buyers need a genuinely different
approach, and this is the moment that proves why.

Where the cookie actually stands as of 2026

Chrome still supports third-party cookies, but a large and
growing share of your audience can’t be reached by them.
Safari has blocked third-party cookies by default for years,
Firefox blocks known trackers and isolates other cookies by
site, and Safari dominates iPhone traffic. The newest pressure
isn’t Google. It’s Apple. Apple had been heading this way
already. With iOS 26 in 2025, Safari turned on its advanced
fingerprinting protection for all browsing by default, cutting
off many tracking scripts’ access to referrer data and link
parameters.

Apple’s newest move goes further than blocking cookies. Since
iOS 27 began rolling out on September 14, a private blocklist built
into WebKit stops requests to listed domains before they ever
leave the device. Apple requires every iPhone and iPad browser
to run on WebKit, so the block covers Safari, Chrome, Edge and
Firefox alike. The block applies to cross-site requests. A request
from a brand’s website to its own domain isn’t affected, which is
one reason first-party and server-side setups hold up better.

Web pages opened inside apps, such as links tapped in Facebook, Instagram or an email app, very likely fall under it too, though that hasn’t been publicly tested. Whether Safari on a Mac is affected is unconfirmed. Chrome, Edge and Firefox on Windows, Mac and Android are untouched.
How much traffic is at stake? About 24% of U.S. web page views come from iPhones and iPads, according to StatCounter (June 2026). That’s the ceiling today, and the share actually blocked is climbing as people update to iOS 27. Roughly threequarters of U.S. web traffic, from Windows PCs, Android devices, and non-Safari browsers on Macs, isn’t covered at all.
Since iOS 27 began rolling out on September 14, a private blocklist built into WebKit stops requests to listed domains before they ever leave the device. Apple requires every iPhone and iPad browser to run on WebKit, so the block covers Safari, Chrome, Edge and Firefox alike.
The list keeps growing, and nobody outside Apple can see it. On October 2, AdExchanger reported that the original handful of blocked vendors had been replaced by a remotely updated list of hundreds of companies: customer data platforms, ad tech and martech firms, data sellers and identity graph operators. AdExchanger reports Apple can add or remove a company without an iOS update, though Digiday reported the code to do that hadn’t shipped yet, and it has published no list, criteria, or appeal process.
Date What happened Why buyers should care
Oct 5, 2026 Apple asks The Trade Desk to test an iOS 27.2 beta (PPC Land); reporting says it restores only The Trade Desk's ad delivery domain The identity companies reportedly stay blocked, so 27.2 doesn't fix the bigger issue
Oct 2, 2026 AdExchanger reports the blocklist has grown to hundreds of CDPs, ad tech, martech, data sellers and identity graph operators, updated remotely (AdExchanger) Any browser-based vendor in your stack could be added overnight, without notice
Sept 29, 2026 AdExchanger reports The Trade Desk can't serve ads on iPhone web pages under iOS 27 (AdExchanger) Open-web DSP reach on iPhone shrinks
Sept 14, 2026 iOS 27 ships; every iPhone and iPad browser stops loading domains tied to UID2, ID5, LiveRamp and others (PPC Land) Hashed-email IDs built to replace cookies now face their own blocks on iPhone
May 2026 Publicis agrees to acquire LiveRamp (PPC Land) Identity infrastructure is consolidating under agency holding companies
Nov 2025 Google sets deprecation of Topics, Protected Audience and Attribution Reporting for Chrome 144, removal by Chrome 150 (Windows Report) Cookie "replacements" many teams tested are going away
Oct 17, 2025 Google retires most Privacy Sandbox ad APIs after low adoption No browser-level substitute for interest targeting
Apr 22, 2025 Google drops the user-choice prompt and keeps third-party cookies in Chrome The deadline disappeared; the underlying problem did not
The takeaway for media buyers: identity plumbing will keep shifting under your feet. Cookies, universal IDs and browser APIs each solve for reach. None of them tell you whether the person on the other end is actually likely to buy.

What signal loss really means for audiences and custom audiences

The biggest risk isn’t losing the cookie. It’s buying audiences built on inference stacked on inference. When signal thins out, many providers fill the gaps with modeled interests, probabilistic matches and lookalikes of lookalikes. The segment name stays the same. What’s inside it gets fuzzier.
Three things happen to a media plan when that drift goes unchecked:
That’s why we tell buyers to judge audiences by conversions, not impressions or click-through alone. Clicks are a useful early read. New customers and incremental return on ad spend (iROAS) are what you’re actually paying for.
One catch: on iPhones, conversion pixels that fire from the shopper’s browser can now be cut off at the device if the vendor is on Apple’s list, and Safari’s fingerprinting protections already strip click IDs and referrer data from many tracking scripts. If your measurement relies on browser pixels, it can undercount iPhone buyers. Send conversions server-toserver instead, through a platform’s conversions API or a direct order feed, so the sale reaches your reporting whatever device it happened on.

Why purchase-based audiences hold up when signals don’t

A purchase is the one signal that doesn’t need a browser’s permission to be true. Someone either bought high-end women’s apparel last month or they didn’t. That’s ground truth. Most audience data on the market is hearsay: inferred interests and modeled demographics built to resemble reality.
A purchase is the one signal that doesn’t need a browser’s permission to be true. Someone either bought high-end women’s apparel last month or they didn’t. That’s ground truth. Most audience data on the market is hearsay: inferred interests and modeled demographics built to resemble reality.

It’s also identity that never needed a browser. Our core data – “3 billion+ transactions, postal records, and hashed email files- moves company to company, server to server, or as files.
It never passes through a shopper’s browser, so Apple’s blocklist can’t intercept it. As the open web moves identity off the device and onto servers, that kind of data becomes more valuable, not less.

Our core data—3 billion+ transactions, postal records, and hashed email files—moves company to company, server to server, or as files. It never passes through a shopper’s browser, so Apple’s blocklist can’t intercept it.

Path2Response Digital Audiences start with real purchase behavior: 3 billion+ transactions from 280+ million U.S. consumers, plus 1.5 million behavior signals a day. Data is refreshed weekly, so we see new buyers other sources won’t see for 15 to 45 days, if at all. Our identity layer links 583M+ hashed emails (HEMs) to verified postal addresses, with a recency signal that shows which identities are still active.

To be clear, no audience is immune at the point of activation. Under iOS 27, The Trade Desk’s ads couldn’t serve on iPhone web pages, and DSP reach on iPhone web inventory shrinks wherever identity calls are blocked. Apple’s blocklist doesn’t affect CTV, social platforms such as Meta, retail media, native mobile apps, desktop, or Android. What changes is the quality of the who. When targeting is based on observed buying, every impression you deliver goes to a real buyer.

Two ways to buy

Platform Custom audience pricing
Meta and social Typically 15% of media (set by the platform)
Other DSPs $1.50 CPM, tied to usage
The Trade Desk 28% of media
Path2Response never invoices you directly. You pay only when you use the audience, as part of your media buy.

It’s also identity that never needed a browser. Our core data- “3 billion+ transactions, postal records, and hashed email files- moves company to company, server to server, or as files.
It never passes through a shopper’s browser, so Apple’s blocklist can’t intercept it. As the open web moves identity off the device and onto servers, that kind of data becomes more valuable, not less.

The proof: #1 of all providers in a head-to-head test

A national fine jewelry and gifting retailer tested audience providers head-to-head in a single digital campaign. Three Path2Response buyer-category audiences reached a 2.01% peak click-through rate, all more than 5x the campaign average and within 0.16 points of each other. Path2Response ranked #1 of all providers. Next, we built a custom model around the retailer’s own buyers.
That consistency matters as much as the peak. Three different audiences landing within a fraction of a point tells you the signal underneath is stable, not lucky.

Six questions to ask every audience provider in 2027

Keep what works. Add what’s different. Measure what matters.
Are third-party cookies going away in 2026?
Not in Chrome. Google kept third-party cookies in April 2025 and retired most Privacy Sandbox ad APIs in October 2025. Safari still blocks them by default, and Firefox blocks known trackers and isolates the rest by site.
With iOS 27, released September 14, 2026, every browser on iPhone and iPad, including Safari, Chrome, Edge and Firefox, began blocking cross-site requests to domains on a private Apple list. The list started with identity providers such as UID2, ID5 and LiveRamp and has reportedly grown to hundreds of ad tech and data companies. Whether Safari on a Mac is affected is unconfirmed.
An audience built from verified purchase records, what people actually bought, rather than browsing behavior or inferred interests.
Path2Response models from a small seed audience and delivers to your seat ID on your DSP, social or CTV platform, with no model fee or onboarding cost.
28% of media on The Trade Desk, $1.50 CPM on other DSPs, and typically 15% of media on Meta and social, all paid through your media buy.
Path2Response is a performance data company that builds audiences from 3 billion+ real transactions across 280+ million U.S. consumers, refreshed weekly. It is CCPAcompliant and SOC 2 certified.

Sarah Hunt has extensive hands-on experience across digital media buying, data licensing and digital audience strategies. She understands the bottlenecks our partners face every day and will play a pivotal role in helping partners scale their audience strategies and maximize the value of their licensed data. She’ll be leading the charge in helping clients navigate modern licensing models and commercialize data to build smarter, more responsive audience connections.

Reach out directly at inquiries@path2response.com to share your ideas and insights.

Achieve breakthrough results to thrill your clients.

Learn how our clients achieve game-changing results.