On this page
- What GA4 records when someone clicks a WhatsApp button
- Why a dedicated WhatsApp event is worth it
- Method 1: No code, with WhatsLink PRO
- Method 2: Google Tag Manager
- Option A: a Just Links trigger (plain links only)
- Option B: the whatslink:click event (links and chat widgets)
- Method 3: gtag code
- Option A: one hand-made button
- Option B: every button, with the free plugin
- Mark the event as a key event
- Where to see the clicks in GA4
- What GA4 numbers leave out
- Which method should you use?
- FAQ
- Official sources
What GA4 records when someone clicks a WhatsApp button
Out of the box, GA4 has no WhatsApp event. If Outbound clicks is on in enhanced measurement, it logs a generic "click" event each time a visitor clicks a link that leads to another website, wa.me and api.whatsapp.com included, with the destination in link_url and outbound set to true. Chat widgets that open WhatsApp from JavaScript, without a link, don't produce it.
Why a dedicated WhatsApp event is worth it
An event called whatsapp_click is easy to find in reports, can be marked as a key event, and can become a Google Ads conversion. GA4 attributes it to the session's source, medium, and campaign, so you can see which campaigns bring WhatsApp clicks, for the visitors whose browser loaded the Google tag.
Method 1: No code, with WhatsLink PRO
The free WhatsLink Click Tracker plugin detects every click on a WhatsApp, Telegram, or phone link, including chat widgets such as Click to Chat and Joinchat, which open WhatsApp from JavaScript. WhatsLink PRO sends each of those clicks to GA4 from a settings page.
- Install the free WhatsLink Click Tracker (1.6.0 or later) and WhatsLink PRO.
- Open WhatsLink Click Tracker → Ad Conversions.
- Under Google Analytics 4, tick Send an event for every click and save.
- Click a WhatsApp button on your site, then look for the event in GA4’s Realtime report.

Each click arrives as whatsapp_click, telegram_click, or phone_click, with the clicked link in a link_url parameter. PRO uses the Google tag your site already loads and adds no tracking code of its own, so your cookie banner keeps applying. On a site that uses Tag Manager without the Google tag, PRO pushes the same event to the data layer instead, and a GA4 Event tag with a Custom Event trigger in your container has to pass it on to GA4. If the page has neither, nothing is sent.
Method 2: Google Tag Manager
Option A: a Just Links trigger (plain links only)
- In Tag Manager, open Variables → Configure and enable the built-in
Click URLvariable. - Create a trigger of type Click – Just Links that fires on Some Link Clicks where
Click URLmatches the RegExwa\.me|whatsapp\.com. It covers wa.me, api.whatsapp.com, and web.whatsapp.com, which some chat plugins use on desktop. - Create a Google Analytics: GA4 Event tag with the event name
whatsapp_clickand a parameterlink_urlset to{{Click URL}}. Attach the trigger. - Test it in Preview mode, then publish the container.
This only sees real links. Chat widgets that open WhatsApp from JavaScript, with no link on the page, never fire a link-click trigger.
Option B: the whatslink:click event (links and chat widgets)
Since version 1.6.0, the free WhatsLink Click Tracker announces every click it logs with a whatslink:click browser event, chat widgets included. A small Custom HTML tag turns it into a data layer event that any GA4 or Google Ads tag can use. The step-by-step setup is in Track WhatsApp Button Clicks in Google Tag Manager.
Method 3: gtag code
Option A: one hand-made button
If your site loads GA4 with gtag.js and you have one hand-made WhatsApp link, you can send the event from the link itself:
<a href="https://wa.me/391234567890"
onclick="if (window.gtag) { gtag('event', 'whatsapp_click', { link_url: this.href }); }">
Chat on WhatsApp
</a>
It works, but you have to repeat it on every button, and it can’t reach buttons generated by a plugin or a page builder.
Option B: every button, with the free plugin
With the free WhatsLink Click Tracker installed, a few lines send an event for every button and chat widget it detects. Add them to your site’s footer, for example with a code snippets plugin:
<script>
document.addEventListener('whatslink:click', function (event) {
if (typeof window.gtag === 'function') {
gtag('event', event.detail.channel + '_click', { link_url: event.detail.url });
}
});
</script>
The event name becomes whatsapp_click, telegram_click, or phone_click, the same names WhatsLink PRO uses. Don’t combine this snippet with PRO’s GA4 option, or each click is sent twice.
Mark the event as a key event
A key event (what GA4 used to call a conversion) shows up in your key event reports and can be imported into Google Ads.
- In GA4, open Admin → Data display → Events.
- If
whatsapp_clickis in the Recent events list, click the star next to it to mark it as a key event. - New events may not appear in the list right away. To mark one ahead of time, click Create event on the same page, enter the exact name,
whatsapp_click, turn on Mark as key event and click Create. Event names are case-sensitive.
Marking is not retroactive: only clicks collected afterwards count as key events. To use them as Google Ads conversions, see WhatsApp Conversion Tracking for Google Ads and Meta Ads.
Where to see the clicks in GA4
- Reports → Engagement → Events: the
whatsapp_clickcount and the users who triggered it. - Explore → Free form: filter on the event name, then break it down by Session source / medium, Session campaign, or Page path and screen class to see which campaigns and pages bring WhatsApp clicks.
- To see which number or link was clicked, add the Link URL dimension. GA4 fills it from the
link_urlparameter, so all the methods above populate it without a custom dimension.

