Why the pixel alone is not enough

Short answer:because the pixel runs inside your customer’s browser, which is not under your control. iOS privacy settings, Safari and ad blockers each cut into the events before they reach the platform. The fix is to send the event from your server directly, in parallel with the pixel, with duplication prevented between the two.

What actually happens

The pixel is a line of JavaScript that runs on the customer’s device. Everything between you and the platform passes through their browser, so anything that gets in the way gets in the way of your data.

• iOS privacy settings. Since 2021 users are asked directly whether to allow tracking, and the opt-in rate has settled at roughly a quarter.
• Safari. Apple documents this itself: any visit arriving from an ad link carries an identifier, and Safari caps the life of the cookie on that visit at 24 hours. So if your customer clicks the ad today and buys three days later, the seven-day attribution window you think you have does not exist on Safari at all.
• Ad blockers. Roughly a third of internet users run one, and they stop the pixel before it even loads.

A Saudi agency wrote in April 2026 that “the pixel alone loses 20 to 40% of events”. On merchant forums the recurring question is almost word for word: Facebook Ads is recording purchases and there are no orders in the store, or the reverse.

The real damage is not in the report

This is the part most people miss.

If the problem were simply that your reports are incomplete, it would be manageable. You would know the number is understated and work around it. What actually happens is worse: the platform’s algorithm learns from the same incomplete data.

The platform optimises based on who bought. If half your buyers never reached it, it builds its picture of your ideal customer from half a sample, and spends your budget against an audience derived from a partial view. Your cost per result climbs month after month and you conclude the market got harder.

The fix: send it from the server

Instead of relying on the browser alone, the event is sent server to server, straight to the platform. A server is not affected by an ad blocker or a browser setting.

Two conditions have to hold for it to work properly.

• Matching identity. The platform needs to know who bought in order to tie the purchase to the click. Email and phone are sent hashed (SHA-256), so matching happens without either side exchanging data in the clear.
• Duplication prevention. If the event arrives from the browser and from the server with no link between them, the sale gets counted twice and your numbers inflate. The fix is that both events carry the same order ID, so the platform recognises them as one sale.

Saudi agencies name that second mistake as one of the three most common faults on Salla and Zid stores.

Where MIQAS comes in

MIQAS captures the order at its source and sends it server to server to Meta, TikTok, Snapchat, X and GA4, carrying your order ID so the platform recognises it as the same event it already saw from the browser.

Email and phone are hashed before sending, and the phone is normalised to international format first so the match rate is higher. The original email or phone is never stored with us.

For full duplication prevention we give you a ready-made snippet for the order confirmation page, written separately for Shopify, Salla and Zid.

How to tell whether you need it

Open Events Manager in your account and look at the event source column. If everything says “Browser” only, you are working from part of your data. You should see “Server” alongside it.

And once it is running, the measure of success is not that the number goes up. It is that the number moves closer to your actual order count.

Common questions

Will this increase my sales? No. It makes your real sales visible to the platform. Any lift that follows comes from the algorithm optimising on complete data, not from the tool itself.

Is there a risk my numbers inflate? That is exactly what the shared order ID prevents. Without it, yes there is a risk. With it, the sale counts once.

Is this a privacy problem? Personal data is hashed before sending and the original is not stored. Marketing consent remains your responsibility as the store owner, the same as with any measurement tool.

The pixel is not wrong. It is incomplete. And the difference between incomplete and complete measurement is not a prettier report. It is that the platform’s algorithm gets to work on the truth.