Conversion tracking is how you find out which ad, which channel and which campaign actually produced an order in your online store. Without it, you pay Snapchat, TikTok, Meta and Google, then look at the sales in your Salla, Zid or Shopify dashboard, and you cannot connect the two.
This guide is written for store owners selling in the UAE, Saudi Arabia and the wider Gulf. It explains what a conversion is, how Google Analytics 4 and Google Tag Manager split the work, how to install the ad platforms’ pixels, how to use the built-in integrations in Salla, Zid and Shopify, when server-side tracking is worth it, and how to test everything before you spend another dirham or riyal.
Every technical detail below comes from the platforms’ official help centres and developer documentation, as they read in October 2026. These interfaces change often, so each point links to its source for you to check.
What is conversion tracking, and why does your store need it?
A conversion is any action you decide is valuable to your business. In an online store it is usually a completed purchase, but it can also be an add-to-cart, a started checkout, a sign-up or a tap on a WhatsApp button.
Google’s Google Ads Help page on conversion measurement describes a conversion action as a specific customer activity that is valuable to your business, such as a purchase, a sign-up or a phone call. You choose what counts and what does not.
Conversion tracking is the system that records that action and ties it to where it came from. When a visitor clicks an ad, the platform stores a temporary identifier in their browser. When they complete the purchase, a tag on your store recognises that identifier and credits the sale to the ad.
Three reasons conversion tracking cannot wait
- The algorithms learn from your data. Sales campaigns on Meta, TikTok, Snapchat and Google optimise towards the purchase events they receive. Without conversion tracking feeding them purchases, they are targeting blind.
- ROAS needs a correct number. You cannot calculate return on ad spend without trustworthy order values. We cover that in detail in our ROAS guide.
- Budget decisions. When you know that one channel brings higher-value orders, you can move budget to it with confidence instead of guessing.
The core events for an online store
| Event | When it fires | Why you need it |
|---|---|---|
| View item | A product page opens | Builds retargeting audiences |
| Add to cart | The add button is pressed | Measures real intent |
| Begin checkout | The checkout page loads | Shows where checkout leaks |
| Purchase | The order confirmation page loads | The event that drives campaign optimisation |
The purchase event is the one everything else rests on. It must carry the order value, the currency and the order ID, as explained further down.
Google Tag Manager vs Google Analytics: who does what?
This is where most store owners get confused. Google Analytics 4 is a measurement and reporting tool. Google Tag Manager is a tool for managing code snippets, and it shows you no reports at all.
What is Google Tag Manager?
According to the Tag Manager Help Centre, it is a tag management system that lets you set up and manage tags on your site. A tag is a small piece of code that sends data somewhere: to GA4, to Google Ads or to an ad platform’s pixel.
How does Google Tag Manager work?
It works through three building blocks. Tags are what gets sent. Triggers decide when, for example when the order confirmation page loads. Variables hold the values that change, such as the order total. All of this lives inside a container, which Google defines as a collection of tags, triggers, variables and related configuration installed on a website or app.
A simple example: you want to send the purchase event to GA4, Meta and TikTok. Without Tag Manager, you paste three snippets into your store theme. With it, you install the container once, add the three tags in its interface and publish them without touching the theme again.
And where does GA4 fit?
GA4 is where the data is read: sessions, traffic sources, the purchase funnel and revenue. Google’s guide to setting up GA4 in Tag Manager explains that the Google tag is what carries data from your website to Analytics, and that you configure it inside a Tag Manager container.
| Google Analytics 4 | Google Tag Manager | |
|---|---|---|
| Main job | Measurement, reports and analysis | Installing and managing tags |
| Shows reports? | Yes | No |
| Data direction | Receives and analyses events | Sends events to GA4 and other platforms |
| Daily user | Store owner and marketer | Whoever runs the technical setup |
| Replaces the other? | No | No |
In short, Tag Manager is the plumbing and GA4 is one of the tanks the data flows into. You can run GA4 without Tag Manager, but a container makes life easier once several platforms are involved.
Conversion tracking setup, step by step
These are the general conversion tracking steps that apply to any store, before we get into each platform.
- List your events. Write down the events you need, starting with purchase. Do not begin with twenty.
- Create a GA4 property and a web data stream. Keep the measurement ID that starts with G.
- Create a Tag Manager account and a web container. Keep the container ID that starts with GTM.
- Connect the container to your store. Use your platform’s official integration where it exists, as described below.
- Add the Google tag for GA4 inside the container and fire it on all pages.
- Add the purchase event with value, currency and order ID.
- Add a Google Ads conversion if you advertise on Google, tied to the same purchase.
- Test before publishing, then publish the version and watch the data for the first 48 hours.
What must the purchase event carry for accurate conversion tracking?
Google’s GA4 ecommerce documentation recommends setting currency at the event level whenever you send a value. If your store sells in SAR and AED, never assume a single fixed currency.
The order ID matters too. The Analytics Help page on transaction IDs says GA4 deduplicates purchase events that share the same transaction ID, that the same ID should not be used across different users, and that you should not send an empty string. This deduplication works for web streams only, not app streams.
Installing the platform pixels: Meta, Snapchat, TikTok and Google Ads
For conversion tracking, each ad platform has its own pixel: a browser snippet that sends events to that platform’s events manager. The conversion tracking principle is identical everywhere; only the names and screens differ.
Meta Pixel
You create the pixel in Events Manager in your business account, then install it through your store platform’s built-in integration or through Tag Manager. The standard events that matter are ViewContent, AddToCart, InitiateCheckout and Purchase.
Snap Pixel
The Snap Pixel works the same way and matters a great deal in Saudi Arabia, where many stores rely on Snapchat. If you are about to launch campaigns there, read our Snapchat ads guide first, then come back to this section.
TikTok Pixel
Salla’s help centre walks through creating a TikTok pixel in Ads Manager: open Events Manager, connect a data source, choose Web, enter your store URL, pick manual setup and the connection method that combines the Pixel with the Events API, then name the pixel and create it. TikTok ads themselves are a separate topic in our blog.
Conversion tracking in Google Ads
In Google Ads you create a conversion action for purchases and install its tag through Tag Manager. You can also import conversions from GA4 instead of using a separate tag. For clean conversion tracking in Google Ads, your campaigns should use one source for purchases, not two. How much Google Ads will cost you is a separate question, covered in its own article.
The golden rule: every purchase must reach each platform exactly once, with the real order value.
Connecting Salla, Zid and Shopify
Each store platform has an official, built-in integration for conversion tracking. We describe only what their own documentation says, because menu paths move as dashboards are updated. If you have not chosen a platform yet, our comparison of Salla, Zid and Shopify covers that decision.
Salla: TikTok conversion tracking
According to Salla’s help article on TikTok, you open Marketing in the dashboard, go to Tracking Tools, pick TikTok in the side menu and press Connect your account. You are sent to TikTok to link an existing account or create one, and you complete the setup steps there.
Once connected, Salla’s tracking page shows the pixel ID, business account, advertiser ID and catalogue settings. You then return to TikTok to finish the Events API setup and choose events. Salla recommends testing with the Pixel Helper extension: add a product to the cart, open checkout, complete a test order and check the extension.
Salla: Snapchat conversion tracking
Salla’s article on connecting Snapchat describes this path: Marketing, then Tracking Tools, then Connect your account. You select the business account, the ad account and the pixel, then approve the permissions. The article says these tools use the Pixel and the Conversions API to collect more accurate data.
Zid: Google Tag Manager and Zid Ads pixels
Zid’s help centre says Google Tag Manager is connected from the dashboard through App Market, then Campaign Tracking, then Google Tag Manager. You enter your container ID in the activation field and press Activate App. The article notes the tool can take 10 to 15 minutes to appear in the store.
For pixels used with Zid Ads, Zid’s pixel FAQ says Meta and Snapchat are connected through Marketing Hub, that every platform requires Admin permissions, and that a merchant’s own TikTok pixel requires contacting the Optimize team.
Shopify: customer events and app pixels
On Shopify, pixels are managed under Settings, then Customer events, as described in the Shopify Help Center. Some pixels come with apps; custom pixels are added manually by a developer. Both run in an isolated sandbox that does not affect the rest of the store.
Shopify’s pixel migration page recommends moving the Meta pixel to the Facebook & Instagram channel and Google Analytics to the Google & YouTube channel. It also warns that tracking the same event more than once is a common problem when migrating.
| Platform | Where conversion tracking is set up | What it covers, per the docs |
|---|---|---|
| Salla | Marketing, then Tracking Tools | TikTok and Snapchat, with pixel and server events |
| Zid | App Market, then Campaign Tracking; Marketing Hub | Tag Manager and Zid Ads pixels |
| Shopify | Settings, then Customer events | App pixels and custom pixels |
Server-side tracking and the Conversions API: when do you need it?
A pixel runs in the visitor’s browser. If the browser blocks tracking, the visitor leaves before the page finishes loading, or they decline consent, the event is lost. So the platforms added a second conversion tracking route: sending the event straight from your store’s server.
Meta and Snapchat call it the Conversions API; TikTok calls it the Events API. Google offers server-side tagging, which the Tag Manager guide describes as moving some tags off your website and onto a server.
When is it worth the effort?
- When you spend meaningful budget every month and see a clear gap between store orders and platform-reported orders.
- When you rely on sales campaigns that learn from the purchase event.
- When your store platform already offers a built-in integration that sends server events, so the cost is low.
A small store that is just starting usually gets reliable conversion tracking from the built-in integration and careful testing. Do not build a tracking server before you have a correct browser purchase event.
The non-negotiable part: deduplication
When the same event is sent from both the pixel and the server, the platform must know they are one event. Each platform does this with a shared event ID:
- Meta: according to Meta’s developer documentation, the pixel’s eventID must match the Conversions API event_id, the event names must match, and events are deduplicated only if they arrive within 48 hours.
- Snapchat: according to Snap’s developer documentation, the pixel’s client_dedup_id is matched with the server event_id within 48 hours, and the order ID on purchase events can be matched for up to 30 days.
- TikTok: according to TikTok’s help centre, event_id must be shared through both the Pixel and the Events API, and overlapping events are merged when they arrive after 5 minutes and within 48 hours of the first one.
These windows are as published in October 2026 and may change, so check the links before you build.
Testing with debug tools
Conversion tracking that has not been tested cannot be trusted. These are the official tools we use in every conversion tracking audit.
Tag Manager preview and Tag Assistant
Before publishing any version, run Preview mode in Tag Manager. Your store opens with Tag Assistant, showing which tag fired, which trigger fired it and what values it carried. Place a full test order and check that the purchase tag fired exactly once.
GA4 DebugView
According to the DebugView help page, you enable debug mode through Tag Assistant or Tag Manager’s preview, then open DebugView from Admin. The middle column shows the events logged in the last 60 seconds, and clicking one shows its parameters: value, currency and transaction ID.
The same page warns that events will not appear if the visitor has not granted analytics consent. If your store shows a consent banner, accept it while testing.
Ad platform tools
- Meta: the Meta Pixel Helper extension and the Test Events tool in Events Manager.
- Snapchat: the Snap Pixel Helper extension and Diagnostics in Events Manager. Snap’s documentation says deduplication results can take up to 24 hours to show.
- TikTok: the TikTok Pixel Helper extension, which is what Salla recommends.
- Google: conversion action status in Google Ads, together with Tag Assistant.
Common conversion tracking mistakes and how to fix them
Most of the conversion tracking problems we see in Gulf stores follow the same few patterns.
Mistake 1: counting purchases twice
The most common cause is a pixel installed twice: once through the platform’s built-in integration and once by hand through Tag Manager. The result is ad-platform sales higher than real orders, and bad budget decisions.
Fix: pick one route per platform. If you combine pixel and server, use a shared event ID. Make sure the purchase event fires once on the confirmation page, not on every page refresh.
Mistake 2: a purchase with no value or the wrong currency
The purchase arrives with a value of zero, or in USD while the store sells in SAR. ROAS then looks like zero or inflated. After fixing it, use the ROAS calculator to compare the real figure with what the platform shows.
Fix: inspect the event in DebugView and in each platform’s test tool. Check that value is numeric, that currency is a valid code such as SAR or AED, and that the order ID is present and not empty.
Mistake 3: ignoring consent
If your store shows a cookie consent banner, your tags must respect the visitor’s choice. Google’s consent mode overview describes four consent types, ad_storage, analytics_storage, ad_user_data and ad_personalization, and two modes: basic, which blocks tags until the visitor interacts with the banner, and advanced, which loads tags with consent denied by default.
Consent is part of conversion tracking, not an extra. Shopify states plainly that merchants are responsible for their own privacy compliance. Review the data-protection rules in the UAE and Saudi Arabia with your legal adviser; do not rely on this article alone.
Mistake 4: events firing on the wrong pages
For example, the purchase event fires when checkout opens rather than on the confirmation page, or add-to-cart fires when a product page loads. That corrupts all optimisation. Test every event with a real end-to-end order.
Mistake 5: trusting the platform’s number blindly
Every platform credits itself using its own attribution window, so a single order can be claimed by Snapchat, TikTok and Google at once. Always compare the total the platforms claim against the actual orders in your store.
Conversion tracking in the Gulf: what is different?
The Gulf market has a few details that affect conversion tracking accuracy and deserve attention.
- Cash on delivery. In many stores the purchase is recorded when the order is placed, not when payment is collected. If the order is later cancelled, it stays in the platform. Review cancellation rates regularly and compare against collected revenue.
- Multiple currencies. A store selling to KSA, the UAE and Kuwait must send the right currency with every order.
- Arabic and English versions. Check that the container and pixels run on both, and that the confirmation page in each language fires the purchase event.
- Peak seasons. Before Ramadan, White Friday and national days, test the whole setup at least two weeks ahead, and do not publish tag changes during the peak.
- Page speed. Every extra tag has a loading cost, and Zid’s help centre says so explicitly. Site speed has its own article on our blog.
- Chat channels. If many orders come through WhatsApp, treat a WhatsApp button tap as a secondary event, not as a purchase conversion. WhatsApp marketing is covered in a separate article.
If shoppers leave before paying, a well-measured begin-checkout event shows it clearly. We cover the fixes in our abandoned cart recovery guide.
Conversion tracking checklist before any campaign launch
Copy this list and work through it with every new setup or theme change:
- Your conversion tracking events are written down and defined, starting with purchase.
- The GA4 property is connected and visits appear in the realtime report.
- The Tag Manager container is installed exactly once across all store pages.
- Each platform pixel is installed through one route only: built-in integration or Tag Manager, not both.
- The purchase event carries value, currency and order ID.
- The order ID is unique and never empty.
- If you use server events, the same event ID is sent from pixel and server.
- The Google Ads purchase conversion has a single source.
- The consent banner works and tags respect the visitor’s choice.
- A full test order appeared in DebugView and in every platform’s tools.
- Both the Arabic and English versions have been tested.
- A weekly conversion tracking review compares store orders against platform-attributed orders.
Conclusion
Conversion tracking is not a technical task that ends on installation day. It is the foundation for every advertising decision, and it needs re-testing whenever the store or the platforms change. Start with one correct purchase event, then expand.
If you would like us to audit the tracking on your store, or build it from scratch with a clear reporting dashboard, see TAIF’s analytics and measurement service or get in touch.
Frequently asked questions
What is conversion tracking in digital marketing?
It is a system that records the valuable actions in your store, such as purchases and add-to-carts, and ties each one to the ad or channel the visitor came from. It tells you what actually drives sales.
What is Google Tag Manager used for, and does it replace Google Analytics?
It is a tool for managing the tags and code snippets on your site from one interface. It does not replace GA4, because it shows no reports. Tag Manager sends the data; GA4 analyses and displays it.
Can I use my store’s built-in integration and Tag Manager together?
Yes, but not for the same pixel. You might run GA4 through Tag Manager and TikTok through Salla’s built-in integration, for example. What you must avoid is the same platform’s pixel installed through both routes, because each purchase would then be counted twice.
Do I need the Conversions API for conversion tracking on a small store?
Not always. If your store platform offers a built-in integration that sends server events, switch it on. Building your own tracking server makes sense once spend grows and you see a clear gap between real orders and platform numbers.
Why does conversion tracking in my ads show more sales than my store received?
Usually for one of two reasons: a pixel installed twice, so each purchase is counted twice, or each platform claiming the same order for itself. Check for duplication first, then compare the platforms’ total with your actual orders.
How do I test conversion tracking after setup?
To test conversion tracking, place a full test order and watch it in Tag Manager preview, GA4 DebugView, and each platform’s test tool or Pixel Helper extension. Confirm the purchase appears once, with the correct value and currency.
Does the consent banner affect conversion numbers?
Yes. When a visitor declines storage, fewer events reach the platforms, so conversion tracking undercounts. Google’s documentation says advanced consent mode provides an advertiser-specific model rather than a general one, which allows more detailed modelling of lost conversions.
