Yes, with conditions. Google allows a direct WhatsApp link as a final URL, but the Message asset is the better route for most accounts. Here is what is allowed, what breaks, and which to pick.
Short answer
You can set a https://wa.me/<number>?text=... link as the final URL of a Google Ads text ad, and Google will serve it. It passes policy as long as the destination is a working WhatsApp Business number that opens a chat, the ad makes it clear the click starts a chat, and the number matches the business in the ad. What you lose is landing-page data: Google cannot measure a conversion on WhatsApp’s domain, so the click is the last thing the platform sees unless you import conversions from your CRM.
The two ways to send Google Ads traffic to WhatsApp
Option 1, the Message asset (recommended). Add a WhatsApp message asset at the account, campaign or ad-group level. A “Chat now” button appears with the search ad, the click opens WhatsApp with a pre-filled greeting, and Google reports the message-click as its own interaction. Setup lives entirely inside Google Ads: Campaigns, then Assets, then Message, then your WhatsApp Business number and greeting.
Option 2, the wa.me final URL. Build the link as https://wa.me/919876543210?text=Hello%2C%20I%20want%20more%20information, use the international number without plus sign or spaces, URL-encode the text, and set it as the ad’s final URL. It works for campaigns where the whole point is the conversation and there is no landing page worth sending people to.
What breaks, from accounts we’ve run
- Disapprovals for destination mismatch. If the display path or the ad copy implies a website and the click opens WhatsApp, expect a “destination not working” or “misleading” flag. Say “Chat on WhatsApp” in the ad.
- No conversion data. The wa.me route gives Google clicks and nothing after. Smart bidding has nothing to learn from. Import qualified-lead conversions from your CRM with the GCLID, or the campaign will optimise for cheap clicks.
- Quality Score drift. Landing-page experience is scored on the final URL. wa.me is not your page, and the score settles low. Message assets avoid this because the final URL stays your site.
- Mobile only, in practice. On desktop the wa.me link opens WhatsApp Web, which many searchers are not signed into. Set device bid adjustments accordingly.
Which one to pick
| Situation | Use |
|---|---|
| You have a landing page and want chat as an extra door | Message asset |
| Local service, every lead is a conversation, no page | wa.me final URL, mobile-heavy bidding |
| You run smart bidding | Message asset, plus CRM conversion import |
| India, LatAm, MENA markets where WhatsApp is the phone | Either, but measure replies, not clicks |
Measure replies, not clicks
Whichever route you use, the number that matters is qualified conversations, not clicks. Put the campaign name in the pre-filled text so the first message tells you where the lead came from, log each conversation in a sheet or CRM with the date and the ad, and import the ones that became customers back into Google Ads as offline conversions. That is the only way the platform ever learns which WhatsApp clicks were worth paying for.
Frequently asked
Is wa.me allowed as a final URL by Google Ads policy? Yes. It is a working destination that does what the ad promises. Policy problems come from the ad copy, not the link.
Can I use api.whatsapp.com instead of wa.me? Yes, both resolve to the same chat. wa.me is shorter and the one Meta documents.
Does the Message asset work outside the US? Yes, wherever WhatsApp Business is available. Availability of the asset type in the interface has rolled out by region; if you do not see it, the wa.me route still works.
Can I track a WhatsApp conversion in GA4? Not directly. Track the click as an event on your site when you use a button, and track outcomes in your CRM.