How to know which ads drive the sales that close on WhatsApp

Short answer: to know which ads drive the sales that close on WhatsApp, you need to tag the source of every conversation the moment it starts, bring that conversation into a CRM, record the sale on the same record and send the result back to Meta and Google. Without these four steps, the ad gets credit for the click and the sale disappears from the report.

In this article

  • Why WhatsApp is a black hole for measurement
  • The three paths a lead takes to WhatsApp
  • How to tag the source on each path
  • From WhatsApp to the CRM without losing information
  • How to send the sale back to Meta and Google
  • The report you end up with
  • Frequently asked questions

Why WhatsApp disappears from the report

In ecommerce, the sale happens on the website and the pixel records the purchase with its value. On WhatsApp, it does not. The person clicks the ad, opens the chat, negotiates for days, sends a payment receipt, and none of that passes through the browser. For Meta and Google, the story ends at the click or the conversation started.

The result is familiar: the ads manager shows "conversations started" and the business owner cannot say which of them turned into money. Without that information, budget is allocated in the dark, and the platform keeps optimizing for people who start conversations, not for people who buy.

The three paths to WhatsApp

PathHow the lead arrivesWhere the source can get lost
Click-to-WhatsApp adThe Meta ad opens the chat directlyThe chat arrives with no campaign tagged if the number is not integrated
Website or landing page with a buttonThe person clicks the ad, goes to the site and then taps the WhatsApp buttonIn the jump from the site to the app, the URL parameters are left behind
Search and Google profileThe person finds the number on Google or MapsThere is no trackable click, only the conversation

How to tag the source on each path

Click-to-WhatsApp ads

When the number is connected to the official WhatsApp Business API, Meta sends, along with the first message, an identifier for the ad that started the conversation. An integrated CRM can read that information and save the source campaign and ad on the contact record. That identifier is also what later lets you send the sale back to Meta.

If the number runs on the regular app, without integration, this information is not available in an automated way. A simple alternative is to use different opening messages per campaign, such as "Hi, I saw your summer promotion ad", but it depends on the person not deleting the text.

WhatsApp button on the website

This is where the biggest loss happens. The person arrives on the site with UTMs and a click identifier in the URL, browses and taps the button. The site needs to:

  1. Store the UTMs and click identifiers (gclid, fbclid) in a cookie or in browser storage as soon as the person arrives.
  2. Generate a short reference code for that visit.
  3. Include that code in the pre-filled WhatsApp message, such as "Hello, I would like a quote [ref: AB12]".
  4. Send the CRM, at the same moment, a record linking the code to the stored sources.

When the conversation arrives with the code, the CRM matches the message to the visit and fills in the source automatically. This is what we do on the EMB-S website and on our clients' websites.

Organic search and Google Maps

For your Google profile, use a dedicated WhatsApp link on the profile button or a specific opening message. That way you can at least separate people who came from Maps from those who came from ads. Search traffic to the website is already covered by the button method.

From WhatsApp to the CRM without losing information

Tagging the source only helps if it is saved somewhere the team uses. The flow we build has these steps:

  1. The conversation enters the CRM automatically, with name, phone, source and the text of the first message.
  2. The lead lands in an initial pipeline stage, with an assigned owner. If an AI agent handles first contact, it fills in the qualification answers.
  3. The salesperson runs the conversation inside the CRM or with synced history, so nothing stays only on their phone.
  4. When it closes, the salesperson marks the deal as won and enters the value. This field is required for the "won" stage.

If the team answers on personal phones, measurement breaks again: the conversation and the sale stay outside the system. Centralizing service on one official number, accessible to the team inside the CRM, is what makes measurement possible. Read more in the article on CRM for small businesses.

Sending the sale back to Meta and Google

With the sale recorded and the source saved, all that is left is telling the platforms.

On Meta

The CRM sends a purchase event through the Conversions API, with the value, the currency and the contact's hashed data. For conversations that started on click-to-WhatsApp ads, Meta offers a specific event format for messaging, which uses the ad identifier. That way Meta links the sale to the ad and starts looking for people similar to buyers. Details in the article on the Meta Conversions API.

On Google Ads

If the lead came from a Google click, the gclid saved on the record lets you import the offline conversion with the sale value. Another option is enhanced conversions for leads, which use hashed email and phone to make the match. In both cases, the import can be automated from the CRM.

The report you end up with

CampaignSpendConversationsSalesRevenueCost per sale
Meta: click to WhatsAppUS$ 4,00032018US$ 27,000US$ 222
Meta: website with buttonUS$ 2,00011011US$ 19,800US$ 182
Google: searchUS$ 3,00014016US$ 30,400US$ 188

Illustrative numbers, to show the format of the reading.

With a table like this, the question "where should I put more budget" finally has an answer. In the example, the campaign with the most conversations is not the one with the best cost per sale.

Common mistakes

  • Using several WhatsApp numbers without control, each salesperson with their own, without integration.
  • Not saving the source at first contact, only when the lead becomes a customer, when the information is already lost.
  • Marking sales without a value, which makes it impossible to calculate return.
  • Counting conversations from existing customers as new campaign leads.
  • Waiting until the end of the month to record sales, which delays platform optimization.

Example rollout at a service company

To make the process concrete, here is how the rollout looks at a company that sells services over WhatsApp and advertises on Meta and Google:

  1. Week 1: centralize service on one number on the official API, connected to the CRM, and move salespeople to answer inside the system.
  2. Week 1: standardize UTMs across all campaigns and add the reference code to the website's WhatsApp button message.
  3. Week 2: build the pipeline with simple stages and make the value required at the won stage.
  4. Week 2: set up automatic sending of qualified lead and purchase events to Meta, and offline conversion imports to Google Ads.
  5. Week 3: check, campaign by campaign, whether conversations arrive with the source filled in and whether marked sales show up on the platforms.
  6. Week 4 onward: read cost per sale by campaign and move budget to what sells.

The technical part usually takes less time than changing the team's habits. Salespeople used to answering on their own phones resist at first. The argument that usually convinces them is simple: with everything in the CRM, no lead is lost during vacations, follow-ups show up as tasks and commissions are easy to prove.

How much of the sales can be attributed

Even with everything set up, some sales will arrive without a clear source: the customer who saved the number and came back months later, the referral from a friend who saw the ad, the person who switched phones. That is normal. The goal is not to attribute 100% of sales, but to have a sample large and reliable enough to compare campaigns with each other. If most sales arrive with a source, budget decisions are already much safer than in the dark.

Frequently asked questions

Do I need the official WhatsApp API?

To measure automatically and send the sale back to Meta with the ad identifier, yes, it is the recommended path. Without it, you can measure partially with different opening messages and reference codes, but with more manual work.

What if the sale happens weeks after the conversation?

No problem. The source is saved on the record from the first contact. When the sale is marked, the CRM knows where it came from, and the platforms accept conversions sent days after the click, within each one's windows.

Can I measure phone calls the same way?

Yes, with tracking numbers per campaign or with the source recorded by the person answering. The logic is the same: source at first contact, sale on the same record.

Summary

  • WhatsApp sales do not pass through the pixel, so they disappear from the report.
  • Tag the source at first contact: official integration for click-to-WhatsApp and a reference code on the website button.
  • Centralize service in a CRM with an official number and mark sales with a value.
  • Send the sale back to Meta through the Conversions API and to Google through offline imports.
  • The result is cost per sale by campaign, which is what decides the budget.