Conversion tracking, GA4 and GTM setup in Dubai

Most accounts we audit have at least one of: missing or double-counted conversions, broken cross-domain tracking, no server-side container, no offline conversions from CRM, and consent mode misconfigured for the UAE legal context.

1. 01

   1. Discovery

   Inventory every conversion, every container, every platform pixel.

2. 02

   2. Server-side foundation

   GA4 + GTM (web + server), CAPI for Meta, Enhanced Conversions for Google, TikTok Events API.

3. 03

   3. Offline conversions

   Connect CRM stages back to ad platforms so smart bidding optimizes for revenue, not form-fills.

4. 04

   4. Documentation + QA

   A measurement plan you can hand to a new agency tomorrow and they'd know exactly what's tracked.

• Measurement plan document
• GA4 + GTM (web + server) implementation
• Meta CAPI, Google Enhanced Conversions, TikTok Events API
• CRM-tied offline conversions
• Consent mode (UAE-compliant)
• QA checklist + handover

Server-side tagging via stape.io, GCP or AWS. Consent mode v2. Enhanced Conversions for leads. Offline events for SQL/Opp/Closed. UTM hygiene across every campaign.

• UAE consent rules are loose by EU standards but still matter for CRM and reporting integrity.
• WhatsApp-led sales mean offline conversions are usually higher-impact here than enhanced conversions.

A tracking setup is only as good as the list of events it is built from, so the first deliverable is a measurement plan that names every event, its parameters, where it fires and which platform receives it. For a UAE lead generation site that usually means form_start and generate_lead with form name and lead type, whatsapp_click and phone_click with the number and the page, a booking or calendar event where one exists, and a crm_qualified event that only ever comes from the CRM. For ecommerce it means the full GA4 commerce set: view_item, add_to_cart, begin_checkout, add_payment_info and purchase with transaction ID, value, currency, items and payment method, so cash-on-delivery and prepaid orders can be separated later. Each event has one name across GA4, Google Ads, Meta, TikTok and LinkedIn, mapped to the platform's standard event where one exists, and a data layer specification is written for the developer so the site pushes the same object every time. Page type, language and user type are added as parameters so reports can be cut by Arabic versus English and by new versus returning. The plan is a living document and is updated with every site change.

The server container is a small web service that receives events from the browser and forwards them to GA4, Google Ads, Meta, TikTok and LinkedIn from your own domain. We host it on stape.io for most clients because it is fast to set up and costs a modest monthly fee, or on Google Cloud when a client wants to run it inside their own account. It is served from a first-party subdomain such as gtm.yourdomain.ae, which extends cookie lifetime in Safari, reduces the data lost to ad blockers and lets us send hashed customer data to the platforms without exposing it in the browser. Server-side also means the browser loads one tag instead of six, which measurably improves page speed on mobile connections. We keep a browser pixel alongside the server events with a shared event ID so each platform deduplicates, and we validate every event in the platform debuggers before launch. Hosting region can be set to a European or Middle East location, which matters for clients with data residency requirements. The container is owned by you, and the setup is documented so any developer can maintain it.

Offline conversions connect what sales knows to what the ad platforms optimize, and the mechanics are precise. Every form captures the Google click ID, Meta click ID, TikTok click ID and LinkedIn identifier in hidden fields along with the UTM set, and these are written to the lead record in the CRM. When a lead reaches an agreed stage, qualified, meeting or won, the CRM exports the click ID, the stage, the timestamp and a value. For Google Ads that goes in through the offline conversion import, either by scheduled sheet or API, within the 90-day click window. For Meta it goes through the Conversions API as a server event matched on click ID, email and phone, with a lead ID where the lead came from an instant form. LinkedIn accepts conversions through its API matched on email. The upload runs at least weekly and daily for high-volume accounts, and a reconciliation report shows how many CRM outcomes matched a click and how many did not, so we can fix the capture rate. Once imports are flowing, the qualified stage becomes the primary conversion and the form fill is demoted to secondary.

Nothing goes live on assumption, because a tracking error discovered after a month of spend has already cost a month of bidding on the wrong signal. QA is run twice: once in a staging or preview environment with test events, and once on the live site with real submissions and, for ecommerce, a real low-value order that is refunded afterward. We check each platform's own debugger rather than trusting the tag manager preview, since a tag can fire correctly and still be rejected on arrival for a missing parameter or a consent state. Cross-domain paths are walked by hand on a phone, because booking tools, payment gateways and Arabic subdomains are where client IDs most often reset. Values are compared to the source system for a sample of real records in AED, and consent mode is tested in all three states. The checklist below is signed by us and by your developer, and the handover pack means a new agency or a new hire could pick the setup up without calling us.