+61 3 8652 4781 targetadsolutions@gmail.com 70 Kent St, Deakin ACT 2600
Mon–Fri, 9:00–18:00 AEST Booking new accounts
Journal · Tracking & Data 6 min read 14 Oct 2026
Tracking & Data

Retargeting after cookies:
what still works in 2026

Third-party cookies are dying, privacy laws are tightening — yet remarketing still works, just differently. Here's the first-party stack we build for every client now.

Liam O'Connor, tracking specialist
Liam O'Connor · Tracking & Data Lead
14 Oct 2026 · 6 min read
Diagram of first-party data flow between site, CRM and ad platforms The post-cookie stack, drawn once, reused daily

Every year someone writes the 'remarketing is dead' post. Every year it isn't — it just keeps moving to higher ground. The 2026 version: third-party cookie audiences are thin, but first-party remarketing is stronger than ever if your plumbing is right.

What actually still works

Site pixel audiences — first-party cookies set by your own domain aren't going anywhere. Meta's CAPI and Google's enhanced conversions recover most of the signal that browser-side pixels lost.

Platform-engagement audiences — people who watched your videos, saved your posts or messaged your page live inside Meta and Google's walls. Zero cookies involved, remarkably effective.

CRM lists — your email list uploaded as a matched audience. Highest-intent pool you own, and most clients never sync it.

Contextual & first-party programmatic — DV360's contextual targeting and publisher first-party segments replace what behavioural third-party data used to do.

The plumbing that matters

  • Server-side tagging (CAPI, Enhanced Conversions) — non-negotiable now.
  • Consent mode v2 configured properly — it's also a legal requirement in the EU.
  • CRM sync on a schedule, not a one-off CSV from 2023.
  • Exclusion lists for converters — nothing wastes spend like re-selling a buyer.
Good remarketing in 2026 looks less like surveillance and more like a CRM with an ad budget.

The honest limitation

Cross-site identity is genuinely weaker. Lookalike pools are smaller, frequency is harder to control across platforms, and attribution windows are shorter. The fix isn't nostalgia — it's building sequences on the pools you can still measure.

Consent mode configuration screen in tag manager

We map every client's remarketing pools before recommending spend — the stack matters more than the budget.

In one breath
  • First-party pixels + CAPI still work fine
  • CRM lists are the highest-intent pool you own
  • Consent mode v2 is table stakes
  • Contextual replaces third-party behavioural

Want this done for you?

This is literally our day job. Free 15-minute account teardown — no deck, no drip sequence.

Get the audit
Liam O'Connor, tracking specialist portrait
Written by

Liam O'Connor

Builds server-side tracking and consent setups for every TAS client. Writes about measurement because he's the one fixing it when Meta's numbers don't match the CRM.

Follow-up questions

People also ask

Third-party cookie audiences are marginal now, but first-party cookies — set by your own domain — still work and aren't going away. Most remarketing pools (site visitors, engagers, CRM lists) are built on those, not third-party tracking.

If you have any EU traffic, yes — Google requires it for remarketing features and it's a legal necessity under GDPR. For AU-only traffic it's still best practice; we'll set it up either way.

Roughly 5,000 monthly site visitors for Meta/Google pools, or 3,000+ emails for CRM matched audiences. Below that, the budget is better spent generating the traffic that fills the pool.
Server-side tagging architecture sketch CAPI + enhanced conversions = the new plumbing

Is your remarketing stack post-cookie ready?

We'll audit your pixels, consent mode and audience pools — and show you exactly which warm audiences you're losing today.