Google Ads WhatsApp and Call Tracking in the UAE and Saudi Arabia: The Full Setup

Why tracking is different in the UAE and Saudi Arabia

In many countries a Google forwarding number on your call asset or website lets Google see each call, its length and the ad behind it.

None of that reaches the Gulf. Neither the UAE nor Saudi Arabia is on Google’s list of countries where forwarding numbers are offered (Google Ads Help, answer 2382961, checked 4 October 2026). Call reporting with call length goes with them, as does the “calls to a phone number on your website” conversion. What survives: clicks on call ads and call assets can still count as conversions, based on Google’s estimate of whether a real call followed, and taps on the number on your mobile site can be conversions too. Importing the outcome of calls is not an option, because Google ties call imports to forwarding numbers as well.

WhatsApp is the second gap. A buyer who would rather message than ring leaves no mark in Google Ads unless you build one. Google’s message assets, which open WhatsApp or SMS from the ad, are labelled beta and need advertiser verification, a good policy history, an active WhatsApp Business or SMS number and a conversion-based bid goal (answer 14888522). Google says message ads run globally on Android and lists the UAE and Saudi Arabia among the countries where they can serve on iOS, but a beta is not open to every account, so check whether the option appears in yours. Chats opened from the ad skip your website anyway, so you still need the method below.

For currency, verification and billing in the region, start with our overview of Meta and Google Ads across the Gulf; here we stick to measurement.

The measurement ladder: taps, qualified leads, sales

Treat measurement as three rungs, each arriving later than the one below and sitting closer to money.

1. Click signals on the landing page. A WhatsApp tap and a phone tap, each its own conversion action. Fast and plentiful, but a buyer and a job seeker look identical.
2. A qualified-lead signal. Your team, or an assistant, marks the enquiry as a real prospect in your CRM or sheet: right service, an area you cover, a realistic timeline.
3. A sale or booking signal. The contract signed, the appointment kept. The fewest, the slowest and the hardest to argue with.

Form submissions sit on the first rung, beside the taps.

Which conversion to bid on, and when

Each conversion action is primary or secondary. Primary actions drive automated bidding and the main Conversions column; secondary ones are recorded for you to watch but ignored by bidding.

At launch only the taps have the volume for bidding to learn from, so they start as primary. Create the qualified-lead action the same day as secondary, so it gathers history without steering anything.

When qualified leads reach Google every week without gaps, and your team marks them against the same definition each time, swap the roles. Bidding then chases the searches that produce prospects rather than idle taps. Reported conversions will fall, because you are counting fewer and better things; judge the switch on cost per qualified lead, and use our guide to what Google Ads cost in AED and SAR to set an affordable one.

For a small business, sales usually stay secondary: too few and too late for bidding to use. Import them anyway, to see which campaigns make revenue and which only make conversations.

Setting up the click signals in Google Tag Manager

1. Create the conversion actions in Google Ads. One website action for WhatsApp clicks and one for phone taps, each in a lead category with the count set to one conversion per click. Note each conversion ID and label.
2. Add a Conversion Linker tag on all pages. It keeps the ad-click details in a first-party cookie, so a tap three pages later is still credited.
3. Build the triggers. Enable the built-in Click URL variable. Add a “Just Links” trigger for Click URLs matching wa.me or api.whatsapp.com (one regular-expression condition covers both), and a second for Click URLs starting with tel:.
4. Add one Google Ads conversion tag per action, each with its own ID and label on its own trigger.
5. Test in preview mode. Open the site through Tag Assistant, tap each button and confirm the right tag fires exactly once — at phone width too, because sticky mobile bars often use different markup.

Two snags are common. Floating chat widgets are often scripts or iframes, not plain links, and Tag Manager cannot see the tap. If the trigger never fires, use an ordinary WhatsApp link, or have your developer push a data-layer event on tap.

The second is duplicates: two taps from one visitor are still one lead. The one-per-click setting absorbs most repeats, and the tag can be limited to once per page. Also check the tap is not counted again by a hard-coded snippet or by an imported GA4 event set as another primary action.

Keeping the click ID from ad to CRM

Whether a tap was worth having is decided days later, and the click ID in your landing-page address is the only thread back to the ad.

1. Turn on auto-tagging. Each ad click then lands with a GCLID in the URL, or a GBRAID or WBRAID for some iOS traffic.
2. Save it on arrival. A short script stores whichever ID is present, with the time, in a first-party cookie on your domain, so it survives a few page views.
3. Pass it into the form through a hidden field filled from that cookie.
4. Carry it into WhatsApp as a short reference. On tap, generate a short code, log it with the click ID and time, and prefill the message: “Hi, I’d like a quote (ref 7KQ2)”. The code points back to the click.
5. Store it with the lead, in the CRM record or sheet row you will later upload.

Some people delete the prefilled text; you lose those chats from the upload, not from the business. Our guide to Google Ads for cargo companies in the UAE shows a simpler version that tags messages by route.

Phone calls

