Conversion Tracking Across Your Website: Forms, Calls and WhatsApp

Website conversion tracking means recording every meaningful action a visitor takes — submitting a form, tapping to call, opening a WhatsApp chat — as an event in your analytics, so you can see which channels and pages produce enquiries. For most businesses, the reliable way to do this is with Google Tag Manager sending clearly named events to GA4, which are then marked as key events and tested before you rely on them.

This guide covers the three contact methods UAE businesses use most and how to track each properly. Setting up the same actions as conversions inside Google Ads is covered separately in our Google Ads conversion tracking checklist.

Plan before you tag

Write a short tracking plan first. It saves rework and makes reports readable.

Action	Event name	Useful parameters	Key event?
Contact form submitted successfully	generate_lead	form_name, service	Yes
Phone number tapped	click_call	link_url, page_location	Yes
WhatsApp link clicked	click_whatsapp	link_url, page_location	Yes
Quote form started	form_start	form_name	No
Brochure downloaded	file_download	file_name	Optional

Use lowercase names with underscores, keep them consistent, and reuse Google's recommended event names (such as generate_lead) where they fit. Register any parameter you want to see in reports as a custom dimension in GA4.

Tracking form submissions

Forms are the most common and the easiest to get wrong. GA4's enhanced measurement can detect form interactions automatically, but it often misfires — counting failed submissions or missing forms that don't reload the page. Treat it as a rough signal, not your key event.

More reliable options, from best to acceptable:

1. A dataLayer push on success. Your developer adds a small snippet that runs only when the form submits successfully — for example, dataLayer.push({event: 'form_success', form_name: 'contact'}). In Tag Manager, a Custom Event trigger listens for it and fires a GA4 event tag.
2. A thank-you page. Redirect to a unique URL after submission and trigger on that page view. Make sure the page can't be reached any other way and isn't indexed.
3. Element visibility. Trigger when a success message appears on screen. Workable when you can't change the form code, but fragile if the design changes.

Avoid triggering on the submit button click — it fires even when validation fails.

Tracking phone calls

On mobile, most calls start with a tap on a tel: link. In Tag Manager:

• Enable the built-in Click URL variable.
• Create a Click – Just Links trigger where Click URL starts with tel:.
• Fire a GA4 event tag named click_call, passing the page location.

This measures intent to call, not a connected call. If phone enquiries are a major source for you, a call tracking service with dynamic number insertion can show which calls connected and how long they lasted, attributed to the visitor's source. Whatever you use, be clear in reports that a click and a conversation are different things.

Tracking WhatsApp

WhatsApp is often the preferred contact method in the UAE, so it deserves the same care as forms.

• Most WhatsApp buttons link to wa.me/ or api.whatsapp.com/. Create a link-click trigger where Click URL contains either, and fire click_whatsapp.
• If your button is a third-party widget that opens a chat window rather than a link, the click may not register as a normal link. Check whether the widget provides its own events or callbacks, or use a Click – All Elements trigger on the widget's element.
• Pre-filled messages (using the text parameter in the link) can include a page or campaign reference, which helps your team see where the chat began.

Like call taps, a WhatsApp click shows intent. The actual conversation happens outside your website. To connect clicks to real enquiries, log each chat in your CRM with its source — see connecting your website and ads to a CRM.

Consent mode

If your site uses a consent banner, Tag Manager tags should respect visitors' choices. Google's consent mode passes consent states (such as analytics_storage and ad_storage, plus ad_user_data and ad_personalization) to Google tags, which then adjust their behaviour. Make sure your consent platform sets these defaults before tags fire. Data protection requirements in the UAE, including the Personal Data Protection Law and free zone regimes, should be confirmed with a legal adviser; your tracking setup should reflect whatever approach you adopt.

Test before you trust

Never publish tracking without testing it.

1. Open Tag Manager Preview mode and complete each action on the real site — including a failed form submission, which should not fire anything.
2. Check that each tag fires once per action, not twice.
3. Use GA4 DebugView to confirm events arrive with the right parameters.
4. Publish the container with a descriptive version name, such as "Add WhatsApp and call tracking".
5. After a few days, compare GA4 counts with the enquiries your team actually received.

Then mark the events as key events in GA4 Admin so they appear in acquisition reports.

Ongoing maintenance

Tracking breaks quietly. Redesigns, new form plugins and changed button links are common culprits. Add a tracking check to your launch checklist for any site change, and review key event trends monthly using the routine in our GA4 reporting guide.

Key takeaways

• Write a tracking plan with consistent event names before setting anything up.
• Track form submissions on success, not on button clicks.
• Track tel: and WhatsApp links as intent, and use a CRM or call tracking to measure outcomes.
• Respect consent choices through consent mode.
• Test in Preview and DebugView, then reconcile with real enquiries.

Wot Digital sets up measurement as part of our digital marketing services, so campaign decisions rest on numbers you can trust.