Open Tracked/Troubleshooting/Cookieless advertising strategies and solutions

Cookieless advertising strategies and solutions

When cookies fail, ad platforms lose the link between ad and sale. The fix is first-party data, server events and honest measurement.

Start free Jump in ↓

5 min read · Updated October 26, 2026

In this guide

Symptoms and fixes A cookieless plan in five steps What to stop doing A worked example Terms you will see Which fix first?What to ask your agency or tool vendor Realistic expectations Frequently asked questions

Check these first

Ads suffer when cookies expire or are blocked: audiences shrink and conversions go unattributed.
The fixes are the same four moves: server-sent events, server-set cookies, first-party identifiers and your own measurement.
Platform dashboards will under-count. Use store revenue as the truth.

Cookieless advertising is not a product. It is what advertising looks like when cookies cannot be relied on. For the background read cookieless tracking. This page is about what to do when you see the symptoms: fewer conversions in Meta and Google Ads than in your store, smaller retargeting audiences and a longer learning period.

Symptoms and fixes

SymptomConversions in the ad platform are lower than store orders

Likely causeCookies or click IDs are lost between the ad click and the purchase.

FixSend purchases from the server with the Conversions API and Google Ads conversions, with hashed e-mail and phone. See Conversions API explained.

SymptomReturning Safari visitors look new

Likely causeScript-set cookies expire after a few days.

FixSet cookies from your server, and restore them. Open Tracked's Cookie Keeper (all plans) remembers them on your server under a hash of a customer identifier. See Safari ITP.

SymptomRetargeting audiences are shrinking

Likely causeThe platforms cannot recognise visitors across sessions.

FixBuild audiences from customer lists (hashed e-mail and phone) and from server events. See customer lists in Google Ads.

SymptomClick IDs disappear from the landing page

Likely causeA browser or privacy tool strips gclid or fbclid.

FixCapture the click ID server-side on the first request, and use a custom parameter you control. See Safari removes click identifiers.

SymptomAttribution reports disagree

Likely causeEach platform models a different view of the same conversion.

FixUse blended numbers: total revenue divided by total spend, and a CRM or store source of truth.

For online stores

Orders from your store, back to the ad that earned them

Your store sends the order once. Open Tracked passes it on to each ad platform, cleaned and deduplicated.

A cookieless plan in five steps

Server-side events

Move purchase and lead events to a server container and send them with the platform APIs.

Longer-lived cookies

Use your own subdomain and a way to restore cookies.

First-party data

Ask for e-mail and phone at checkout and in lead forms with consent.

Audience lists

Upload and refresh customer lists in each platform.

Measure independently

Track spend, revenue, ROAS and profit in your own analytics.

What to stop doing

Judging campaigns only by the last-click numbers inside one platform.
Relying on a single cookie for the whole journey.
Waiting for a browser change before you act.

0 of 5 done

Server events are live for purchase and leadA shared event ID deduplicates browser and server copiesCookies are set or restored from my own domainCustomer lists are uploaded to each platformI compare platform numbers with store revenue weekly

Open Tracked covers the first three on every plan: server container, Cookie Keeper and the Data Store with the Enricher. Its analytics product covers the fifth.

Ask AI

Ask Ari instead of digging through reports

Ari reads your tracking and ad data and answers in plain words.

A worked example

A shop has 1,000 orders a month, 40 percent from iPhones. Meta shows 620 purchases and the retargeting audience for website visitors has shrunk by a third. The shop adds server purchase events with hashed e-mail, restores cookies from its own subdomain and uploads its customer list. A month later Meta shows about 800 purchases and the audience is back to its old size. These figures are illustrative. Compare your own platform and store numbers before and after.

Terms you will see

Click ID: A value added to an ad link, such as gclid, that ties a sale to an ad.
Modelled conversion: A conversion estimated by the platform when it cannot see the full path.
Customer list: Hashed e-mail and phone numbers uploaded to build an audience.
Blended ROAS: Total revenue divided by total ad spend across channels.
First-party data: Data you collect yourself from your own visitors and customers.

Which fix first?

If you have	Do this first	Then
Pixel only	Add server events with a shared event ID	Cookie restore, customer lists
Pixel and server events	Raise match quality with hashed e-mail and phone	Cookie restore, audience refresh
A good server set-up	Measure independently with your own analytics	Test profit-based bidding

What to ask your agency or tool vendor

0 of 5 done

How do you recover purchases when the browser loses the cookie?Which identifiers do you send with each event?How do you respect consent in the server container?How do you check that platform numbers match store orders?What happens to my data and my containers if I leave?

Realistic expectations

Cookieless fixes narrow the gap between the ad platform and your store. They do not close it completely. Some visitors block everything, some decline consent, and some buy on a device the platform never saw. Aim for a gap you can explain and a trend that improves, not a perfect match.

The short version

3 things to remember

Scroll and the points stack up.

Ads suffer when cookies expire or are blocked: audiences shrink and conversions go unattributed.

The fixes are the same four moves: server-sent events, server-set cookies, first-party identifiers and your own measurement.

Platform dashboards will under-count. Use store revenue as the truth.

Frequently asked questions

What is cookieless advertising?

Running ads without relying on third-party cookies, using first-party data, server-sent events and modelling instead.

Do I need to stop using the Pixel?

No. Keep it, add server events and share an event ID.

How do I rebuild audiences?

From customer lists and server events: hashed e-mail and phone uploaded to Meta, Google and TikTok.

Is it enough to wait for the platforms to model?

Platform modelling helps but cannot replace missing identifiers. Collect first-party data.

Where does consent fit?

Everything above still needs a lawful basis. Respect the visitor's choice.

Do I need spreadsheets to read my results?

No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.

Is Open Tracked different from Open Track or Open Space Track?

No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.

Fix your tracking at the source

Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.

Start free More in Troubleshooting →

Written by

The Open Tracked team

We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?

Write to us Read the docs

Was this article helpful?