WhatsApp UTM Tracking: Tag Links and Attribute Chats

Add UTM parameters to links you share on WhatsApp so GA4 stops counting them as direct, and see which campaign led to each WhatsApp click on your site.

Updated Oct 24, 2026 8 min read
On this page
  1. WhatsApp UTM tracking in two directions
  2. And the other way round
  3. Two directions, two different problems
  4. Direction A: tag the links you share in WhatsApp
  5. The base template
  6. WhatsApp UTM naming conventions (chat, group, Status)
  7. Put a tagged link inside a wa.me share link
  8. Check the result in GA4
  9. What tags can’t tell you: forwarding
  10. Direction B: see which campaign led to a WhatsApp click
  11. Tagging ads that use click IDs
  12. What WhatsLink stores with each click
  13. The limit: UTMs are read from the page of the click
  14. The numbers worth watching
  15. Reports and ad conversions with WhatsLink PRO
  16. Mistakes that break WhatsApp attribution
  17. FAQ
  18. Official sources

WhatsApp UTM tracking in two directions

Links you share inside WhatsApp need UTM tags on the website URL, or GA4 can't tell where those visits came from and reports them as direct.

And the other way round

For visitors who click your WhatsApp button, tag your landing pages: a click logger saves the page's source, medium and campaign with every WhatsApp click.

WhatsApp UTM tracking covers two different jobs: tagging the links to your website that you share inside WhatsApp, so your analytics stops filing those visits as direct, and recording which campaign brought the visitor who then clicks the WhatsApp button on your site. Both work the same way: UTM parameters go on your own page URLs, never on the wa.me link.

This guide covers both directions, with naming templates you can copy, the checks to run in GA4, and the limits worth knowing before you trust the numbers.

Two directions, two different problems

People mix these up because both involve WhatsApp and UTMs. They answer different questions and you read them in different places.

A: WhatsApp → your siteB: your site → WhatsApp
What happensSomeone taps a link to your site that was shared in a chat, a group, a Status or a ChannelA visitor from an ad, email or post taps the WhatsApp button on your page
The problemThe visit can arrive with no source, so GA4 reports it as (direct) / (none)The conversation continues in the WhatsApp app, where your analytics can’t follow
Where the UTMs goOn the website URL you share in WhatsAppOn the landing page URL used in your ad, email or post
Where you read the resultGA4 acquisition reportsA click log that stores the page’s UTMs with each WhatsApp click (or GA4 events)
Two UTM flows: a tagged link shared in WhatsApp arriving in GA4 as whatsapp / social, and a tagged landing page whose UTMs are saved with the WhatsApp click
Direction A tags the links you share in WhatsApp; direction B tags the landing page, and the click log reads the UTMs from the page of the click.

One thing to drop right away: adding UTM parameters to a wa.me link does nothing for your analytics. That link opens a chat, not your website, so no analytics tag on your site ever sees those parameters.

When a link to your site carries no campaign tags and the visit brings no referral details, GA4 has nothing to classify it with and files it under (direct) / (none). Google lists links without UTM parameters as one cause of direct traffic. Tagging every website link you post in WhatsApp fixes that for your own links.

The base template

Keep three values fixed for a campaign and use the fourth to tell placements apart:

https://example.com/autumn-offer/?utm_source=whatsapp&utm_medium=social&utm_campaign=autumn_offer&utm_content=status
  • utm_source=whatsapp: the platform, always written the same way.
  • utm_medium=social: GA4’s Organic Social channel matches the medium social, and whatsapp is also on Google’s list of social sources, so these visits land in Organic Social. Keep paid-style mediums such as cpc or paid for real ads: with a social source they put the visit in Paid Social.
  • utm_campaign: the offer or message, such as autumn_offer.
  • utm_content: where you posted it (chat, group, Status). GA4 shows it as Session manual ad content.

You can build these by hand or with Google’s Campaign URL Builder, then paste the result into WhatsApp.

WhatsApp UTM naming conventions (chat, group, Status)

These are conventions, not WhatsApp requirements: WhatsApp has no official UTM format. What matters is that everyone on your team uses the same values.

