CONVERSION TRACKING QA

Your Conversion Data Might Be Lying — Most Accounts Have Errors You Haven't Found

In the UAE, WhatsApp is how customers contact businesses — but most ad accounts have no conversion event tracking WhatsApp clicks at all. Every WhatsApp lead generated by a Google Ads or Meta Ads campaign is invisible to the platform. Smart Bidding has no signal from one of the highest-intent actions a visitor can take. This QA audit finds that gap and every other tracking error in your setup — across Google Ads, Meta Ads, GA4, and GTM.

Request your Tracking QA → View the evidence →
This is for you if

This QA is for businesses in the UAE that have tracking configured but aren't certain it reflects how customers actually convert

The business owner whose ads drive WhatsApp enquiries that are never counted as conversions — Your Google Ads and Meta campaigns drive visitors to your site. Many of those visitors click your WhatsApp button rather than filling in a form. But your ad accounts show conversions only from form submissions — the WhatsApp click-throughs are not tracked. The platforms are optimising toward a partial signal that excludes your highest-intent channel, and your reported CPL bears no relationship to your true cost per qualified lead.

The real estate or property developer with leads coming through multiple touchpoints — Your campaigns generate inquiries through contact forms, WhatsApp, phone calls, and Meta lead ads. Each comes through a different system. None of them are unified in your conversion tracking. Google Ads attributes to the last Google click. Meta attributes to the last Meta impression. The same lead may be counted in both platforms. Your total reported conversions exceed your total actual inquiries, and you cannot identify which channel is genuinely driving pipeline.

The regional marketing manager scaling budgets across UAE and GCC markets — You are increasing ad spend across Google and Meta for UAE, Saudi Arabia, and other GCC markets. Conversion data is the primary input to those budget decisions. If the tracking is inaccurate — missing WhatsApp events, duplicate conversions, values not passing in AED — you are scaling based on distorted signals. Confirming tracking accuracy before increasing spend is the correct sequence.

What's broken

The four most common tracking errors we find in UAE accounts

WhatsApp clicks not tracked as conversion events

WhatsApp is the primary contact channel for businesses across the UAE, yet the vast majority of ad accounts have no conversion event associated with WhatsApp clicks. A visitor who clicks the WhatsApp button after seeing a Google Ad generates no conversion signal in Google Ads. Smart Bidding cannot credit the ad for that outcome. The platform continues optimising toward form submissions and phone calls while the highest-intent conversions happen entirely outside the tracked funnel.

Duplicate conversion events inflating counts by 2–3x

Duplicate conversion events — where both a native Google Ads tag and a GA4-imported conversion fire for the same action — are as common in UAE accounts as in any other market. Accounts that have been through multiple agency setups frequently accumulate overlapping conversion tags from different providers, none of which were properly decommissioned. The result is conversion counts that bear no relationship to actual lead or sale volume.

Purchase events firing without revenue values in AED

For UAE e-commerce and subscription businesses, purchase events that fire without passing transaction values — or that pass values in USD rather than AED — render value-based bidding unusable. Smart Bidding cannot distinguish between a high-value transaction and a low-value one if every conversion looks the same to the algorithm. Incorrect currency configuration is a consistent finding in UAE accounts where setup was done by providers unfamiliar with AED-denominated markets.

Form events firing on page load instead of form submit

This trigger error is as common in UAE accounts as anywhere else. A confirmation page trigger fires on every page load rather than on a successful form submission. Every visitor who reaches the confirmation URL — regardless of whether they submitted a form — is counted as a converted lead. In high-traffic UAE campaigns, this can produce thousands of phantom conversions per month.

What we engineer

What the QA covers

Google Ads conversion actions

We audit every active conversion action in your Google Ads account: status, category, counting method, value configuration, and attribution window. We check specifically for WhatsApp click conversion events — whether they exist and whether they are passing the correct event data — and identify any duplicate conversion actions from multiple tag installations or GA4 imports.

Meta Pixel events

We verify that the Meta Pixel is firing the correct standard events — including Lead, Contact, Purchase, and InitiateCheckout — with the correct parameters. For UAE accounts, we check that purchase values are denominated in AED and that WhatsApp click events are configured as custom conversions where relevant. We verify deduplication setup where both the Pixel and Conversions API are in use.

GA4 key events

We review GA4 key event configuration, trigger logic, and parameter accuracy. For UAE businesses, we specifically check whether WhatsApp click events are configured as GA4 key events and whether those events are being imported into Google Ads. We also verify that transaction values are passing in AED and that the currency code is correctly specified in the dataLayer.

GTM tags and triggers

We audit the full GTM container — every tag, trigger, and variable — and test each conversion tag against its intended user action. For UAE accounts, this includes testing WhatsApp click listeners, phone number click tags, and any custom event listeners set up to capture contact actions beyond standard form submissions.

Cross-domain tracking

