Before you run Meta ads in the UAE: set up tracking that actually works

Before you spend a dirham on Meta ads, set up tracking: the Meta Pixel on your website and the Conversions API from your server, sending the same events with the same event IDs, so Meta counts each sale or lead once. Meta itself recommends running the Conversions API alongside the Pixel for the best ad performance (Meta). Without it, Meta optimises your budget towards whatever it can see, which is usually clicks, not customers.

We set this up before building the creative system and campaign architecture for ScaleHaus, a UAE diecast store. Here's the order we do it in.

Why tracking comes before creative

Meta's delivery system learns from the conversions you report. If purchases go unreported (a browser blocks the Pixel, a customer pays in another tab, an order completes on WhatsApp), Meta learns from a partial picture and spends towards the wrong people. Good tracking doesn't make a bad ad good, but bad tracking makes good ads look bad.

Step 1: install the Meta Pixel

The Pixel is a script on your website that reports what visitors do. On Shopify it's built into the Facebook & Instagram sales channel; on a custom site it goes in the page template. For an online store, the standard events that matter are:

• ViewContent, when someone views a product;
• AddToCart;
• InitiateCheckout;
• Purchase, with the order value and currency (AED).

For a service business, track Lead when someone sends an enquiry form, books a call or starts a WhatsApp chat.

Step 2: add the Conversions API

The Conversions API sends the same events from your server rather than the visitor's browser, so they arrive even when the browser drops the Pixel. If you already have a Pixel, Meta lets you set up the Conversions API for website events from Events Manager without code; custom sites can send events directly from the backend.

Step 3: deduplicate

When the same purchase arrives from both the Pixel and the server, Meta needs to know it's one purchase. The recommended way is to send the same event name and the same event ID from both: Meta treats events with a matching ID and name as identical and keeps the first one it receives. Check Events Manager after a test order: you should see one purchase, received from both the browser and the server.

Step 4: send good customer information

Server events can include hashed customer details, such as email and phone, which help Meta match the event to the right account. Only send what your privacy policy says you collect, and hash it as Meta's documentation describes.

WhatsApp ads and lead forms

In the UAE, many customers would rather message than fill in a form:

• Click to WhatsApp ads open a chat with your business. Meta makes messages free for a period after someone contacts you this way, so the follow-up costs nothing extra (more in our WhatsApp Business API guide).
• Meta lead forms collect a name and number without leaving Instagram or Facebook.

Either way, record which campaign each lead came from. In SARZ Command, enquiries from Meta Ads arrive tagged with their campaign and stay tagged through to the sale, so you can see which campaign actually sells, not just which one gets clicks.

Then build the creative

Once Meta can see real conversions, the creative is what moves the numbers. For ScaleHaus we built a creative system rather than one-off ads: consistent brand elements, made in 4:5 for the feed and 9:16 for stories and reels, so new variations can be produced and tested quickly.

A quick checklist before you launch

1. Pixel installed and firing the right events.
2. Conversions API live, with the same event IDs as the Pixel.
3. One test purchase or lead showing once in Events Manager.
4. AED order values on purchases.
5. Every lead tagged with the campaign it came from.

Want this tracking built into your store or website from day one? See Shopify and custom e-commerce stores or custom websites in Dubai.