Where you share the linkutm_contentExample ending of the URL
One-to-one chatschat…&utm_campaign=autumn_offer&utm_content=chat
A groupgroup_01, group_02……&utm_campaign=autumn_offer&utm_content=group_01
Your Statusstatus…&utm_campaign=autumn_offer&utm_content=status
Your WhatsApp Channelchannel…&utm_campaign=autumn_offer&utm_content=channel
A “Share on WhatsApp” button on your siteshare_button…&utm_campaign=autumn_offer&utm_content=share_button
  • Lowercase everything. GA4 treats values as case-sensitive: WhatsApp and whatsapp become two sources.
  • Use underscores, no spaces. Pick one separator and keep it.
  • Code your groups. group_01 in a shared sheet beats a group name in the URL, and keeps names and phone numbers out of your analytics.
  • Write the values down. A shared sheet with the approved campaign names stops autumn-offer and autumn_offer from splitting one campaign in two.

WhatsApp’s click-to-chat format https://wa.me/?text= opens WhatsApp with a pre-filled message and lets the person choose who to send it to. Put your tagged URL in that message, URL-encoded, and every forward of it carries your tags:

https://wa.me/?text=Take%20a%20look%20at%20our%20autumn%20offer%3A%20https%3A%2F%2Fexample.com%2Fautumn-offer%2F%3Futm_source%3Dwhatsapp%26utm_medium%3Dsocial%26utm_campaign%3Dautumn_offer%26utm_content%3Dshare_button

The tagged URL must be encoded, or the & characters end the text parameter early and your tags are lost. Any URL encoder does it; test the link once on your phone before you publish it.

Check the result in GA4

  1. Open one of your tagged links yourself and look for the visit in Reports → Realtime.
  2. After a day, open Reports → Acquisition → Traffic acquisition and look for whatsapp / social under Session source / medium.
  3. To compare placements, open the Manual report (Acquisition → Overview → View Manual campaigns) and add Session manual ad content.

Make sure your page doesn’t redirect to a URL without the parameters: Google warns that redirects can strip UTM parameters and that URL shorteners can strip referral details.

What tags can’t tell you: forwarding

Tags describe the link you sent out, not where it ended up. If someone copies your Status link into a group, the visits still say status. Read placement reports as “how this link variant performed”, not as a map of where it was shared.

Direction B: see which campaign led to a WhatsApp click

Here the campaign lives on your landing page. A visitor arrives from an ad or a newsletter on a tagged URL such as:

https://example.com/dental-implants/?utm_source=newsletter&utm_medium=email&utm_campaign=implants_october

When they tap your WhatsApp button, a click tracker reads the parameters still in the page address and saves them with the click. The click row then says: this page, this time, this source, medium and campaign.

Tagging ads that use click IDs

  • Google Ads auto-tagging adds a gclid to your URL, not UTMs, and GA4 gives auto-tagging priority over manual tags. GA4 is covered either way, but a tool that reads UTMs sees nothing. Add your UTMs in the Final URL suffix (account, campaign or ad group level), for example utm_source=google&utm_medium=cpc&utm_campaign=implants_october.
  • Meta Ads: add the same kind of parameters when you create the ad, in the Tracking section, in the URL parameters field (or with Build a URL parameter).
  • Email and social posts: tag the link by hand or with your email tool’s UTM option.

The free WhatsLink Click Tracker logs every click on WhatsApp, Telegram and phone links, chat widgets included, with the page title, the full page URL, the date, the clicked link, the referrer, and utm_source, utm_medium and utm_campaign in their own columns. It has no columns for utm_content or utm_term, but they stay visible in the page URL, which is stored in full.

To count the WhatsApp clicks a campaign produced, type its name in the search box: the search also looks in page addresses, where the UTMs are, and the total above the table is the count. Sorting by UTM Campaign groups the rows. For more on reading single rows, see who clicked your WhatsApp link: page, UTM and referrer per click.

The limit: UTMs are read from the page of the click

WhatsLink reads the UTMs from the address of the page where the click happens. If the visitor lands on /dental-implants/?utm_campaign=implants_october, then opens your contact page and clicks WhatsApp there, the parameters are no longer in the address and the UTM columns stay empty. The referrer column usually shows the landing page the visitor came from, which is a clue but not a report you can filter.

  • Put a WhatsApp button on every campaign landing page, so the click can happen where the tags are.
  • For the whole visit, use GA4 as well: its session dimensions (Session source, Session campaign) describe how the session started, so a WhatsApp event later in the visit still carries the campaign.