We check whether GA4 and Google Ads tracking correctly handles user journeys that cross domains — including third-party booking platforms, payment gateways used in the UAE market, and landing page tools hosted on separate domains from the main site. Cross-domain breaks are a consistent finding in UAE campaigns where separate landing page infrastructure is used for Arabic and English audiences.

Attribution model configuration

We review the attribution model in use and assess whether it reflects multi-touch customer journeys common in UAE markets — where users may encounter an ad on Meta, research on Google, and convert via WhatsApp. Last-click attribution systematically undervalues every touchpoint before the final click and provides a distorted picture of which channels and campaigns are driving pipeline.

Conversion window settings

We verify that conversion window settings are appropriate for UAE market purchase cycles. For real estate and high-consideration B2B categories with long decision timelines, default 30-day windows frequently miss legitimate late conversions. For retail and e-commerce, the opposite problem — windows that are too long — can import irrelevant historical conversions into current bidding signals.

Request your Tracking QA →
What changes

What you receive

Before
After
Before Complete QA report with every issue found
After A written report documenting every tracking error found across Google Ads, Meta Pixel, GA4, and GTM. Each issue is described precisely, located specifically, and rated by severity: critical (actively distorting campaign decisions), significant (causing data loss or inflation), or advisory (reduces future risk).
Before Exact fix instructions for each issue
After Every issue in the report includes step-by-step instructions for fixing it. For missing WhatsApp conversion events, the report specifies the GTM tag configuration, the trigger setup, and the Google Ads conversion action parameters needed. For AED currency errors, the dataLayer specification is included. Implementation can proceed without needing additional interpretation.
Before A conversion tracking setup that reflects how UAE customers actually convert
After WhatsApp clicks tracked. Form submissions tracked accurately. Purchase values passing in AED. Once the errors identified in the QA are corrected, your Smart Bidding and Meta algorithms receive signals that correspond to actual customer behaviour in the UAE market — not a partial and distorted version of it.
Before A documented tracking baseline for future reference
After The QA produces a written record of your correct tracking configuration. When site updates, new campaigns, or Arabic landing page additions introduce regressions, you have a baseline to verify against rather than waiting for performance anomalies to surface the problem.
Common questions

FAQ

How do you track WhatsApp clicks as conversion events?

WhatsApp clicks are tracked by configuring a click listener in Google Tag Manager that fires when a user clicks a WhatsApp link — typically a wa.me or api.whatsapp.com URL. This trigger activates a Google Ads conversion tag and a GA4 event tag simultaneously, recording the click as a conversion in both platforms. The QA confirms whether this is in place, and if not, the fix instructions specify the exact GTM configuration required.

Our campaigns are managed by a UAE agency — can you still QA the account?

Yes. The QA is independent of your current management arrangement. We review the account as it stands and report findings directly to you. Many UAE clients find that their tracking was configured during an initial agency setup and has never been reviewed against actual firing behaviour since.

Do you check tracking for both Arabic and English landing pages?

Yes. Where separate landing pages exist for Arabic and English audiences, we test conversion events on both. Arabic landing pages sometimes use different GTM triggers or have been built on separate platforms that are not covered by the main site's tracking configuration. These gaps are a consistent finding in UAE accounts running bilingual campaigns.

Our purchase values are in AED — will the QA check that values are passing correctly?

Yes. Verifying that transaction values are passing in AED — and that the correct ISO currency code is specified in the dataLayer and conversion tag configuration — is a standard part of the QA for UAE e-commerce accounts. Incorrect currency specification causes Smart Bidding to misinterpret the relative value of transactions and renders value-based bidding unreliable.

What is the difference between a Conversion Tracking QA and a full Paid Ads Audit?

A Conversion Tracking QA is a focused technical check of whether your existing tracking records the right events accurately — WhatsApp clicks, form submissions, purchases, and other key actions. A Paid Ads Audit is broader, covering campaign structure, keyword strategy, bidding, creative, and landing pages in addition to tracking. If your primary concern is whether your conversion data is accurate, the QA is the right scope. If you want a full account diagnostic, the Paid Ads Audit includes tracking as one of its check areas.

Our team

The people behind the work

Not a black box. Real specialists you can call, with their names on the work.

Niraj Raut

Niraj Raut

Founder — Ecommerce SEO
Keshab Joshi

Keshab Joshi

PPC Expert
Hawrry Bhattarai

Hawrry Bhattarai

Google Ads Expert
Arogya Rijal

Arogya Rijal

SaaS SEO Expert
About Us →
Start here

Find Out Whether Your Tracking Reflects How UAE Customers Actually Convert

Five business days. A written QA report. Severity ratings and exact fix instructions for every issue found. If your account is missing WhatsApp conversion events, counting the same lead twice, or passing purchase values without AED denomination — this QA will find it. If the setup is correct, you will have documentation confirming that before you increase spend.

Request your Tracking QA →

5-day turnaround · Written QA report · Every issue rated by severity · No retainer required