Why every ad platform claims the same sale

Open your Google Ads, Meta and TikTok dashboards on the same day and add up the revenue each one reports. The total is almost always more than your store actually took. That is not a bug in any one platform. It is what happens when three separate scorekeepers each count a sale they touched. This post explains why the numbers overlap, what the platforms cannot see at all, and how a pixel on your own domain gives you one count you can plan spend on.

Three referees, one goal

Picture a shopper. She sees a TikTok video on Monday. On Wednesday she searches for the product and clicks a Google Shopping ad. On Friday a Meta retargeting ad reminds her, and she buys that night.

Each platform saw a real click from a real person who later bought. Each platform has a rule that says "if someone clicks our ad and buys within our window, count it." So TikTok counts the sale. Google counts the sale. Meta counts the sale. One order, three conversions.

Nobody is lying. The platforms are each answering the question "did we touch this buyer?" and the honest answer is yes. The question you need answered is different: "which of these touches earned the money, and where should the next dollar go?" No single platform can answer that, because none of them can see the other two.

What the platforms cannot see

The overlap is the well-known half of the problem. The less-known half is everything the platform tags miss.

A platform tag is a small script that runs in the shopper's browser. It only works when the browser lets it. Several things get in the way:

• Ad blockers and browser privacy settings. Many blockers filter third-party ad scripts by default. The click happened, but the tag that would record the purchase never loads.
• Consent banners. If your banner puts the ad tags in a category most visitors decline, the tag is withheld for those visitors. The order still happens. The platform never hears about it.
• Device switches. Research on a phone at lunch, buy on a laptop at night. To a browser tag those are two strangers.
• Slow buyers. Some products are bought the same day. Others are researched for weeks. A platform's default lookback window closes long before some orders arrive.
• Orders outside the browser. Phone orders, point-of-sale, draft orders your team enters. The tag never sees them.

When the tag misses an order, the platform either takes no credit (and its bidding learns that the campaign "does not convert") or the order gets assigned to "direct" in your analytics. Both push your budget in the wrong direction.

What "first-party" actually means

A first-party pixel is a tracking script served from your own store domain rather than from an ad network's domain. It records the shopper's visit as part of your site, not as a third party watching your site.

That single change matters for three reasons:

1. It is not treated as an ad tracker by default. Blockers and privacy settings target third-party scripts. A script on your own domain, on a neutral path, is treated like the rest of your site.
2. It captures the click IDs the platforms leave behind. When a Google, Microsoft, Meta or TikTok ad sends someone to your site, the landing URL carries a click identifier. The pixel records it on arrival, so the source is known even if the platform's own tag never fires.
3. It sees the whole journey, not one platform's slice. Monday's TikTok visit, Wednesday's Google click and Friday's Meta click land in one record for one visitor.

Orkie's Pixel adds a second piece: a server-side copy of every order from Shopify or BigCommerce. The order arrives from the store platform, independent of the browser. So an order is never lost because a tab closed early or a blocker fired. The browser record and the order record are joined by identity, using the email, phone or customer ID at checkout, and the same identity joins the phone session to the laptop session.

One order, credited once

Once every touch and every order sit in one place, attribution becomes a choice you make rather than a fight between dashboards. The Pixel shows the same orders under several models side by side:

The order in the example above shows up once under every model. Under first click it belongs to TikTok. Under last click it belongs to Meta. Under position-based, TikTok and Meta share most of it and Google gets a slice. You can see all of that on one page, against the same verified revenue, with ad spend counted once beside it.

That is the difference. The platforms each give you their number. The pixel gives you your number, and lets you look at it from several angles.

Why this changes what you do next

Say your store does $3 million a year and spends on Google Shopping, Meta and TikTok. Say each platform reports a return on ad spend of 4. Add them up and the platforms claim more revenue than you booked. You cannot tell which one to cut.

With a first-party record, you might find that TikTok opens a lot of journeys but rarely closes them, that Google closes most of what TikTok opened, and that Meta retargeting is mostly claiming buyers who were already on the way. That picture supports a real decision: keep TikTok as a prospecting line, protect Google Shopping, and trim the retargeting budget. The platform dashboards could never have shown you that, because none of them can see the others.

The pixel also fixes the second problem, the missed orders. Verified orders can be sent back to Google, Microsoft, Meta and TikTok as enhanced or offline conversions, so each platform bids on your real sales rather than the subset its own tag happened to catch. That is a topic for another post. The short version: the platform's number starts to match yours.

Where to start

The Pixel is the first thing installed in every Orkie workspace, before a campaign is touched or a feed is built. Everything else reads it. Let it run for a few weeks, look at your own journeys under a few models, and make the next budget decision with those numbers in front of you.

Ready to see one number instead of three? Talk to us.

---

Want this for your business? Talk to us How the pixel works