What GA4 records when someone clicks your WhatsApp button
Google Analytics 4 records events that happen inside the browser session. With enhanced measurement enabled (or a custom event configured), GA4 can log that a user clicked a link to `wa.me`. What it records: the event occurred, which page the user was on, and — if the landing page URL was tagged with UTM parameters — which campaign brought that session. What it cannot record: anything after the user leaves the browser for the WhatsApp app. The session ends at the app boundary.
The attribution gap that happens at every WhatsApp click
When a visitor clicks your WhatsApp button, the browser hands off to the WhatsApp app and the HTTP referrer chain breaks. GA4 has no way to recover it. If that visitor returns to your site later via a different channel, GA4 attributes the new session to the new source — the original click is absorbed into the aggregate. A server-side click log, captured in PHP before the app switch, survives this gap because it doesn't depend on the browser session continuing.
What Google Analytics 4 actually measures
GA4 is a session-based analytics platform. It tracks what happens inside the browser: page views, scroll depth, time on page, clicks, and custom events you configure. For WhatsApp specifically, GA4 can record that a user clicked a `wa.me` link — but only if you’ve set up a click event via Google Tag Manager or gtag.js. Without that configuration, GA4 has no record of the click at all.
When the event is configured, GA4 stores it against the current browser session. This means you can see: how many WhatsApp click events occurred, which pages generated them, and which campaign brought the session (if the landing page URL had UTM parameters). That’s useful aggregate data.
What GA4 cannot do is retain any of this after the user switches to the WhatsApp app. The browser session ends at that boundary. The click event exists in GA4, but it’s a one-way door — you know someone clicked, not what they ultimately did, and if they return later, GA4 won’t connect that new session to the original click.
What a WhatsApp click tracker captures differently
WhatsLink PRO operates at a different layer. When a visitor clicks a WhatsApp button, the plugin executes a PHP request before the browser navigates away. It reads the current page URL — including any UTM parameters — and writes a click record to the WordPress database. This happens server-side, independent of the browser session.
The result is a log entry that contains:
- Source page URL
- Device type (mobile / desktop)
- Timestamp
- `utm_source`, `utm_medium`, `utm_campaign`, `utm_term`, `utm_content`
This record survives the app switch because it was written before the switch happened. It doesn’t depend on the referrer chain staying intact, and it’s not affected by what the user does after opening WhatsApp.
Where each tool has blind spots
**GA4 blind spots:**
- Attribution breaks at the WhatsApp app boundary
- Low-traffic pages may show zero WhatsApp events due to event sampling
- UTM data is session-scoped, not click-scoped — shared across all events in the session
- Requires configuration (GTM or gtag.js) to track WhatsApp clicks at all
**WhatsLink PRO blind spots:**
- Tracks only WhatsApp clicks, nothing else
- No funnel or session data — you see the click, not the journey before it
- Per-click CTR requires cross-referencing with GA4 page views for the denominator
When to use both
The recommended setup for any WordPress site running paid traffic or active content marketing: run both in parallel.
Use GA4 for: site-wide analytics, funnel analysis, audience segmentation, and aggregate WhatsApp click counts in your main dashboard.
Use WhatsLink PRO for: per-click attribution (“which campaign drove this specific click?”), per-page CTR analysis, device breakdown for WhatsApp clicks specifically, and CSV export when you need to reconcile click data with ad spend.
The two tools answer different questions. GA4 answers “how is my site performing overall?” WhatsLink PRO answers “where exactly are my WhatsApp conversations coming from?”
- GA4: aggregate event counts by page and time period
- GA4: session-level UTM data (landing page only, pre-click)
- GA4: device and audience breakdown across all site events
- WhatsLink PRO: per-click record with source page and timestamp
- WhatsLink PRO: UTM fields captured server-side at moment of click
- WhatsLink PRO: CSV export for offline analysis and attribution reporting
FAQ
Does Google Analytics track WhatsApp clicks?
Not automatically. GA4 requires a custom event to be configured — either via Google Tag Manager or gtag.js — to log clicks on wa.me links. Even then, GA4 records only that the click occurred. It cannot retain attribution data after the user switches from the browser to the WhatsApp app, which ends the GA4 session.
What's the difference between GA4 and a WhatsApp click tracker?
GA4 measures sessions and in-browser behaviour. A WhatsApp click tracker like WhatsLink PRO logs a specific event — the click on a WhatsApp button — server-side, independently of the browser session. GA4 gives you aggregate counts and funnel data; WhatsLink gives you a per-click record with UTM fields that persist after the app switch. They complement each other and serve different purposes.
Why does WhatsApp traffic show as direct in Google Analytics?
When a user taps a WhatsApp link, the OS switches to the WhatsApp app and the HTTP referrer is dropped. Any new browser session that user starts later will appear as direct traffic in GA4 because there is no referrer signal to attribute it to. The only way to preserve campaign attribution is to capture UTM data server-side at the moment of click, before the browser navigates away.
Do I need both GA4 and WhatsLink PRO?
For most WordPress sites running any kind of paid traffic or content marketing, yes. GA4 handles site-wide analytics, funnel analysis, and audience reporting. WhatsLink PRO handles WhatsApp click attribution specifically — answering 'which campaign or page drove this click?' in a way GA4 structurally cannot. If your only goal is knowing how many total WhatsApp clicks you receive, GA4 with a custom event is sufficient. If you need attribution, you need a server-side record.
Can I replace GA4 with WhatsLink PRO?
No. WhatsLink PRO tracks one specific event: clicks on WhatsApp links. It does not track page views, sessions, bounce rate, conversions, or any other site behaviour. It is a focused tool for WhatsApp click attribution. GA4 handles everything else. They are complementary, not interchangeable.
How do I know which UTM campaign drove a WhatsApp click?
If the visitor landed on your site via a tagged URL (e.g. ?utm_source=google&utm_campaign=brand), WhatsLink PRO reads those parameters from the page URL at the moment of click and stores them in the click log. GA4 also captures UTM data at the session level, but loses it after the app switch. WhatsLink PRO retains it because the capture happens server-side before the user leaves.