The numbers worth watching

Once tagged traffic is flowing, a few numbers answer most marketing questions. None of them needs WhatsApp itself.

  • WhatsApp clicks per campaign: from the UTM Campaign column of your click log.
  • Clicks per landing page: which pages turn campaign visitors into conversations.
  • Click rate per campaign: WhatsApp clicks divided by the campaign’s sessions in GA4. A campaign with fewer visits but more clicks per visit brings better-matched visitors. The method is in WhatsApp Button CTR: How to Measure and Improve It.
  • Share of clicks with a UTM source: if most clicks have none, your campaigns either aren’t tagged or visitors click on pages other than the landing page.
  • Clicks against chats received: some visitors open WhatsApp and never write. Compare for a couple of weeks before you call clicks “leads”.

The free log is enough to see the campaign of each click. WhatsLink PRO turns it into reports and sends the clicks onward:

  • Report filters by date range, UTM source, UTM medium and UTM campaign, with a daily trend chart, Top UTM Sources, Top Pages and a “Clicks with UTM” KPI.
  • Ad Conversions: every click as a Google Ads conversion, the Meta Pixel Contact event and a GA4 whatsapp_click event, using the Google and Meta tags already on your site. Your ad platforms then credit the campaign through their own click tracking, without depending on UTMs. Setup is in How to Track WhatsApp Clicks as Conversions in Google Ads and Meta Ads.
  • CSV export with the UTM columns, and daily or weekly summary emails.

Neither version knows who sent a message or connects to a CRM. If you need the campaign saved on the contact record, follow the steps to capture WhatsApp lead source in your CRM.

Mistakes that break WhatsApp attribution

  • Tagging the wa.me link instead of the page. Analytics never sees it.
  • Shorteners and redirects that drop the query string before the page loads.
  • Mixed spelling: WhatsApp, whatsapp and wa as three sources of one channel.
  • Personal data in UTMs: no names, phone numbers or emails in any value.
  • Counting share-button clicks as enquiries. A “Share on WhatsApp” button is also a wa.me link, so click trackers log it alongside chat clicks. Tell them apart by the clicked link: share links start with https://wa.me/?text=, with no phone number.

If you also want the WhatsApp click itself in GA4 reports, see How to Track WhatsApp Clicks in Google Analytics 4 (3 Ways).

What WhatsLink records for attribution

  • UTM source, medium and campaign with every WhatsApp click
  • Full page URL, referrer and clicked link per click
  • Chat widgets included: Click to Chat, Joinchat, WP Social Chat
  • PRO: report filters by date range and UTM values
  • PRO: clicks sent to Google Ads, the Meta Pixel and GA4
  • PRO: CSV export with the UTM columns
Get WhatsLink PRO

FAQ

What UTM parameters should I use for WhatsApp links?

A common convention is utm_source=whatsapp and utm_medium=social, a campaign name in utm_campaign, and the placement (chat, group_01, status, channel) in utm_content. GA4's Organic Social channel matches the medium social. Keep all values lowercase, because GA4 treats them as case-sensitive.

Can I add UTM parameters to a wa.me link?

You can, but they do nothing for your analytics: a wa.me link opens a chat, not your website, so no analytics tag on your site ever reads them. Put the UTMs on your own page URLs instead: on the link you share in WhatsApp, or on the landing page of your ad or email.

Why does traffic from WhatsApp show as direct in GA4?

When a link to your site has no UTM parameters and the visit carries no referral details, GA4 has nothing to classify it with and reports it as (direct) / (none). Tag the website links you share in WhatsApp and those visits appear as whatsapp / social.

Does WhatsLink record utm_content and utm_term?

Not in separate columns: WhatsLink stores utm_source, utm_medium and utm_campaign in their own columns. It saves the full page URL of each click, so utm_content and utm_term stay visible there. All values are read from the page where the click happens.

Do I need UTMs if I track WhatsApp clicks as conversions in Google Ads or Meta?

Not for the ad platforms: Google Ads and Meta credit each conversion to the ad through their own click tracking. UTMs are still useful for your own click log and for channels without click IDs, such as email and posts you share in WhatsApp.

Official sources

Related guides