Most tracking tutorials assume a card payment and a thank-you page that always loads. A typical Riyadh or Dubai store has cash on delivery, two buy-now-pay-later providers that redirect off-site, Snapchat and TikTok carrying real budget, a storefront in two languages, and a privacy law in each country. Each one changes what a "purchase" means, or whether the platform hears about it at all.
What do Salla, Zid and Shopify track out of the box?
All three get a browser pixel onto the store, and some integrations add server events, but none of them knows a COD order isn't revenue yet.
Salla has the most native coverage. Its help center documents apps for Google Tag Manager, the Facebook Pixel, the TikTok Pixel and the TikTok Conversion API. Salla's Meta Ads integration says connecting your account sets up the pixel, the Conversions API and the catalog automatically, and its Snap Business Extension (under Marketing, then Tracking tools) syncs the Snap Pixel, catalog and Conversions API. Those articles don't say how deduplication works or which order status triggers the purchase, so test it in each platform's Events Manager before adding anything. More on our Salla conversion tracking page.
Zid offers a Snap Ad integration that installs the Snap Pixel; apps cover the rest. I couldn't find Zid documentation of native Conversions API support for Meta or TikTok, so check what your apps actually send. Zid's webhooks are the useful part: order.create, order.status.update and order.payment_status.update, with conditions that filter on status (including delivered and cancelled) and payment_method (including Cash On Delivery). That's exactly what COD tracking needs. See Zid conversion tracking.
Shopify stores in the region usually run Meta's and TikTok's official apps, which can send server events. Its checkout fires the purchase when the order is placed, whatever the payment method, so COD orders still count on day one.
How should you track cash on delivery orders?
Treat the checkout as an order placed, and send the purchase only when the order is real. COD orders get refused at the door, ignore the confirmation call, or come back. If the pixel already called it a sale, the algorithm learns to find people who place orders, not people who pay.
Three workable options, trading signal speed against signal truth:
- Purchase at checkout, cleaned up later. Fastest signal, most inflated. Only Google Ads cleans up properly, through conversion adjustments keyed on order ID: a retraction zeroes out a refused order, a restatement changes the value. Google's help docs say to wait at least 24 hours, and that automated bidding ignores adjustments made after 7 days.
- Purchase on confirmation. Many Gulf stores confirm COD orders by phone or WhatsApp within hours. Send the purchase server-side when the status moves to confirmed or preparing, with
event_timeset to the original order time. Meta and Snapchat reject anevent_timemore than 7 days old, which confirmation easily beats. This is my default. - Purchase on delivery. Cleanest revenue, slowest signal. Use Salla's
order.status.updatedor Zid'sorder.status.updatefiltered to delivered. Slow deliveries can drift outside your attribution window, so the sale arrives but can't be credited to the ad.
Whichever you pick, don't let the browser fire the same Purchase for COD orders at checkout, or deduplication keeps that first copy and your confirmation logic changes nothing. Fire a different browser event for unconfirmed COD orders. On TikTok, don't build on PlaceAnOrder: TikTok's help center lists it as soft-deprecated, with CompletePayment renamed to Purchase.
Why do Tabby and Tamara orders go missing from ad reports?
Because the purchase pixel lives on your thank-you page, and BNPL checkout sends the shopper to another domain first. If they approve and close the tab, or the redirect fails on a weak mobile connection, the browser never reports the sale.
Both providers tell merchants not to trust the redirect anyway. Tabby's docs return the customer to your success, cancel or failure URL with payment_id appended, call the redirect a frontend navigation signal only, and say to verify status on your backend (success means AUTHORIZED or CLOSED). Tamara's docs describe an order_approved webhook, after which you call the authorise endpoint, and note that this server-to-server step avoids frontend redirection issues.
Same shape as COD, then: the order is confirmed on a server, so send the conversion from one. Two more gotchas:
- Referral hijacking in GA4. If the return visit starts a new session, the BNPL domain gets the credit. Add the provider's checkout domain to GA4's unwanted referrals list.
- Lost click IDs. Capture
fbclid,ttclidand the Snap click ID on landing and store them against the cart, so the server event carries them even if the shopper never returns.
The general pattern is in BNPL conversion tracking.
How do you send phone numbers so Meta, Snapchat and TikTok can match them?
Normalize every number to full international format, then shape it the way each platform wants before hashing with SHA-256. COD stores always have a phone number because the courier needs one, email is often optional, and Salla's storefront login accepts a phone number as the identifier. Here the phone is the customer field you'll actually have.
The trap: Saudi and UAE shoppers both type local numbers starting 05. Hash that as-is and it matches nobody. And the platforms disagree on the plus sign:
| Platform | Event and dedup key | Phone format before SHA-256 | Docs say |
|---|---|---|---|
| Meta Conversions API | Purchase, event_id matching the pixel's eventID | 9665XXXXXXXX (digits, country code, no leading zero) | Event time up to 7 days back |
| Snapchat Conversions API | PURCHASE, event_id matching the pixel's dedup ID | 9715XXXXXXXX (no +, no 00, no leading zero) | Dedup on event_id within 48 hours; event time up to 7 days back |
| TikTok Events API | Purchase, same event_id in pixel and API | +9665XXXXXXXX (E.164; per TikTok's partner integration docs) | Dedup within 48 hours |
| Google Ads enhanced conversions | Purchase conversion, transaction_id | +9715XXXXXXXX (E.164) | Retract or restate by order ID |
// Normalize a KSA or UAE number once, then format per platform.
function toIntlDigits(raw, defaultCountry) { // '966' or '971'
var d = String(raw || '').replace(/\D/g, '');
if (d.indexOf('00') === 0) d = d.slice(2); // 00966... -> 966...
if (d.indexOf('966') === 0 || d.indexOf('971') === 0) return d;
if (d.indexOf('0') === 0) d = d.slice(1); // 05X... -> 5X...
return defaultCountry + d;
}
var digits = toIntlDigits(order.phone, order.country === 'AE' ? '971' : '966');
var forMetaAndSnap = sha256(digits); // 9665XXXXXXXX
var forTikTokGoogle = sha256('+' + digits); // +9665XXXXXXXX
Send hashed email when you have it, plus IP, user agent and the platform cookies captured at checkout (_fbp, _ttp, Snap's sc_cookie1). Confirm the fields arrive with Snap's validate endpoint and Meta's and TikTok's test events tools. Snapchat is usually the most neglected; see Snapchat Conversions API.
What breaks with Arabic and English storefronts and SAR or AED pricing?
Mostly identifiers and currency, not the language itself:
- Product IDs must be language-neutral. If the Arabic storefront sends the product name or a localized URL as
content_ids, it won't match a catalog keyed on SKU. Send the same SKU from both versions. - One container, one dataLayer schema. Triggers that match on English button text or
/en/URL paths silently stop firing on the Arabic version. Trigger on dataLayer events, never on visible text. - Send the currency the order was charged in. Use the ISO code,
SARorAED, with the value. Don't hard-code one currency for a store selling into both countries, and don't convert to USD yourself because the ad account bills in dollars; GA4 and Google Ads convert to your reporting and account currency. A missing currency code is how a 300-riyal order becomes a 300-dollar one.
What do Saudi PDPL and UAE PDPL mean for conversion tracking?
Both laws reach your customer data even if your company or servers sit outside the country, and both lean on consent. This is the high-level picture only; I'm a tracking engineer, not a lawyer, so get legal advice for your setup.
- Saudi Arabia. The Personal Data Protection Law took effect on 14 September 2023, with a one-year grace period that generally ran to 14 September 2024. SDAIA is the regulator. DLA Piper's summary says it covers entities outside the Kingdom processing data of people living there, that consent is the primary legal basis, and that transfers abroad are allowed only under conditions, which makes sending customer data to ad platforms a question for counsel. There's no Saudi law specifically on cookies, but the PDPL still covers what pixels collect.
- UAE. Federal Decree-Law No. 45 of 2021 makes consent the default, with listed exceptions. It covers controllers outside the UAE processing data of people in the UAE, and leaves DIFC and ADGM under their own data protection regimes. Its executive regulations hadn't been published as of DLA Piper's January 2025 update, and I couldn't confirm their status from a primary government source, so check with your advisers.
One technical point: hashing protects a phone number in transit, but the hash still identifies a person to Meta or Snapchat. Don't assume hashed data falls outside either law. A server-side setup gives you one place to decide what leaves and to apply a consent choice to every platform at once.
Why does first-party server-side tracking fix what the default setup misses?
Because in the Gulf the truth about an order lives in the order system, and only a server can listen to it. The browser sees a checkout. Your Salla, Zid or Shopify backend sees whether the courier collected the cash and whether Tabby authorized the payment. The build I'd put on a Saudi or UAE store:
- A server GTM container on your own subdomain, for example
data.yourstore.sa, so cookies are set first-party and last longer in Safari. That needs your own domain on the store, not a platform subdomain. - Browser events go through it: page views, add to cart and checkout from the pixel, each with an
event_id. At checkout the container stores the order ID with the click IDs and platform cookies. - The order webhook becomes the purchase. Salla's
order.status.updated, Zid'sorder.status.updateor Shopify's order webhooks post to the container. Prepaid and BNPL orders fire Purchase once payment is verified; COD on confirmation or delivery. - One event, four destinations. The container sends the Purchase to Meta CAPI, Snapchat CAPI, TikTok Events API and Google Ads with the order ID as
event_id, the stored click IDs,SARorAED, and the phone number formatted per platform and hashed. - Reversals flow back. A refused or returned order triggers a Google Ads retraction and a GA4 refund event, so value-based bidding isn't trained on cash you never collected.
BNPL sales stop vanishing when a tab closes, COD stops inflating ROAS, and Snapchat and TikTok get identifiers they can match instead of a pixel fighting ad blockers.
Frequently asked questions
Should I send a Purchase event for cash on delivery orders at checkout?
Not if you can help it. Send a different browser event, and send Purchase from the server once the order is confirmed or delivered.
Does Salla support the Meta Conversions API?
Salla says its Meta Ads integration sets up the pixel, Conversions API and catalog when you connect your account. It doesn't document deduplication or the purchase trigger, so test it in Meta's Events Manager.
Why don't Tabby or Tamara purchases show up in Meta or Snapchat?
The pixel fires on the thank-you page, and shoppers who approve payment on the provider's page don't always come back. Both providers say to confirm payment on your backend; send the conversion from there too.
How should I format Saudi and UAE phone numbers for Conversions APIs?
Convert 05X local numbers to 9665X or 9715X, then hash with SHA-256. Meta and Snapchat want digits only; Google and TikTok expect E.164 with the plus sign.
Do I need the Snapchat Conversions API if I already have the Snap Pixel?
Snap recommends running both, with the same event_id on each. The server event still arrives when the pixel is blocked or the thank-you page never loads.
Does the Saudi PDPL require a cookie banner?
There's no Saudi law specifically about cookies, but the PDPL treats consent as the primary basis for processing personal data. Ask a lawyer how that applies to your tracking.
If your ad reports don't match what the courier and Tabby actually paid out, we can rebuild your tracking on first-party server-side GTM, with order-system purchases, proper dedup and phone matching for every platform you run. About 98% accuracy is typical, and we guarantee 95% or better. Tell us about your store and we'll show you where the gaps are.
- saudi arabia
- uae
- cash on delivery
- snapchat capi
- bnpl
- salla

