WhatsApp conversions in Google Ads: count chats, not taps.

To count WhatsApp chats as Google Ads conversions, record the conversion when a message actually arrives, not when someone taps the WhatsApp button. That means keeping the gclid from the ad click attached to the person who ends up messaging you, and importing the chat into Google Ads as an offline conversion. Then do the same for the sale. Google learns from people who wrote to you and people who paid, instead of everyone whose thumb touched the button.

Why is a WhatsApp button tap a bad Google Ads conversion?

Because it measures intent to open an app, and nothing after that. The usual setup is a click trigger in Tag Manager on any link to wa.me, marked as a conversion. It takes ten minutes and it reports the moment WhatsApp opens. Whether anyone typed a word is not part of the data.

Google’s own message assets work the same way. When a Search or Performance Max ad carries a WhatsApp number, Google adds a Leads from Messages goal, as its message assets help page describes. Google Ads Liaison Ginny Marvin confirmed in November 2024 that a click on the message asset is reported as a conversation started, as Search Engine Roundtable reported. So the conversation column counts clicks with a friendlier name.

The question PPC forums keep asking is the obvious one: how do I count only the people who actually send a message? The gap between taps and messages is the gap between what Google is optimising for and what the business wants. Smart Bidding finds whoever looks most like your conversions. If the conversion is a tap, it gets very good at finding tappers.

What should count as the WhatsApp conversion?

Three events are worth separating, and each deserves its own conversion action:

• The tap. Keep it, as a secondary action. It is useful for spotting a broken button or a landing page nobody engages with. It should not steer bids.
• The received message. A real person wrote to you from a real ad click. This is the primary conversion for most businesses that sell over WhatsApp.
• The sale. The booking, the order or the signed quote that came out of the chat, with its value. This is the signal worth paying Google to chase.

The message and the sale both happen outside your website, so neither can be counted by a tag. Both have to be imported, and both need the click ID that started them.

How do you connect a WhatsApp chat to the ad click?

By making sure the click survives the trip. With auto-tagging on, every Google Ads click lands with a gclid in the URL. The job is to keep that click attached to the person who ends up writing to you, and there are three routes that do it:

• Ad, landing page, WhatsApp button. The usual path. Your landing page already holds the click, the campaign and the keyword, so the chat it starts can carry them.
• Ad, branded WhatsApp page, WhatsApp. For ads aimed straight at chat. The ad lands on a short page in your branding that looks like the familiar “continue to WhatsApp” screen, and the click is recorded before the visitor leaves.
• Tracked link, WhatsApp. For your Google Business Profile and anywhere else with no website journey. Each link knows what it was for.

Joining the click to the message that follows is the hard part. Done by hand, it means reading every first message and guessing its campaign, which works for about a week. Google’s open-source WCI project is a do-it-yourself option. It runs on Google Cloud and is labelled as not an officially supported Google product, so it suits a team with engineers to spare.

Expect some chats with no click behind them: the customer who saved your number months ago, a forwarded message. Those chats are still leads. They just cannot be credited to a click, and should be counted as WhatsApp leads without a campaign rather than guessed.

How do you import WhatsApp conversions into Google Ads?

As offline conversions keyed on the gclid. Google’s offline conversion setup guide lists the requirements: auto-tagging switched on, and each gclid stored with the lead it belongs to. The steps:

1. Create two conversion actions with the import source, one for a received WhatsApp message and one for a WhatsApp sale. Set the message as primary, or the sale if you have the volume.
2. Upload each matched chat with its gclid, the conversion action name and the time the message arrived. The gclid is case sensitive, so copy it exactly.
3. Upload the sale later against the same gclid, with its value, when the chat turns into a booking.
4. Demote the tap to a secondary action, so it stays in reports and out of bidding.

Timing matters. Google’s offline conversion imports FAQ says a gclid conversion can be uploaded as long as it is no more than 90 days old, and enhanced conversions using personal data no more than 63 days. A slow sales cycle should upload the message the day it arrives and the sale whenever it lands, inside that window.

What about chats from Meta campaigns?

A Meta placement that opens WhatsApp directly is a different case, because the chat never touches your website and there is no gclid to carry. Meta sends its own click ID with the first message instead. Meta and Google each want their own conversions back, so a business running both needs both loops. WhatsApp lead tracking covers the Meta click ID and the other ways to attribute a chat.

How does Lead Source handle WhatsApp chats from Google Ads?

Lead Source for WhatsApp, now in closed beta, does the join for you across all three routes, without a cloud project. When a message reaches your WhatsApp Business number, it arrives as a lead with the visit’s channel, campaign, gclid, landing page and journey.

A lead is created only when a real message arrives. A tap never counts, three messages in a row count once, and a chat with no click behind it arrives as a WhatsApp lead with no campaign rather than a guess. Each WhatsApp lead from a Google click carries the gclid you need for the import. Google Ads lead tracking covers how Lead Source records the click side for form leads too.

Where should you start?

With a week of counting by hand. Note the taps Google Ads reports, then count the WhatsApp chats that actually arrived over the same days. If the second number is much smaller, your bidding has been learning from the first one.

Then switch the primary conversion to a received message, keep the tap as secondary, and start importing. Give Smart Bidding a few weeks on the new signal before judging it. It has a lot of tappers to forget.