How to Track WhatsApp and Click-to-Call Leads in GA4 and Google Tag Manager

Why WhatsApp and Phone Clicks Disappear From Your Analytics

On a lot of service-business websites, the contact form is not where most enquiries start. Visitors tap a floating WhatsApp button, the number in the top bar, or a “Call now” link in the footer. GA4 does not treat any of those taps as a lead by default. Unless you set something up, a visitor who opens WhatsApp from your homepage looks the same in your reports as a visitor who read one page and left.

GA4’s enhanced measurement can record outbound clicks, and a wa.me link usually counts as one. The trouble is that it arrives as a generic click event mixed in with every other external link on the site: your Facebook icon, a link to a supplier, a citation in a blog post. You cannot sensibly mark that as a key event. Phone links (tel:) point to no domain at all, so do not count on enhanced measurement to cover them.

The fix is to send your own, clearly named events when someone clicks a WhatsApp or phone link, then tell GA4 that those events matter. This guide covers both ways to do it — Google Tag Manager and plain gtag.js — plus testing and the mistakes we see most often when auditing tracking setups.

Plan Your Event Names Before You Touch GTM

Google’s event naming rules are short: names are case-sensitive, must start with a letter, and may only use letters, numbers, and underscores, with a 40-character limit. Some names, including click and page_view, are reserved for events GA4 collects itself, and parameter names cannot begin with prefixes such as google_, ga_, or firebase_. Most importantly, once an event has months of data behind it, renaming it splits your history in two. Decide the names once and write them down.

You have two reasonable options. Google’s recommended generate_lead event is fine if you want a single lead event with a parameter that says where it came from. Separate custom events are easier to read in reports and easier to mark as separate key events. For most small business sites we prefer separate events, because the owner wants to see “WhatsApp vs phone” at a glance without building an exploration.

A simple naming plan for contact clicks

Action	Event name	Useful parameters
Tap on any WhatsApp link	whatsapp_click	link_url, click_location
Tap on any tel: link	phone_click	link_url, click_location
Tap on a mailto: link	email_click	link_url, click_location
Contact form submitted successfully	generate_lead	form_name

The click_location parameter is the one that pays off later. Knowing whether people use the floating button, the header number, or the footer tells you which placement earns its space. If you are deciding where those buttons should go in the first place, our landing page design guide covers placement and CTA hierarchy.

Method 1: Track WhatsApp and Call Clicks With Google Tag Manager

Use this method if GTM is already installed, or if you expect to add more tracking later. If your GA4 tag is currently hardcoded in the page <head>, read the common mistakes section first — running both setups at once is the most frequent cause of doubled data.

Step 1: Enable the built-in click variables

1. In your GTM container, open Variables.
2. Under Built-In Variables, click Configure.
3. Tick Click Element, Click Classes, and Click URL in the Clicks group.

Step 2: Create a variable that records where the click happened

Create a new user-defined variable of type Custom JavaScript and name it CJS – Click Location. Adjust the selectors to match your own markup. The ones below match a typical layout with a floating button, a top bar, a header, and a footer.

function () {
  var el = {{Click Element}};
  if (!el || !el.closest) { return 'unknown'; }
  if (el.closest('.whatsapp-fab')) { return 'floating_button'; }
  if (el.closest('.top-bar, header')) { return 'header'; }
  if (el.closest('footer')) { return 'footer'; }
  return 'content';
}

Because the trigger in the next step only fires on links, {{Click Element}} will be the <a> element itself, so closest() starts from the link and walks up.

Step 3: Create the two triggers

1. Go to Triggers → New and choose Click – Just Links.
2. Select Some Link Clicks.
3. For WhatsApp, set the condition to Click URL — matches RegEx (ignore case) — and use the pattern below.
4. Save it as Click – WhatsApp, then repeat for phone with Click URL — starts with — tel:, saved as Click – Phone.

