Measurement and analytics
Google Tag Manager: count WhatsApp clicks, calls and forms as enquiries
Ilyes Massoudi9 min readThe short answer
Google Tag Manager is one container placed on the site once, from which you manage every measurement code: Analytics, ad pixels, Clarity, without editing the site each time. Its most important use in the Gulf is tracking the conversions that never pass through a thank-you page: a click on a WhatsApp link, a tap on the phone number, and a form submission. Three triggers, three tags and half an hour, then marking the events as key events in GA4 and importing them as conversions in Google Ads. Without that, your site measures visits and knows nothing of enquiries, and your ads optimise for clicks rather than customers.
What Tag Manager actually is
One idea: instead of placing the Analytics code on your site, then the Google Ads code, then the Snapchat and TikTok pixels, then Clarity, each one an edit by the developer, you place one code called the container. Then from a web control panel you add whatever you want inside the container.
Only three terms you need:
- Tag: the thing that sends: send an event to GA4.
- Trigger: when it sends: on a click on a link containing wa.me.
- Variable: a piece of information added: the clicked link, the page name.
Why WhatsApp specifically
In the Gulf most enquiries do not pass through a thank-you page that can be measured. The visitor taps WhatsApp or the number and leaves the site. Analytics does not see that unless you tell it. Which is why most accounts I open show zero conversions while the phone keeps ringing.
Setup step by step
Before you start: create an account at tagmanager.google.com, create a web container, and place its code on the site (through a WordPress plugin, the platform settings, or your developer once). Then add a GA4 configuration tag with the G- measurement ID on an All Pages trigger.
WhatsApp clicks:
- Variables: enable the built-in click variables (Click URL, Click Text).
- Triggers: New, Click: Just Links, Some Link Clicks, Click URL contains
wa.meorapi.whatsapp.com. - Tags: New, GA4 Event, event name
whatsapp_click, add a parameterpage_locationwith the value{{Page URL}}, using the trigger above.
Call clicks: the same trigger with Click URL starts with tel:, event phone_click.
Form submissions: the Form Submission trigger if the form is a standard one, or an Element Visibility trigger on the thank-you message if the form does not reload the page, event form_submit_lead. Test both, because some forms fool the first trigger.
Testing: preview mode, click every button, confirm the event appears, then publish.
In GA4: Admin, Events; after 24 hours the new events appear; switch on Mark as key event for each.
In Google Ads: Goals, Conversions, Import, from GA4, choose the key events.
What it tells you after a month
| Question | Report |
|---|---|
| Which source brings enquiries | GA4, Traffic acquisition, key events column |
| Which page brings enquiries | GA4, Landing page, key events |
| Arabic or English | Filter on page path starting with /ar or /en |
| Mobile or desktop | GA4, Tech, key events |
| Are the ads bringing customers | Google Ads, conversions per campaign |
Common mistakes
- Tracking all clicks and drowning in noise. Target the links precisely.
- The container installed alongside direct Analytics, counting twice.
- Forgetting to mark the event as a key event in GA4, so it records but never counts as a conversion.
- Tracking a view of the contact page as a conversion. A view is not an enquiry.
- Not excluding your own team’s clicks, so everything appears to work.
A note on personal data
Tracking records visitor behaviour, not identities, if configured correctly, but it remains data processing: mention it in your privacy policy, reduce personal data in the GA4 settings, and ask a legal adviser about the consent required in your country. What the site must publish is in the privacy article.
Where this sits in the audit
The audit detects whether your site measures anything at all and which tracking tools are installed, and scores the conversion path on every page. If you have GA4 with key events I put those numbers behind the conclusions in the report. If you do not, installing measurement becomes the first item in the plan, because it is the precondition for measuring everything after it.