Open Tracked/Guides/Meta omnichannel ads playbook

Meta omnichannel ads playbook

A playbook for retailers: do the data work first, then the campaign, then the measurement.

3 min read · Updated October 26, 2026

In this guide

1. Catalogue 2. Online events 3. Store sales 4. Campaigns 5. Testing 6. Weekly checks Common problems A realistic example Frequently asked questions

Before you start

Do the data work first: catalogue, online events, store sales with matching data.
Then set up campaigns, run a holdout test and review weekly.
Check Meta's current campaign types before you start.

This is the practical companion to Meta omnichannel ads: a checklist you can work through. Product names change, so confirm the details in Meta's documentation. It also leans on offline conversions, Facebook ad optimisation and lift studies.

1. Catalogue

0 of 4 done

The catalogue feed is complete and currentProduct IDs match the IDs in your eventsPrices and availability are rightStore inventory is included if you advertise local availability

Set up in minutes

Connected in minutes

Add your domain, install the pixel, connect your ad platforms and watch the first events land.

2. Online events

0 of 4 done

Pixel and Conversions API send ViewContent, AddToCart and Purchase with content IDsEvent IDs are sharedEvent match quality is healthyConsent is respected

3. Store sales

0 of 6 done

Customer identifiers are captured at the till with consentSales are exported or streamed with order ID, time, amount and product IDsE-mail and phone are normalised and hashedEvents use an offline action sourceOnline and store sales share stable IDs for deduplicationMatch rate is monitored

Live view

Watch events arrive, live

A sample feed. In Open Tracked you see the same stream for your own store.

4. Campaigns

0 of 4 done

I confirmed the current omnichannel campaign type in Ads ManagerOptimisation targets sales across channels where availableBudgets reflect both channelsCreative covers online and local offers

5. Testing

Choose a holdout

A set of regions without the campaign, or a platform lift test.

Run for several weeks

Avoid sales events.

Compare store and online sales

In test and holdout regions.

Calculate incremental profit

Including store margins.

6. Weekly checks

0 of 5 done

Offline match rate and event volumeOnline purchases against shop ordersStore sales sent against point-of-sale totalsCreative performance and fatigueBudget pacing

Common problems

SymptomStore events do not match

Likely causeNo customer data at the till.

FixStart a loyalty or e-receipt programme with consent.

SymptomDouble counting

Likely causeA sale is sent online and in store.

FixUse stable IDs.

SymptomCatalogue mismatch

Likely causeIDs differ.

FixFix the feed or the events.

SymptomResults are unclear

Likely causeNo holdout.

FixRun a regional test.

Open Tracked's tagging server can receive point-of-sale data by webhook on your own subdomain and send it to Meta with the same matching logic as online events, and its analytics shows spend, revenue and profit by channel.

A realistic example

A retailer works through the playbook in order. Week one: it fixes its catalogue IDs so they match its events. Week two: it checks online event quality and sets deduplication. Week three: it connects its point-of-sale export to a tagging server, which hashes customer data and sends store sales to Meta with stable IDs. Week four: it sets up the campaign and a regional holdout. After six weeks it reviews the holdout result, calculates incremental profit and decides to scale in the regions where the lift was strongest. By following the order, the team avoided the common mistake of launching the campaign first and then discovering that it could not measure what the campaign did.

Works worldwide

Runs on your domain, anywhere

Your tracking runs on your own domain, so a visit from any country is handled the same way.

Frequently asked questions

What is an omnichannel ads playbook?

A step-by-step plan for connecting online ads to store sales, from data to measurement.

Where do I start?

With the catalogue, online events and store sales data, before the campaign.

How do I test impact?

With a regional holdout or a platform lift test.

How do I avoid double counting?

Use stable IDs across online and store sales.

Can a tagging server help?

Yes. It can receive point-of-sale data and send it to Meta with matching data.

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 Guides →

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?