Looks like you're in . Want the local site?
In the UAE, WhatsApp is the primary conversion channel for most businesses — and it is invisible in standard GA4 and Google Ads setups. Arabic and English campaigns run simultaneously but attribution rarely separates them. We build tracking that reflects how customers actually convert in this market, not how they convert in a US product template.
Business where WhatsApp drives leads but analytics show nothing — Customers land on your site, click the WhatsApp button, message your sales team, and convert offline. Your Google Ads account shows minimal conversions. Your GA4 shows traffic and bounce rates. No one has tracked the click-to-chat as a conversion event, so an entire conversion channel is invisible to the algorithm and to your reporting.
Running Arabic and English campaigns with merged attribution — Your Google Ads and Meta campaigns target Arabic-speaking and English-speaking audiences separately — different creatives, different landing pages, sometimes different offers. But your conversion data comes back as a single merged pool. You cannot tell whether your Arabic-language campaigns are performing differently from English-language campaigns, or whether attribution is skewed by device and language preference patterns.
E-commerce or real estate business with GA4 but no verified conversion setup — A GA4 property exists and gets traffic, but key events are not configured, conversion actions in Google Ads are not linked correctly, and no one has verified whether the purchase or lead form event is firing on the right page with the right parameters. Budget is being spent and the optimisation algorithm has no signal.
WhatsApp click-to-chat is the de facto lead generation mechanism for a large share of UAE businesses — real estate, retail, professional services, healthcare. Standard GA4 and GTM templates do not capture this event. When it is not tracked, the paid channels that drive the most WhatsApp-initiated leads show zero or low conversion rates, and budget shifts away from them based on data that ignores the market's primary contact method.
When a campaign in Arabic and a campaign in English both drive to the same GA4 property with no language or campaign-segment dimension, reported performance is an average of both. If Arabic-language campaigns convert at a different rate — which they frequently do, given different device behaviours and different audience intent patterns — you cannot see it. Bidding decisions are made on blended data that represents neither segment accurately.
Google Ads campaigns frequently have two or three conversion actions active simultaneously — a GA4-imported event, a direct Google Ads conversion tag, and a legacy conversion action from a previous setup. All three count. When Smart Bidding receives the same conversion signal three times, it learns from a distorted picture of what is actually working.
For UAE real estate, automotive, and high-consideration B2B sectors, the online interaction is an enquiry — the actual conversion happens offline after a site visit, a meeting, or a phone call. Without offline conversion import, campaigns are optimising toward enquiries rather than toward qualified leads or deals closed. The algorithm cannot distinguish a serious enquiry from a low-quality form fill.
We configure GA4 key events to reflect the UAE conversion journey: page views, scroll depth, form submissions, phone click events, and — critically — WhatsApp click-to-chat events tracked as GA4 conversion events with parameters that identify source, campaign, and language. Custom dimensions are set up to segment Arabic versus English campaign traffic at the event level.
Your GTM container is audited for zombie tags, duplicate triggers, and misconfigured variables. A new event schema is designed to cover all conversion touchpoints: WhatsApp button clicks, phone number clicks, contact form submissions, and e-commerce transactions. Arabic and English campaign parameters are captured and passed as custom dimensions in every event where attribution is relevant.
We configure conversion actions in Google Ads for each distinct conversion type: WhatsApp click, phone call, form submission, and purchase — as separate actions, not merged. Meta Pixel is audited and a Conversions API (CAPI) configuration is recommended for iOS audiences, which are significant in the UAE market given high iPhone adoption rates. Duplicate conversion actions are consolidated.
WhatsApp click-to-chat tracking is implemented via GTM — a custom event fires when a visitor clicks your WhatsApp contact link or button, capturing the source, medium, campaign, and language parameters. This event is imported into Google Ads as an offline conversion action, giving Smart Bidding a signal from your most-used conversion channel.
For real estate, automotive, and B2B businesses, offline conversion import is configured to bring CRM-stage data back into Google Ads. When a lead advances to a qualified stage or a deal closes, that event is imported against the original ad click. Campaigns can then optimise toward actual qualified leads rather than raw enquiry volume.
For UAE e-commerce businesses, we audit Merchant Centre for feed errors, suppressed products, and currency or region attribute issues. We link Merchant Centre to Google Ads and verify that purchase conversion tracking is configured without duplication between the native platform integration and any GTM-based conversion tag.
WhatsApp Business API changes the conversation routing but not the click event on your website. The conversion event fires when a visitor clicks the WhatsApp link or button on your site, regardless of where the conversation is then handled. We configure the GTM trigger to fire on the click event itself, so API versus native WhatsApp does not affect data collection.
GA4 does not separate by language natively, but it can be configured to do so. We set up a custom dimension that captures the language parameter from your UTM tags, and ensure that every Arabic-language campaign uses a consistent language parameter in its UTM structure. This allows you to filter and compare performance by language in GA4 Explorations and in Looker Studio dashboards.
Yes, but the configuration is slightly different. Each site gets its own GTM container and GA4 event schema, and we configure cross-domain tracking if there is any navigation between the two sites during a user session. Conversion data from both properties can be consolidated in a single GA4 account for portfolio-level reporting.
Meta Conversions API (CAPI) is the primary mitigation. CAPI sends event data server-side rather than relying on browser-based pixel firing, which means iOS users who have opted out of tracking still contribute server-side conversion signals. We configure CAPI for your Meta ad account as part of the standard setup, with event deduplication to prevent double-counting between pixel and API.
GA4 and Google Ads conversion data typically begins populating within 24–48 hours of the tracking going live. For Smart Bidding strategies, Google Ads recommends 30–50 conversions in a 30-day period before switching from manual to automated bidding — the timeline depends on your conversion volume, not the setup itself.
Not a black box. Real specialists you can call, with their names on the work.
If your customers are converting through WhatsApp and that is not tracked, if your Arabic and English campaigns are reporting as a merged pool, or if your GA4 is collecting data but has no conversion events configured — every paid decision is being made without the most important inputs. A 10-day setup fixes that.
10-day turnaround. Audit before any changes. You own everything we build.
Ignited Nepal
Growth engineering · replies within 1 business day
By continuing you agree to our privacy policy.