A tap proves a call was attempted, not who placed it. Log each tap with its click ID and time, and where call volume is low enough to do it reliably, match it to your phone system’s log once the caller becomes a prospect. Calls placed straight from a call asset never touch your site, so record them in the CRM as “Google Ads call” for your own reporting.

If you would rather not build this yourself, it is part of our Google Ads management in the UAE and Google Ads management in Saudi Arabia; the account, tags and data stay in your company’s name.

Uploading qualified leads and sales to Google Ads

Offline conversion import is how the upper rungs reach Google: this click became a qualified lead, or a sale, at this time.

• Each row needs the click ID, the conversion action’s name exactly as it appears in Google Ads, the conversion time with its time zone, and a value if you use one. Dubai is GMT+4 and Riyadh GMT+3, so a sheet feeding accounts in both must be clear about the clock.
• The window. Conversions uploaded more than 90 days after the last click are not imported (answer 7012522). With a long sales cycle, the qualified-lead upload is what reaches Google in time.
• The rhythm. Weekly at least, more often while bidding is learning, on a fixed day with a named owner. The UAE weekend is Saturday–Sunday and Saudi Arabia’s Friday–Saturday, so a team covering both is safest uploading Monday to Thursday.

Three ways to send the rows:

• A spreadsheet on Google’s template, uploaded in the interface. Cheap, but it depends on someone remembering.
• A CRM connector, direct or through an integration tool. Less manual work; check that the click ID travels with the stage change, not just the email address.
• The Google Ads API, connected by a developer. Worth it at high volume or with a custom CRM.

Before the first upload, write down what “qualified” means — for a clinic, perhaps a consultation request with a preferred date; for a property broker, a buyer with a budget and a timeline — and keep it fixed. Redefining it every month changes what bidding aims at.

Enhanced conversions for leads when the click ID goes missing

Click IDs get lost: a redirect strips them, a cookie is blocked, a form is filled in a week later on another device. Enhanced conversions for leads gives Google a second way to match, with no click ID needed in your CRM.

When someone submits your form, the Google tag captures the email or phone number they typed, in hashed form. When you later upload that lead as qualified with the same details, hashed, Google matches the two.

• It covers form leads only, because the tag needs details typed on your site. Chats and calls still rely on the click ID or reference.
• Keep phone numbers in the CRM in the format the form collects, with +971 or +966, so the hashes line up.
• Say in your privacy notice that form details are used to measure advertising.
• Run it alongside click-ID capture; each catches leads the other misses.

Where an AI WhatsApp assistant fits

The weak point is the second rung: someone must read, judge and mark every chat, weekends included, and when that slips the upload thins out.

An AI assistant on your WhatsApp Business number can take that step. It replies within moments, asks what your sales team would ask — which service, which emirate or city, how soon, roughly what budget — and tags the chat as qualified, not qualified or needing a person. The reference from the prefilled message is in the first line, so the tag lands on the right click ID without anyone copying it.

That qualified tag becomes the conversion you upload, so Google learns from chats that passed your own questions rather than from taps. It also covers the hours your team is off, including the UAE’s Saturday–Sunday and Saudi Arabia’s Friday–Saturday weekends, in English or Arabic.

Two points of care. A customer who messages you opened that conversation, but promotions sent later need their opt-in. And the assistant should say plainly that it is automated, ask only what qualification needs, and keep answers where your team can find and delete them.

It runs on the WhatsApp Business API rather than the phone app; our WhatsApp Business API set-up guide covers the account side, though its pricing is for India.

A testing checklist and the usual mistakes

Run this before launch and whenever the website changes:

1. Open the landing page with a test click ID in the URL; confirm it survives every redirect and lands in the cookie.
2. Tap WhatsApp on a phone: one tag fire, a prefilled reference, and that reference logged beside the click ID.
3. Tap the number (one tag fire, and it dials), then submit the form (the click ID reaches the CRM).
4. Tap the same button twice: still one conversion.
5. Next day, check each action is recording, with the right primary and secondary settings.
6. Upload one real qualified lead and read the upload report for errors.
7. Repeat on the Arabic page, if you have one.

If an action still shows as inactive, our guide to getting help with Google Ads in the UAE and Saudi Arabia lists Google’s own channels.

The short version

Without Google forwarding numbers, advertisers in the UAE and Saudi Arabia must build their own bridge from ad click to real lead. Count WhatsApp and phone taps as separate conversions, keep the click ID with every enquiry, decide which leads qualify and upload them weekly. Bid on taps first, switch to qualified leads once they arrive steadily, and let an assistant do the tagging so it never slips.

To have this built and run for you, see our Google Ads management for UAE businesses or the same service for businesses in Saudi Arabia.

Beeps Digital Beeps Digital is an AI growth agency based in Kothamangalam, Kerala. We run Google Ads for businesses in the UAE and Saudi Arabia, and build the WhatsApp follow-up and conversion tracking behind them, in English, Arabic and Malayalam. We work with Gulf clients remotely from Kerala and have no office in the GCC. CIN: U62010KL2026PTC100348.