Conversion Tracking Setup in Saudi Arabia (2026): Salla, Zid, WhatsApp and SAR Values

Conversion tracking tells each ad platform which clicks became sales or real enquiries, so it can find more people like them. The parts are familiar: GA4, Google Ads conversions, the Meta pixel with the Conversions API, Google Tag Manager. What changes in Saudi Arabia is where the conversions happen. Many stores run on Salla or Zid. Many enquiries arrive on WhatsApp or by phone. Snapchat and TikTok often take real budget. And every value should be in SAR, reported on Riyadh time. This guide is built around those differences.

We do not publish a price list for tracking work. What a build involves depends on what already fires, so we check the account first and quote after.

Start with what your Saudi customer actually does

Before any tag goes in, write down every action worth money and what it is worth in SAR:

• A paid order on your Salla, Zid or Shopify store.
• A WhatsApp chat that turns into a booking or an order.
• A phone call long enough to be a real conversation.
• A form that your sales team marks as qualified.
• A branch visit, if you can match it back later.

A tap on a WhatsApp button is not an enquiry, and an order placed is not always an order paid. Decide what counts before tagging, or the platforms will optimise toward the wrong thing.

Build order for a Salla or Zid store

1. Platform integrations first. Connect the store's own Google and Meta integrations, then confirm each purchase is sent once, with the order value as a number and currency SAR.

2. GA4 and Tag Manager. Add them where the store allows, and check events in DebugView before trusting any report.

3. Google Ads purchases. One purchase conversion per order, with enhanced conversions switched on.

4. Meta pixel and Conversions API. Browser and server events with a shared event id, so Meta counts each order once. Our guide to Meta CAPI setup in Saudi Arabia covers phone matching and deduplication.

5. Snap Pixel and TikTok pixel. Add both, with their server connections where you spend seriously, so you are not paying for reach you cannot measure.

6. Merchant Center. SAR pricing and Saudi tax settings in the feed from day one, matching the store.

If you are still choosing or rebuilding a store, see our Salla store development service.

Lead businesses: WhatsApp and calls

Many Saudi service businesses close by conversation rather than by form. Track three layers:

• Contact started. A WhatsApp click or a call, recorded as a secondary action so it does not drive bidding.
• Qualified enquiry. Marked by your team in a CRM or a shared sheet.
• Sale. Imported back to Google and Meta as an offline conversion with its SAR value.

Without the second and third layers, the platforms learn to find people who tap buttons, not people who buy.

SAR values and Riyadh time

Two settings cause more reporting arguments in Saudi accounts than anything else.

Currency. Send value as a number and currency as SAR on every platform. Some Saudi brands run an ad account billed in USD. That is fine, but conversion values should still be sent in SAR so revenue matches the store.

Time zone. Set the ad accounts, GA4 and the store to Riyadh time. If one of them runs on Dubai time, daily totals will never match, and a Saudi National Day or Ramadan report will cut across the wrong hours.

Personal data

Saudi Arabia has its Personal Data Protection Law. Collect customer details with a clear privacy notice and a lawful basis, hash phone numbers and emails before they leave your server, and keep consent records clean. A well planned setup meets both needs at once.

What clean tracking lets you report

Cost per purchase and return on ad spend exist only because purchases are tracked properly. In the online stores we run in Saudi Arabia, Performance Max reports a cost per purchase and a return on ad spend we can act on only because each order reaches Google once, as a paid order, with its SAR value. Without a deduplicated purchase event in SAR, neither figure could be trusted, and neither account could be optimised toward sales.

Checks before you trust the numbers

• Place a real test order and see it once in GA4, Google Ads, Meta, Snapchat and TikTok, in SAR.
• Check that Meta Events Manager shows browser and server events merged, not doubled.
• Compare a week of store orders with what each platform reports.
• Recheck after every store theme or app change, because tags often break silently.

If you want your Saudi tracking checked before you spend more, talk to us.

Frequently asked questions

What does a Saudi tracking setup include?

GA4, Tag Manager where the store allows it, Google Ads purchases with enhanced conversions, the Meta pixel with the Conversions API, Snap and TikTok pixels, and Merchant Center with SAR pricing and Saudi tax settings. Lead businesses add WhatsApp, call and offline sale tracking.

Do Salla and Zid stores need extra work?

Usually. Their built in integrations are a good start, but you still need to confirm each purchase is sent once, with the value as a number and currency SAR, and that browser and server events share an event id so nothing is counted twice.

How should I track WhatsApp enquiries?

Record the click or chat as a secondary action, mark qualified enquiries in your CRM, and import closed sales back to Google and Meta with their SAR value. That way the platforms learn from buyers, not from people who only tap a button.

Why do my ad platforms and my store show different totals?

Most often it is currency or time zone. Values sent in USD, or one system on Dubai time while the others run on Riyadh time, make daily totals drift apart. Set every system to SAR values and Riyadh time, then compare again.