To put these numbers in a shareable report, see how to build a WhatsApp analytics dashboard in Looker Studio.
What GA4 numbers leave out
GA4 can only count clicks from visitors whose browser loaded the Google tag. Visitors who decline analytics cookies (where your consent setup blocks the tag), ad blockers, and privacy browsers all reduce the count. Reports with small numbers over a short date range can also be withheld by GA4’s data thresholds. So the GA4 total can be lower than the real number of clicks.
GA4 and a click log stored in WordPress record the same click differently:
| GA4 event | Click log in WordPress | |
|---|---|---|
| Where it is stored | Your GA4 property | Your WordPress database |
| Needs the Google tag to load | Yes | No |
| Campaign | The session’s source, medium, and campaign | The UTM parameters in the address of the page where the click happened |
| What else you can see | Sessions, users, devices, and other events | One row per click: page, link, date, referrer |
| What happens in WhatsApp | Not visible | Not visible |
The chat itself is not a website session, so neither tool knows whether the visitor sent a message; what WhatsApp itself can report is covered in WhatsApp Analytics: Chat Stats and Website Click Tracking. WhatsLink’s own click log records every click it detects, without IP addresses or location. Comparing the two totals tells you how much GA4 is missing.
Which method should you use?
- A chat widget (Click to Chat, Joinchat, WP Social Chat…) and no time for code: Method 1.
- A chat widget, you already use Tag Manager: Method 2, option B.
- A chat widget, no Tag Manager, comfortable pasting a snippet: Method 3, option B.
- Only plain wa.me links, and you already use Tag Manager: Method 2, option A.
- One hand-made button: Method 3, option A.
What WhatsLink adds to GA4
- Every WhatsApp, Telegram, and phone click, chat widgets included (free)
- A whatslink:click event for Tag Manager or your own gtag code (free)
- whatsapp_click, telegram_click, and phone_click events in GA4 without code (PRO)
- The same clicks as Google Ads conversions and Meta Pixel Contact events (PRO)
- A click log in WordPress with page, UTM parameters, and referrer (free)
FAQ
Does GA4 track WhatsApp clicks automatically?
Partly. With Outbound clicks turned on in enhanced measurement, a click on a plain wa.me or api.whatsapp.com link creates a generic "click" event with the destination in link_url and outbound set to true. There is no dedicated WhatsApp event, and chat widgets that open WhatsApp from JavaScript, without a link, don't create it.
What event name should I use for WhatsApp clicks?
There is no official name. Use lowercase with underscores, such as whatsapp_click. WhatsLink PRO uses whatsapp_click, telegram_click, and phone_click, with the clicked link in link_url. Pick one name and keep it: renaming later splits your data.
Can GA4 show which campaign brought a WhatsApp click?
Yes. Events are attributed to the session's source, medium, and campaign. In an Exploration, filter on your WhatsApp event and break it down by Session campaign or Session source / medium. Campaign names come from the UTM parameters of the landing page or from linked ad accounts.
Why does GA4 show fewer WhatsApp clicks than my click log?
GA4 only counts visitors whose browser loaded the Google tag. Declined cookie consent (when your setup blocks the tag), ad blockers, and privacy browsers reduce the count, and data thresholds can withhold small numbers. A click log stored in WordPress, like WhatsLink's, does not depend on the Google tag.
Do I need Google Tag Manager to track WhatsApp clicks in GA4?
No. You can send the event with gtag from the button itself, use a short snippet that listens to the free WhatsLink plugin's whatslink:click event, or let WhatsLink PRO send it from a settings page. Tag Manager is useful if you already manage your tags there.