Ad pixels and server-side conversion tracking

Pixels are how your ad platform learns which ads produced orders. You connect each platform once and Ordexs fires the events on your storefront for you — page views, cart, checkout and purchase.

The platforms: Meta (Facebook and Instagram), TikTok, Google, Snapchat, Pinterest, and a custom option for anything else.

Two fields per platform, and they do different jobs:

  • Pixel ID — browser-side tracking. Fires from the shopper's own browser.
  • Server token — server-side conversion tracking, Meta's Conversions API and its equivalents. Fires from Ordexs directly to the platform.

Add both. The browser pixel alone loses every shopper running an ad blocker or a privacy browser, and in this market that is a large slice of them. The server token is what makes those conversions arrive anyway, so the platform can optimise on real purchases rather than the fraction it happened to see. Events are deduplicated between the two, so a purchase counted both ways is still one purchase.

A saved token shows as dots. For security Ordexs never shows the token itself again once it is saved — the box shows a row of password dots instead, which means a token is stored. To replace it, click the box and paste the new token, then save. Clicking away without typing keeps the saved one.

The list shows how many pixels are live, and you can open your store to check them with the platform's own debugging tools.

What gets sent. High-value events by default — purchase, checkout started, and add to cart. Low-value events like every page view are deliberately not mirrored server-side, because the volume costs money and teaches the platform very little.

Extra options. Each pixel card has an Extra options drawer, closed by default; tap it to open. The badge on it shows how many options are on. Save the card after changing them.

Order status events (Meta and TikTok only, need the server token). Four switches: Send confirmed orders, Send delivered orders, Send cancelled orders and Send returned orders. When on, Ordexs sends a ConfirmedOrder event when your team confirms an order, DeliveredOrder when the courier delivers it, CancelledOrder when an order is cancelled and ReturnedOrder when the courier brings the parcel back, within about 10 minutes, matched to the shopper by hashed phone and the ad cookies captured at checkout. In cash on delivery the checkout purchase is only a promise; create a custom conversion on DeliveredOrder in the platform's Events Manager and optimise your campaigns on it to pay for buyers who really pay. Cancelled and returned orders are useful as audiences to exclude from your ads. Until a server token is saved on the card, these four switches are greyed out and shown off, with a note asking for the token; paste it and they unlock. The card explains where to generate the token: Meta Events Manager → pixel → Settings → Conversions API; TikTok Events Manager → pixel → Settings → Events API (you need Admin or Operator access, and a token only works for pixels of its own ad account).

Don't count as a purchase (every platform except custom). Two switches, both off by default:

  • Duplicates: a repeat order by the same customer sends no Purchase event. "Duplicate" means your own Duplicate rule from the Orders page (same phone, or same phone and same items, within the time you chose). The customer's first order still counts, so a real buyer is counted once.
  • Blocked devices: an order flagged as coming from a device you blocked (Settings → Order protection) sends no Purchase event. With Blocked devices set to Block those orders never exist, so this only matters when it is set to Flag, or when a device only looks like one you blocked.

These orders still appear in your dashboard as normal. Only the ad platform stops counting them, so with either switch on, the platform can show fewer purchases than your Orders page. Other flags (too many orders, risk badges, the bot check) never stop a Purchase event.

Blocked orders are never sent. An order that Order protection blocks is never created, so no pixel receives a Purchase for it.

Per-product pixels. A product can carry its own tracking pixel in addition to the store's, for a campaign that needs its conversions kept separate.

Attribution is separate from pixels. Ordexs records where each order came from — Instagram, Facebook, TikTok, search, a referral, or direct — from the link the shopper arrived on, and shows it as a badge on the order. That works whether or not any pixel is connected, and it is the honest answer to "which channel is actually producing orders" when a platform's own dashboard claims credit for everything.

Meta Ads as a one-click connection is not live yet (see the upcoming integrations, and Analytics → Ads manager). Until then, pasting the Pixel ID and token here is how Meta tracking is set up, and it works.

More in Marketing

Still need help?

Ask the assistant from the search box in your dashboard. It answers from these same guides, in English, French or Arabic, and can make changes for you. Or write to us and a person will reply.