(^https?://(www\.)?(wa\.me|api\.whatsapp\.com|web\.whatsapp\.com)/)|(^whatsapp:)

Use the Just Links trigger type rather than All Elements. Many WhatsApp buttons contain an icon inside the link. With All Elements, a tap on the icon reports the icon as the clicked element, and Click URL comes back empty, so the trigger silently fails on exactly the taps you care about.

Step 4: Create the GA4 event tags

1. Go to Tags → New → Google Analytics: GA4 Event.
2. Enter your Measurement ID (it starts with G-).
3. Event name: whatsapp_click.
4. Add event parameters: link_url = {{Click URL}} and click_location = {{CJS – Click Location}}.
5. Set the firing trigger to Click – WhatsApp and save.
6. Duplicate the tag, rename the event to phone_click, and switch the trigger to Click – Phone.

Do not publish yet. Test first using the steps further down.

Method 2: Track Clicks With gtag.js and No Tag Manager

If your site already loads GA4 with the standard Google tag snippet and you do not want another tool, a short script does the same job. This is how we usually handle hand-coded sites: one listener on the document catches every matching link, including links added to the page later.

<script>
document.addEventListener('click', function (event) {
  var link = event.target.closest ? event.target.closest('a[href]') : null;
  if (!link || typeof gtag !== 'function') { return; }

  var href = link.getAttribute('href') || '';
  var eventName = null;

  if (/^tel:/i.test(href)) {
    eventName = 'phone_click';
  } else if (/^mailto:/i.test(href)) {
    eventName = 'email_click';
  } else if (/^(https?:\/\/(www\.)?(wa\.me|api\.whatsapp\.com|web\.whatsapp\.com)\/|whatsapp:)/i.test(href)) {
    eventName = 'whatsapp_click';
  }
  if (!eventName) { return; }

  var location = 'content';
  if (link.closest('.whatsapp-fab')) { location = 'floating_button'; }
  else if (link.closest('.top-bar, header')) { location = 'header'; }
  else if (link.closest('footer')) { location = 'footer'; }

  gtag('event', eventName, {
    link_url: href,
    click_location: location
  });
});
</script>

Place it just before </body>, or add it to a JavaScript file that is already loaded on every page. It relies on the gtag() function defined by the Google tag snippet in your <head>, so the snippet must stay in place. The typeof check stops the script from throwing an error if an ad blocker prevents the Google tag from loading.

Notice what the script does not do. It does not call preventDefault() or delay the link. Holding a visitor back for a few hundred milliseconds so that analytics can finish is a poor trade. Opening WhatsApp links in a new tab (target="_blank" with rel="noopener") keeps the current page alive while the event is sent.

Register Custom Parameters So They Show Up in Reports

GA4 receives click_location as soon as you send it, but standard reports will not show it until you register it as a custom dimension.

1. In GA4, go to Admin → Data display → Custom definitions.
2. Click Create custom dimension.
3. Dimension name: Click location. Scope: Event. Event parameter: click_location.
4. Save. The dimension only fills in for data collected after you create it, so do this on day one.

Test Everything in DebugView Before You Publish

DebugView shows events from debug-enabled devices within seconds, which makes it the right place to confirm the setup works. Standard reports can take a day or more to catch up, so they are no use for testing.

1. GTM users: click Preview in GTM. Tag Assistant opens your site in a connected window. GA4 tags fired in preview mode are automatically marked as debug traffic.
2. gtag.js users: connect your site in Tag Assistant (tagassistant.google.com), or temporarily add debug_mode: true to your config line as shown below. Remove it when you finish.
3. In GA4, open Admin → Data display → DebugView and pick your device if more than one appears.
4. Tap each WhatsApp and phone link on the site — header, footer, floating button, and any link inside page content.
5. Click each event in the DebugView timeline and confirm that link_url and click_location carry the values you expect.
6. Test on a real phone as well as desktop. Mobile is where most of these taps happen, and it is where a hidden duplicate button or an off-screen sticky bar tends to show up.

// Temporary: remove after testing
gtag('config', 'G-XXXXXXXXXX', { debug_mode: true });

In GTM preview, also check that each tag fires exactly once per click. If you see two whatsapp_click events for one tap, look for a second trigger or a hardcoded event that duplicates the tag.

Mark the Events as Key Events

Google renamed “conversions” to key events in GA4. Marking an event as a key event is what puts it into the key event columns of your reports and makes it available for import into Google Ads.

1. Once an event has arrived at least once, go to Admin → Data display → Events and switch on Mark as key event next to whatsapp_click and phone_click.
2. If an event has not appeared in that list yet, go to Admin → Data display → Key events → New key event and type the exact event name. Spelling and capitals must match.
3. Leave the counting method on Once per event unless you have a reason to count only one per session.
4. If you run Google Ads, link the accounts and import the key events from inside Google Ads, so bidding can use them.

Be honest with yourself about what these numbers mean. A whatsapp_click event records a tap that opened WhatsApp. It does not tell you whether a message was sent, and a phone_click on a desktop may open a calling app the visitor closes straight away. Treat these events as signs of strong intent, not as confirmed leads. One practical trick for closing the gap is to pre-fill the WhatsApp message with a short phrase (for example ?text=Hi%2C%20I%20found%20you%20on%20your%20website). Then your team can count, inside WhatsApp, how many conversations really started from the site.

Common Mistakes

• Running a hardcoded Google tag and a GTM Google tag at the same time. Both send page views, so every number doubles. Pick one place for GA4 to live. If you move to GTM, remove the hardcoded snippet in the same release.
• A regex that is too loose. Matching just the word whatsapp will also fire on an internal link to a blog post with “whatsapp” in its URL — like the address of this very article. Match the domains (wa.me, api.whatsapp.com) instead.
• Marking the generic click event as a key event. That counts every outbound link as a conversion and makes your key event rate meaningless.
• Changing event names after launch. GA4 does not merge old and new names. Keep a short tracking document so the next developer does not “tidy up” your naming.
• Testing on the live property without filtering yourself. Define internal traffic for your office IP under the data stream’s tag settings, and enable the data filter once you have checked it works, so staff clicks are excluded.
• Sending personal data. Never push a visitor’s name, phone number, or email address into event parameters. Your own business number in link_url is fine. Anything the visitor typed is not.

If you have not connected Search Console yet, do it alongside this work. Our Google Search Console setup guide shows which search queries bring visitors in. GA4 then shows which of those visitors tapped to call or chat.

Frequently Asked Questions

Can I track WhatsApp clicks in GA4 without Google Tag Manager?

Yes. If GA4 is installed with the standard Google tag snippet, a short click listener that calls gtag('event', 'whatsapp_click') whenever someone taps a wa.me or api.whatsapp.com link does the same job as a GTM trigger and tag.

Does GA4 know whether the WhatsApp message was actually sent?

No. GA4 records the tap that opened WhatsApp or the dialler. What happens inside WhatsApp or the phone app is invisible to your website. Pre-filling the WhatsApp message with a short phrase helps your team count real conversations that started from the site.

Should I use generate_lead or custom event names?

Either works. generate_lead is a Google recommended event and suits a single lead event with a parameter describing the source. Separate names such as whatsapp_click and phone_click are easier to read in reports and to mark as separate key events. Choose once and do not rename later.

Why do my events appear in DebugView but not in reports?

Standard GA4 reports can take 24 to 48 hours to process new data, and custom parameters only appear after you register them as custom dimensions. DebugView and the Realtime report show events almost immediately.

Can I use these key events in Google Ads?

Yes. Link your GA4 property to Google Ads, mark the events as key events in GA4, then import them as conversions inside Google Ads.