What is a key event in GA4?

A key event is GA4's replacement for conversions — an event you mark as valuable, like a form submit or WhatsApp click. Marking events as key events lets every GA4 report show which pages and channels produce them.

How do I track WhatsApp clicks in GA4?

Fire an event when any link to wa.me is clicked, either via Google Tag Manager's click-URL trigger or a small script. Then mark that event as a key event so it appears in conversion reports.

Why does my GA4 show traffic but no leads?

Usually one of two reasons: enquiry actions are not tracked as events, so leads are invisible, or the traffic is arriving on pages with weak CTAs and mismatched intent. Fix tracking first, then judge the pages.

Do I need Google Tag Manager for this?

It helps but is not required. The three UAE lead events — WhatsApp, form, phone — can be fired with a few lines of code on the site itself. GTM becomes worth it when marketing needs to change tracking without a developer.

Is GA4 enough or do I need other analytics tools?

For most UAE SMEs, GA4 plus Search Console covers everything that matters: what searchers see, what visitors do, and which pages produce enquiries. Add other tools only when a specific question those two cannot answer keeps coming up.

Do I need a cookie consent banner for GA4 in the UAE?

If you serve EU visitors or run remarketing ads, add a consent banner that gates non-essential tags and disclose analytics in your privacy policy. For a purely local audience the bar is lower, but a clear privacy policy is still good practice — the compliance context is in the [UAE website compliance guide](/blog/uae-compliance).

How do I know my GA4 lead tracking is actually working?

Open GA4's Realtime report, then click your own WhatsApp button, tap your phone link, and submit your own contact form on the live site. Each should appear as an event within seconds. If it does not fire for you, it is not firing for customers either.

GA4 Lead Tracking for UAE Websites: What to Measure

Most UAE business sites launch with GA4 installed and nothing configured. The dashboard fills with users and sessions, but nobody can answer the only question that matters: which pages and channels produce enquiries? This guide covers the small set of things worth tracking and how to act on them.

Short Answer

Track the actions that are actual enquiries in the UAE: WhatsApp link clicks, contact-form submissions, and phone-number taps. Mark each as a key event in GA4, connect Search Console, and review one report weekly — key events by landing page and by channel. Everything else is secondary.

The three events that are real leads in the UAE

WhatsApp clicks — clicks on any `wa.me` link. In most UAE industries this is the #1 enquiry channel, and it is invisible in a default GA4 install.
Form submissions — fire an event on successful submit (not on page load of the form, and not on button click if validation can still fail).
Phone taps — clicks on `tel:` links, which on mobile means a real call attempt.

If your developer set up custom events, verify them in GA4 under Reports → Engagement → Events by clicking each button on your live site and watching for the event in Realtime.

Mark them as key events

In GA4, Admin → Events → toggle each of the three as a key event (GA4's term for conversions). This single step is what turns GA4 from a traffic counter into a lead tracker: every standard report can then be sliced by key events, and any future ad campaigns can optimise toward them.

The two reports worth reading weekly

Skip the default dashboard. Two views answer the useful questions:

Report	Question it answers	Where in GA4
Key events by landing page	Which pages actually produce enquiries	Engagement → Landing page, add key events column
Key events by session channel	Which sources send buyers, not just visitors	Acquisition → Traffic acquisition

Reading them is where the value is. A landing page with high traffic and zero key events has a message or CTA problem — the fixes are usually the ones covered in why business websites don't get enquiries. A page with few visits but a high enquiry rate deserves more internal links and possibly ad spend — the same logic behind a strong lead-generation landing page.

Connect Search Console — it's half the picture

GA4 shows what visitors did; Search Console shows what searchers saw before clicking. Link the two (Admin → Product links → Search Console) and check queries and pages monthly. Impressions without clicks usually means a weak title; clicks without key events means the page attracts the wrong intent. For a new site, pair this with a proper indexing check so you know Google sees every page you launched.

UTM discipline for everything you share

GA4 can only attribute what is tagged. Add UTM parameters to links you control — Google Business Profile website link, Instagram bio, WhatsApp broadcasts, email signatures. Untagged, these all pile into "direct" and you lose the ability to see which effort produced leads. Keep the scheme boring: `utmsource=instagram&utmmedium=social&utm_campaign=bio`.

What to ignore

Sessions, bounce rate, average engagement time, and real-time user counts are almost never actionable for a lead-generation site. A UAE business site exists to produce enquiries; measure enquiries. If a metric cannot change what you do next week, it does not belong in the weekly review — the same discipline that decides which pages a company website actually needs.

A 30-minute monthly routine

1. Key events by landing page — find the best and worst converters. 2. Key events by channel — see which sources deserve more effort. 3. Search Console queries — spot titles that underperform their impressions. 4. Check one enquiry path end-to-end (fill your own form, click your own WhatsApp link) to catch silent breakage. 5. Note one change to make — a CTA, a title, an internal link — and make it.

That routine is more effective than any dashboard subscription, and it feeds directly into the pre-launch and post-launch checks in the SEO checklist before launching a website.

Setting up the three events without a full-time developer

Google Tag Manager (no code on the page). Create a GTM account, add the container snippet once, then build three triggers: a click trigger where the click URL contains `wa.me`, one where it contains `tel:`, and a form-submission trigger. Each fires a GA4 event tag. This is the route to prefer if marketing will change tracking without waiting on a developer.
A few lines directly on the site. If your developer already added the GA4 tag, they can attach a small script that sends a GA4 event when someone clicks a WhatsApp or phone link, or completes a form. This is leaner and fine for a site that rarely changes its tracking needs.

Either way, verify before you trust it: open GA4's Realtime report on one screen, click your own WhatsApp button, phone link, and submit your own form on another, and confirm each event appears. Tracking you have not personally tested is tracking you should assume is broken — the same "check one enquiry path end-to-end" discipline in the monthly routine above.

Consent, privacy, and clean data in the UAE

Tell visitors you use analytics in a plain privacy policy, and if you serve EU visitors or run ads, add a consent banner that gates non-essential tags. The broader policy-and-trust picture is in the UAE website compliance guide.
Do not put personal data in event names or parameters. Never send names, emails, or phone numbers into GA4 as event values — track that a form was submitted, not who submitted it.
Filter your own traffic. Exclude your office IP and your developer's so internal clicks do not inflate the numbers you make decisions on.
Keep UTM tags free of personal data and consistent, so attribution stays clean without leaking anything sensitive.

Good measurement and good privacy are not in tension here: tracking enquiry actions rather than identities gives you everything you need to improve the site and nothing you have to worry about storing.