Conversion tracking in the UAE: calls, WhatsApp and forms
A step-by-step set-up for counting calls, WhatsApp taps and forms in a UAE ad account, with what to do when a step fails and a test for each route.
The short answer
Count the three routes separately: forms on the thank-you page or success event, WhatsApp taps as link-click events, and phone calls through call-button taps plus a call log, because Google's forwarding numbers weren't offered in the UAE on 7 November 2026. Mark the real enquiry as the primary conversion, then send qualified outcomes back to Google and Meta.
On 7 November 2026 the UAE was not on Google's list of countries where forwarding numbers are available, so the call tracking that Google Ads guides often tell you to switch on isn't there for a UAE business. That makes phone calls the route to plan first, and WhatsApp the second, because to Google's tags a WhatsApp tap is simply a click on a link. Forms are the easy part.
The steps below build a set-up that counts all three routes, marks the enquiry that matters, and sends outcomes back so the ad platforms can learn from them. Each step says what to do if it fails.
How do you count calls, WhatsApp and forms in a UAE account?
- List the routes and define 'qualified'. Write down every way an enquiry reaches you (form, phone call, WhatsApp chat, booking) and what makes one qualified, such as a confirmed budget or an address you serve. If sales can't agree on the definition, stop here, because tracking can count anything but it can't decide what matters.
- Put one Google Tag Manager container on the site and connect Google Analytics 4 and the Google tag through it. You need admin rights to the container and the property in your own name. If the site builder only accepts a plain Google tag, install that and add events through its custom event option, and never run two tags for the same property or every enquiry is counted twice.
- Count forms on success, not on click. Fire the event on the thank-you page, or on the form's success message if the page doesn't change. If there is no thank-you page, ask the developer to push a success event, because a button click fires even when the form fails validation and you will count enquiries that never arrived.
- Count WhatsApp taps. Add a trigger for clicks on any link containing wa.me or api.whatsapp.com, send a GA4 event and a Google Ads conversion from it, and mark the event as a key event in GA4, the name GA4 now uses for conversions. If your button is a chat widget with no link, ask the developer for a click event, and check in Tag Assistant's preview that it fires before you trust it.
- Count call taps and log real calls. A trigger on links that start with tel: counts taps on the number. Without forwarding numbers, a call can't be tied to an ad unless you keep a call log with a source field or use a third-party tracker that can issue UAE numbers. If nobody will fill in the log, say so in the report and treat call taps as taps, not calls.
- Create one conversion action per route in Google Ads and mark one of them Primary. The real enquiry is the Primary action and everything softer is Secondary, so bidding chases what you would pay for. If an action still shows no recent conversions a week later, repeat it on the live site with Tag Assistant open and look for a trigger that never fires.
- Record what happens to every chat. Label WhatsApp chats as new, qualified, won or lost, with the source, in the WhatsApp Business app or in your CRM. If you move to the API to automate this, note that Meta charges per delivered message, and since 1 October 2026 service replies are charged again after 1,000 free a month per number, so check the current rate card first. The WhatsApp Business API guide explains the options.
- Send outcomes back. Capture the click ID (GCLID, plus GBRAID or WBRAID when present) in hidden form fields, store it with the lead in your CRM, and upload qualified and won outcomes as offline conversions. Store phone numbers in full international format, starting +971 for UAE numbers, so matching works. Leads who arrive by call or WhatsApp without filling in a form carry no click ID, so keep them in the call log and chat labels and report them by source.
- If you advertise on Meta, add the Conversions API alongside the pixel and make sure each event is counted once. Meta's documentation says a set-up should confirm that events are deduplicated and matched correctly. If Events Manager shows the same enquiry twice, the browser and server events aren't sharing an event ID, so ask the developer to send one.
- Test every route end to end and write down the date. Submit a test form, then tap the WhatsApp button and the call button on a phone, watch each tag fire in Tag Assistant's preview and in GA4's DebugView, and check that the conversion appears in Google Ads. If one route fails, fix it before spending another dirham, because an account that can't count a route will quietly starve it.
Do you need consent mode and a cookie banner in the UAE?
In November 2023 Google extended its consent mode with ad_user_data and ad_personalization, on top of the existing ad_storage and analytics_storage settings. Google's EU user consent policy names the European Economic Area, the UK and Switzerland, not the UAE, so that policy is not the reason a UAE-only site would add consent mode. A UAE site with visitors from those places still has to consider it.
The UAE's federal personal data law is Federal Decree-Law No. 45 of 2021, and Morgan Lewis reported on 15 June 2026 that the regulations needed to apply it had not yet appeared, so check whether that has changed. The DIFC and ADGM have their own data protection laws that apply inside those zones. That leaves the cookie question for a UAE lawyer to answer for your business, and this isn't legal advice, so read the PDPL glossary entry and take advice before you rely on any banner.
How do you know the numbers are right?
Compare the platform's count with your own enquiry log once a week for a month. The platform should never report more qualified enquiries than your log contains, and a day with zero conversions on a busy day usually means a broken tag. A gap in the other direction is normal while calls and chats are still being logged by hand, and it tells you which route to fix next.
If you would rather someone else built and maintained the set-up, start from our PPC and Google Ads service page. Whoever does it, open Tag Assistant on your own site now and tap your own WhatsApp button. If nothing fires, you have found your first fix, and the Google Ads set-up guide shows what to build next.
Questions people ask
How do I track WhatsApp clicks as conversions in Google Ads?
Use Google Tag Manager to fire an event when someone clicks a link containing wa.me or api.whatsapp.com, then create a conversion action for it in Google Ads. It counts taps, not conversations, so also log chats in your inbox or CRM and mark which ones were real enquiries.
How do I count phone calls if Google's call reporting isn't available?
Count taps on the call button with a link-click trigger, keep a call log where reception records the source of each call, or use a third-party tracker that can issue UAE numbers. Google's forwarding numbers weren't offered in the UAE when its help page was checked on 7 November 2026, so recheck before relying on either route.
Do I need a cookie banner for conversion tracking in the UAE?
That is a legal question this guide can't settle. Google's consent policy names the EEA, UK and Switzerland rather than the UAE, and the UAE personal data law was still awaiting implementing regulations at the latest source dated June 2026. Take advice from a UAE lawyer. This isn't legal advice.
What is the Meta Conversions API, and do I need it?
Meta describes it as a connection between your marketing data and its systems, sending events from your server alongside the browser pixel. If you use it, check that each event is counted once and matched correctly. Don't rely on promises of a fixed uplift: judge it by whether reported enquiries match your own log.
Why don't my Google Ads conversions match my CRM?
The usual causes are counting taps and clicks instead of completed enquiries, tags that fire twice, different date windows, and leads that arrive by call or WhatsApp with no click ID. Reconcile weekly, and treat the platform reporting more qualified enquiries than your log as a sign of double counting.
Sources
- Google, EU user consent policy
- Google Ads Help, About call reporting, viewed 7 November 2026
- Google Tag Platform, consent mode guide, 2026
- Morgan Lewis, UAE Establishes Federal Authority for Artificial Intelligence and Data, 15 June 2026
- Meta for Developers, Conversions API, 2026
- Meta for Developers, WhatsApp Business Platform pricing, 2026
- DIFC, Data Protection Law, DIFC Law No. 5 of 2020
- ADGM, Penalties of Non-Compliance with the DPR 2021