Skip to main content
TrackingConsultingFree audit
SallaFor Salla / سلة merchants

Get your Salla tracking to 95%+ accuracy guaranteed in writing.

Salla powers tens of thousands of MENA stores. The default Pixel + GTM install sends Meta, TikTok and Snap a fraction of the data they need to optimize. iOS share is lower in the GCC than in the West — but ad blockers, ITP, and Snap's notoriously poor tag matching together still cost you a substantial share of your reported conversions. We rebuild your Salla tracking server-side, with full identity match, dedup discipline, and live Mada / Apple Pay / STC Pay event coverage.

Get my free conversion tracking auditSee what we check

Free30 minutesNo obligation

By Ariful IslamHow Salla works ↓

Salla · what breaks

Why Salla stores under-perform on paid ads

  1. 01

    Cross-domain checkout breaks attribution

    Salla's hosted checkout typically runs on a different subdomain or CDN. Click_id (fbclid, ttclid, sc_click_id) drops on the redirect. Meta and Snap can't tie the conversion back to the click. Reported ROAS reads like fiction.

  2. 02

    Snap is huge in MENA — and Snap match rates are awful by default

    Snap drives serious DTC volume in the GCC, but the default Snap Pixel install only matches much of conversions. Without server-side CAPI + sc_click_id forwarding, your Snap CPMs balloon and ROAS lies.

  3. 03

    TikTok Events API not enabled

    MENA merchants run heavy TikTok ads but most never enable Events API. iOS and ad-blocker traffic vanishes. Value-Based Optimization can't be unlocked because data quality is too low.

  4. 04

    Native Mada / Apple Pay / STC Pay events not tracked

    Salla's regional payment methods don't fire Purchase events the same way as Stripe checkout. Most stores miss a meaningful share of completed orders entirely in their ad reports.

Salla · the fix

What changes after we ship — Salla

  • The conversions your browser tags never sent

    Across Meta, TikTok, Snap and Google — measured pre/post in your own ad-platform reports.

  • Snap match rate from ~35% to 80%+

    Full identity match + sc_click_id forwarding = Snap finally optimizes properly.

  • TikTok VBO eligibility unlocked

    Once Events API data quality is high enough, Value-Based Optimization opens up.

  • Every payment method counted

    Mada, Apple Pay, STC Pay, COD all fire as proper Purchase events with the right currency / value.

Salla · architecture

How a Salla order should reach the ad platforms

Salla serves the Gulf market, where cash on delivery is a substantial share of orders. That single fact changes what a conversion means more than any technical consideration.

  1. 1

    Click identifiers captured at first touch

    Click IDs are captured in the theme at landing and written to a first-party cookie, surviving the Arabic and English storefront switch.

  2. 2

    The browser sends the fast, fragile copy

    Theme code fires browsing and cart events. Checkout is hosted, so the browser path thins out at the purchase.

  3. 3

    The order itself is the source of truth

    The Salla order webhook is the truth, and it is where a cash-on-delivery order's real status — placed, delivered, or returned — can be distinguished.

  4. 4

    A server container sends the authoritative event

    The order webhook posts to a GTM server container on your own subdomain, keyed on the Salla order ID, with the COD status carried through.

  5. 5

    Customer identity raises match quality

    The order carries customer phone and email where collected. In this market phone is the stronger identifier, and it is hashed server-side.

Salla · events

The event set we build on Salla, and where each one comes from

Cash on delivery makes the delivered event, not the placed event, the one worth optimizing toward.

view_itemA product page rendersitem_id, value, currency, event_idBrowser + server, deduped
add_to_cartThe cart updatesitem_id, quantity, value, currency, event_idBrowser + server, deduped
begin_checkoutThe hosted checkout is enteredvalue, currency, num_items, event_idBrowser + server, deduped
purchaseThe order is placed — for prepaid orders this is the saleorder_id, value, currency, items[], hashed email/phone/name/address, event_idServer authoritative
subscription_startedA cash-on-delivery order is confirmed delivered and paidorder_id, value, currency, plan, event_idServer authoritative
refundAn order is returned or refused on deliveryorder_id, value, currencyServer only

Salla · normal or broken

Cash-on-delivery changes the whole picture — Salla

A COD order is an intention, not a payment. Treating the two the same is the defining mistake in this market.

Normal, not a fault

  • A meaningful share of orders never being paid for

    COD refusal rates are a real cost of doing business in this market, not a tracking fault.

  • Bilingual storefronts reporting separately

    Correct behavior for a dual-language store.

  • Ad platforms report more conversions than you have orders

    Meta credits a 7-day click and 1-day view; Google credits on click date. Two platforms can each claim the same sale. Compare each one to your order records separately and never add them together.

  • Recent days always look worse than they finish

    Conversions are credited back to the date of the click, so yesterday's return on ad spend is understated and will keep improving for several days. This is attribution working, not data arriving late.

Actually broken

  • Cash-on-delivery orders counted as revenue at placement

    Bidding is trained on orders that will be refused at the door, and the campaigns with the highest refusal rates look like the best.

  • Refusals never reported back

    Reported return stays permanently inflated by the refusal rate.

  • Click IDs lost on the language switch

    Attribution destroyed at the first redirect.

  • Phone number not hashed correctly for the local format

    Match rates collapse because the number format does not normalize.

