Get your Zid tracking to 95%+ accuracy guaranteed in writing.
Zid is one of the largest ecommerce platforms in Saudi Arabia and the GCC. Its default Pixel + GTM integration is browser-only, with poor Snap match rates, no TikTok Events API, and limited Mada / Apple Pay / STC Pay coverage. We rebuild Zid tracking server-side with full identity match for every paid channel popular in MENA.
Free30 minutesNo obligation
Zid · what breaks
Why Zid stores under-perform on paid ads — Zid
- 01
Snap match rates run low by default
Snap is huge in MENA but Zid Pixel passes minimal identity match params.
- 02
TikTok Events API not enabled
iOS + ad-blocker traffic lost. VBO locked behind data quality.
- 03
Mada / STC Pay events not fired correctly
Regional payment methods miss a large share of completed orders.
- 04
Cross-border ROAS confusion
Stores selling to KSA + UAE + Egypt mix currencies, breaking attribution.
Zid · the fix
Outcomes — Zid
The conversions your browser tags never sent
Across Meta, Snap, TikTok and Google
Snap match rate to 80%+
Full identity + sc_click_id forwarding
Every payment method counted
Mada, Apple Pay, STC Pay, COD all fire
Currency-normalized reporting
Cross-border ROAS makes sense
Zid · architecture
How a Zid order should reach the ad platforms — Zid
Zid serves the Gulf market, where cash on delivery is a large share of orders. Treating a placed COD order as revenue is the single most expensive mistake in this market.
- 1
Click identifiers captured at first touch
Click IDs are captured in the theme at landing and stored in a first-party cookie, surviving the Arabic and English storefront switch.
- 2
The browser sends the fast, fragile copy
Theme code fires browsing and cart events. The checkout is hosted.
- 3
The order itself is the source of truth
The Zid order webhook is the truth, and it carries the payment method and delivery status that a COD business needs.
- 4
A server container sends the authoritative event
The order webhook posts to a GTM server container on your own subdomain, keyed on the Zid order ID, with the COD status carried through.
- 5
Customer identity raises match quality
The order carries customer phone and email where collected. Phone is the stronger identifier in this market, hashed server-side after normalizing to the local format.
Zid · events
The event set we build on Zid, and where each one comes from — Zid
The delivered event, not the placed event, is what a COD business should be optimizing toward.
| Event | Fires when, on Zid | Key parameters | Sent from |
|---|---|---|---|
| view_item | A product page renders | item_id, value, currency, event_id | Browser + server, deduped |
| add_to_cart | The cart updates | item_id, quantity, value, currency, event_id | Browser + server, deduped |
| begin_checkout | The hosted checkout is entered | value, currency, num_items, event_id | Browser + server, deduped |
| purchase | A prepaid order is paid, or a COD order is confirmed delivered | order_id, value, currency, items[], hashed email/phone/name/address, event_id | Server authoritative |
| refund | An order is returned or refused on delivery | order_id, value, currency | Server only |
Zid · normal or broken
Cash on delivery changes what a conversion is — Zid
A placed COD order is an intention. Treating it as revenue trains bidding on people who will refuse at the door.
Normal, not a fault
A meaningful share of COD orders never being paid
Refusal is a normal cost in this market, not a tracking fault.
Bilingual storefronts reporting separately
Correct 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
COD orders counted as revenue at placement
The campaigns with the worst refusal rates look like the best performers.
Refusals never reported back
Reported return permanently inflated.
Click IDs lost on the language switch
Attribution destroyed at landing.
Phone numbers hashed without normalizing the local format
Match rates collapse for reasons nothing in the interface explains.
Zid · prove
How we prove the Zid build is correct — Zid
The tag firing proves the tag fires. These prove the numbers are right.
Source of truth
Zid 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 format, with match rates checked.
- Purchase count within a few percent of zid 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.
Zid · free audit
What we check in the free audit
- Snap match rates run low by default
- TikTok Events API not enabled
- Mada / STC Pay events not fired correctly
- Cross-border ROAS confusion
Zid · when not to buy
When a Zid rebuild is not what you need — Zid
We would rather say this now than three weeks into an engagement.
- You are prepaid-only at low volume.
- Your COD refusal rate is negligible and you have measured it.
- You are testing the market rather than scaling in it.
Zid · what we deliver
Deliverables — Zid
Zid integration module
Custom JS + webhook
Server-side gateway
Stape Pro or self-hosted sGTM (KSA-region option)
Meta CAPI · Snap CAPI · TikTok Events API
Deduped, EMQ 8+
Currency normalization
All values in baseline currency
Notion runbook + 30-day support
Bilingual handover
Written guarantee
95%+ tracking accuracy
Measured against Zid order records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Foundation pixel install for your Zid 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
- Zid 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
1st-party server-side
Recommended$800One-time fee · most popular
The done-for-you package every Zid 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
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid-media channel running 1st-party server-side, end-to-end. For Zid 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
FAQ
Zid questions, answered
Yes — bilingual storefronts fully handled.
Yes — installment events fire correctly.
Yes — KSA-region data residency option available.
More on Zid
- GuideServer-Side Tracking Explained: What It Is, How It Works, and Who Actually Needs It (2026)
- GuideServer-Side Tracking for Shopify: The 2026 Setup That Actually Works
- Free toolFree Zid audit
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
