E-commerce Tracking · GCC

Meta Conversions API for Salla & Zid: The GCC E-commerce Tracking Guide

iOS updates, ad blockers, and stricter browser privacy have made the Meta pixel alone unreliable. If you run a Salla or Zid store in Saudi Arabia or the UAE, server-side tracking via the Conversions API (CAPI) is no longer optional — it is how you keep ROAS, attribution and audience matching alive in 2026.

Why CAPI matters for Salla and Zid stores

The standard Meta pixel fires in the browser. That fires only when a customer's browser cooperates — which today means losing 20–40% of conversion signal across Safari, in-app browsers, ad blockers, and slow mobile connections. The Conversions API sends those same events from your store's server directly to Meta, so:

  • Event match quality goes up (more hashed email, phone, name, IP, user agent reaching Meta).
  • Attribution becomes resilient to browser privacy changes and iOS ATT.
  • Algorithm learning improves — Advantage+ Shopping, lookalikes and value optimisation get cleaner signal, lifting ROAS materially.

Across managed Salla and Zid accounts in KSA and UAE, switching from pixel-only to a deduplicated pixel + CAPI setup typically recovers 15–35% of reported purchases and lifts ROAS by 10–25% within 14 days.

Before you start: prerequisites

  • A Meta Business Manager with admin access.
  • A live Meta Pixel (you will keep using it — CAPI complements it, not replaces it).
  • A Conversions API access token (Events Manager → your pixel → Settings → Conversions API → Generate access token).
  • Admin access to your Salla or Zid store.
  • Your domain verified in Meta Business Manager, plus 8 prioritised events configured in Aggregated Event Measurement (Purchase first).

Part 1 — Meta CAPI on Salla

Salla ships a native Meta integration in the App Store. It is the fastest path to a clean CAPI setup, and it handles event deduplication for you.

  1. From your Salla dashboard go to Apps Store → Marketing → Facebook Pixel & Conversions API and install the official app.
  2. In the app, paste your Pixel ID and the CAPI access token you generated in Events Manager.
  3. Enable the events you want to track server-side. At minimum: PageView, ViewContent, AddToCart, InitiateCheckout, Purchase. Add Lead only if you run lead-gen flows.
  4. Toggle Advanced Matching on. Salla will hash and forward email, phone, first/last name, city and country with each event — this is where most of the match-quality lift comes from in the GCC.
  5. Save. Place a test order and confirm it shows up in Events Manager → Test Events with both Browser and Server sources and the same event_id (dedupe working).

GCC gotcha: Salla customers often check out with a Saudi phone number but no email. Make sure phone-number matching is enabled — it is the highest-signal identifier you will get in KSA.

Part 2 — Meta CAPI on Zid

Zid offers a native Facebook & Instagram integration that includes Conversions API support. The setup is similar in spirit to Salla but lives in a different place.

  1. From your Zid dashboard open Marketing → Marketing Channels → Facebook & Instagram (or install the official app from the Zid Market if not already enabled).
  2. Connect your Meta Business account and select the correct Business Manager, ad account, and pixel.
  3. Provide the Conversions API access token from Events Manager.
  4. Enable the full e-commerce event set: PageView, ViewContent, AddToCart, InitiateCheckout, AddPaymentInfo, Purchase. Zid sends the matching event_id from both browser and server for deduplication.
  5. Enable Advanced Matching and confirm hashed customer parameters (em, ph, fn, ln, ct, country) are passing through in Test Events.
  6. Place a test order on a sandbox/test product and verify the Purchase event arrives once in Events Manager with Browser + Server sources and a value matching your store currency.

GCC gotcha: Make sure Zid is sending the order value in the same currency you bid in inside Ads Manager (SAR for KSA, AED for UAE). Mixed currencies break value optimisation and Advantage+ Shopping.

Validating the setup (do not skip this)

An installed integration is not a verified integration. Always check four things in Events Manager:

  1. Test Events: each event appears with Browser and Server tags and identical event_id values.
  2. Diagnostics: no "missing parameters", "deduplication issues" or "redundant events" warnings.
  3. Event Match Quality (EMQ): Purchase should land above 7.0 once real traffic flows. Below 6.0 means matching parameters are missing.
  4. Overview: 24 hours after launch, server-side event counts should be higher than browser-only counts. If they are equal, CAPI is not actually contributing new signal.

Future-proofing: what to do once CAPI is live

  • Turn on value-based lookalikes from your CAPI Purchase events — these consistently outperform interest targeting in KSA and UAE.
  • Switch campaigns to Advantage+ Shopping once you have 50+ server-side Purchase events per week.
  • Send offline conversions (WhatsApp closes, in-store visits) through the same CAPI endpoint to close the attribution loop for healthcare, real estate and high-AOV verticals.
  • Re-check EMQ monthly. Salla/Zid app updates occasionally drop a matching parameter — catching it early protects ROAS.

Common GCC e-commerce attribution mistakes

  • Running CAPI without the pixel — you lose browser-side advanced matching and dedup. Run both.
  • Sending the Purchase event from both the thank-you page and the webhook without sharing an event_id — Meta double-counts.
  • Hashing parameters manually before sending — Salla and Zid already hash; double-hashing breaks matching.
  • Verifying the domain on the storefront subdomain but running ads to the apex (or vice versa). Verify both.

Need help wiring this up?

I set up Meta Conversions API on Salla and Zid stores across KSA, UAE, Egypt, Kuwait, Qatar and Oman, including dedup, advanced matching, AEM prioritisation and Advantage+ Shopping migration. If you want it done right the first time, get in touch.