Salla · prove

How we prove the Salla build is correct

The tag firing proves the tag fires. These prove the numbers are right.

Source of truth

Salla order records

  • COD and prepaid orders confirmed distinguished, with delivered status reported separately.
  • Refusals confirmed reversing the conversion.
  • Click IDs confirmed surviving the language switch.
  • Phone hashing verified against the local number format, with match rates checked.
  • Purchase count within a few percent of salla order records for a fully closed week, matched on order ID rather than on totals.
  • No order ID appearing twice in any platform's event log.
  • Deduplication confirmed at every destination that supports it.
  • Test and staff orders excluded, with the exclusion confirmed active rather than merely configured.
  • The same reconciliation repeated 30 days later, because a setup that works once and then drifts is the harder failure to catch.

Salla · free audit

What we check in the free audit

  • Cross-domain checkout breaks attribution
  • Snap is huge in MENA — and Snap match rates are awful by default
  • TikTok Events API not enabled
  • Native Mada / Apple Pay / STC Pay events not tracked

Checked against

Salla order records

Get my free conversion tracking audit

Free30 minutesNo obligation

Salla · when not to buy

When a Salla rebuild is not what you need

We would rather say this now than three weeks into an engagement.

  • You are prepaid-only at low volume. Then a standard purchase event covers you.
  • Your COD refusal rate is negligible and measured.
  • You are testing the market rather than scaling in it.

Salla · what we deliver

Deliverables — Salla

  • Salla tracking module

    Custom JS + webhook integration

  • Server-side gateway

    Stape Pro or self-hosted sGTM

  • Meta CAPI · Snap CAPI · TikTok Events API

    All deduped, EMQ 8+

  • Google Enhanced Conversions

    Web + Leads coverage

  • Cross-domain click_id forwarding

    fbclid · ttclid · sc_click_id · gclid

  • QA + Notion runbook

    Plus 30-day support

Written guarantee

95%+ tracking accuracy

Measured against Salla order records. Miss it and we keep working at no cost.

Get my free conversion tracking audit

Pricing

Pick the package that fits your ad spend

Browser-side starter

$400One-time fee · lifetime ownership

Foundation pixel install for your Salla store. Honest disclosure: this is a starting point only. If you spend $1K+/month on paid media you should be on the 1st-party server-side tier — rather than quote you a recovery percentage, we'll show you how to measure your own gap: compare what the platforms reported against the orders in your backend for the same week. That ratio is the entire argument, and it's yours to check — see trackingconsulting.com/measurement-accuracy-methodology.

  • One-time fee · zero monthly · zero SaaS lock-in
  • Salla dataLayer (clean spec)
  • GA4 e-commerce events
  • Meta Pixel · Google Ads tag
  • TikTok Pixel · Microsoft UET
  • Consent Mode v2 banner integration
  • QA test orders + 7-day support
  • No CAPI · no iOS recovery
Lock in the one-time price

1st-party server-side

Recommended

$800One-time fee · most popular

The done-for-you package every Salla store running paid ads should start with. We build the entire 1st-party server-side stack on your subdomain — Meta, Google, TikTok, Microsoft, LinkedIn all fed from the server. Recovers the conversions iOS, Safari ITP, ad blockers and cookie deprecation hide today. You don't lift a finger. Built in 2–4 days · accurate data in 7 days.

  • One-time fee · save vs SaaS subscriptions over 5 years
  • Fully recovered + built in 2–4 days · accurate data in 7 days
  • Everything in browser-side starter
  • 1st-party server-side GTM (your subdomain)
  • Meta CAPI · full advanced matching · 8+ EMQ
  • Google Enhanced Conversions (Web + Leads)
  • TikTok Events API · Microsoft UET server
  • Deterministic browser ↔ server deduplication
  • Live EMQ verification + screenshots
  • Notion runbook + 30-day support · zero recurring
Lock in the one-time price

Full 1st-party stack

$1,800One-time fee · lifetime ownership

Every paid-media channel running 1st-party server-side, end-to-end. For Salla brands spending $30K+/month who can no longer afford attribution leaks. Pay once. Own everything. Includes Pinterest + Snap + Reddit + LinkedIn CAPI, Klaviyo identity stitching, BigQuery + Looker Studio.

  • One-time fee · save 6-figure SaaS subscriptions over 5 years
  • Everything in 1st-party server-side tier
  • Pinterest · Snapchat · Reddit · LinkedIn · X CAPIs
  • Klaviyo identity stitching (if used)
  • BigQuery export (server logs + GA4)
  • Looker Studio attribution dashboard (branded)
  • Multi-region / multi-currency / EU residency
  • GDPR-audit-ready Consent Mode v2 wiring
  • 60-day support · optional retainer · no lock-in
Lock in the one-time price

FAQ

Salla questions, answered

Yes — bilingual storefronts are common in MENA and we handle both. Event names stay English (per ad-platform requirements) but values pass through cleanly.

More on Salla

Free · 30 min

Free Salla tracking audit

Book a free Salla audit WhatsApp

Free30 minutesNo obligation