Track WhatsApp and phone-call leads from your ads (UAE and India)
A plan to measure which ads and channels bring WhatsApp chats and phone calls that turn into customers: click-to-WhatsApp labels and the Conversions API for business messaging, WhatsApp button clicks on your website, Google call assets and call conversions, what works without Google forwarding numbers, source logging in your CRM, and the consent, recording and telemarketing rules. Legal points are checked for the UAE and India only; other places are not checked.
This is a practical, copy-paste process for most of your enquiries come by whatsapp or phone, and you cannot say which ads brought the people who paid. Use it when you want a clear structure, then add your own details.
Verified on 2026-11-0947 sources cited
Quick start
1. This is a first-pass check, not legal or tax advice. It covers the UAE and India. Other places are not checked. 2. Start a simple log, in a CRM (customer list tool) or a spreadsheet: first contact date, where the person came from, status, amount paid, and whether they agreed to more messages. 3. On the WhatsApp Business app, turn on Tools > Your customers’ activity, and use the ready-made labels (Lead, Paid and so on) within 7 days of the ad click. Custom labels may not count. 4. On the WhatsApp Business Platform (API), ask your provider to save the ad click ID with each chat and send leads and sales through Meta’s Conversions API. 5. For a WhatsApp button on your website, track the click as its own event. A click is not a lead until a chat really starts. 6. For Google call buttons: Google’s forwarding numbers are not listed for the UAE, so use a separate ad number and count call clicks. In India they work with limits, so count calls above a set length. 7. Do not record calls, make marketing calls, or send WhatsApp data to other tools until you have checked the rules here. 8. Judge each channel by cost per paying customer from your own log. Confirm with a qualified accountant or lawyer for your country.
Before you start
- You want to set up or improve a WhatsApp chatbot or AI assistant. This method only measures leads. Set up an AI support chatbot that customers trust
- You need general tag setup: the Google tag, GA4, the Meta Pixel, a consent banner or website purchase tracking. Set up conversion tracking with GA4, Consent Mode and Meta CAPI
- You already log outcomes in a CRM and only need the upload to Google, Meta or LinkedIn: stages, values, time limits and bidding switches. Send lead outcomes from your CRM back to your ad platforms
- Your leads come mainly from forms rather than chats or calls. Run lead form ads that bring real leads
- You want to paste real chats or call transcripts into an AI tool and need to know if that is safe. Use AI at work without leaking company data
- Your customers or business are outside the UAE and India. The platform steps may still help, but the legal rules here were not checked for other places.
- You sell alcohol, drugs, medical or healthcare products, gambling, dating or other goods on WhatsApp’s restricted list. Check the WhatsApp Business Messaging Policy with a lawyer before you build tracking on it.
Full method
How to use this method
- 1. Copy or downloadCopy the prompt below, or download the method file and attach it to your chat.
- 2. Paste into any AIChatGPT, Claude, Gemini or Copilot. Replace each [PLACEHOLDER] with your details, or let the AI ask you.
- 3. Add your materialAttach your own files, data or brief so the AI works from your facts, not guesses.
The prompt
Paste it as-is. The AI will ask for anything still in [BRACKETS].
# Track WhatsApp and phone-call leads from your ads (UAE and India) Method by Deepstory Research: deepstoryresearch.com/method/whatsapp-call-lead-tracking You are a marketing analytics lead who tracks WhatsApp and phone leads for service businesses in the UAE and India. Follow the method below step by step. Goal: A plan to measure which ads and channels bring WhatsApp chats and phone calls that turn into customers: click-to-WhatsApp labels and the Conversions API for business messaging, WhatsApp button clicks on your website, Google call assets and call conversions, what works without Google forwarding numbers, source logging in your CRM, and the consent, recording and telemarketing rules. Legal points are checked for the UAE and India only; other places are not checked. ## My inputs - Business and where it operates: [BUSINESS_AND_WHERE_IT_OPERATES] (example: car-servicing garage on the Sharjah mainland, UAE) - Ad channels and monthly spend: [AD_CHANNELS_AND_MONTHLY_SPEND] (example: Meta click-to-WhatsApp AED 3,000, Google Search with a call button AED 2,400) - WhatsApp setup: [WHATSAPP_SETUP] (example: WhatsApp Business app on one phone, no solution provider) - Phone setup: [PHONE_SETUP] (example: one main landline, a second local number used only in the Google call asset, no recording) - Where you log leads: [WHERE_YOU_LOG_LEADS] (example: a shared spreadsheet with date, phone number, status and amount paid) - Monthly chats calls and paying customers: [MONTHLY_CHATS_CALLS_AND_PAYING_CUSTOMERS] (example: 200 Meta conversations, 120 Google call clicks, 64 paying customers, average first job AED 450) Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source. ## Steps to follow 1. Confirm the country, the WhatsApp tool (Business app or Platform) and the phone setup. 2. Check which measurement options exist there: Meta labels or Conversions API, Google forwarding numbers, or call clicks only. 3. Write the definitions of a chat, a lead, a qualified lead and a paying customer, and one source list for the CRM. 4. Plan the website button event, the pre-filled source code and the call conversion settings. 5. Check WhatsApp terms and policy, consent, recording and telemarketing rules for the place. 6. Build the weekly table of cost per lead and cost per paying customer by channel. 7. Plan how outcomes go back to each ad platform. ## Deliver the output in this structure - What each channel can and cannot measure here - Lead and customer definitions - CRM source fields - Meta plan (labels or Conversions API) - Website button and call tracking plan - Terms, consent and recording checklist - Channel results table - Questions for a lawyer ## Quality rules - Never treat a button click, a call click or a conversation started as a customer. - State the country next to every Google forwarding number or Meta feature claim. - Never ask for or paste real names, phone numbers or chat text; use counts and column names. - Label the result a first-pass check, not legal or tax advice, and say other places are not checked. - Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION. - If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED]. - End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.
What you need to give the AI
| Input | Placeholder | Example |
|---|---|---|
| Business and where it operates | [BUSINESS_AND_WHERE_IT_OPERATES] | car-servicing garage on the Sharjah mainland, UAE |
| Ad channels and monthly spend | [AD_CHANNELS_AND_MONTHLY_SPEND] | Meta click-to-WhatsApp AED 3,000, Google Search with a call button AED 2,400 |
| WhatsApp setup | [WHATSAPP_SETUP] | WhatsApp Business app on one phone, no solution provider |
| Phone setup | [PHONE_SETUP] | one main landline, a second local number used only in the Google call asset, no recording |
| Where you log leads | [WHERE_YOU_LOG_LEADS] | a shared spreadsheet with date, phone number, status and amount paid |
| Monthly chats calls and paying customers | [MONTHLY_CHATS_CALLS_AND_PAYING_CUSTOMERS] | 200 Meta conversations, 120 Google call clicks, 64 paying customers, average first job AED 450 |
Use it when
- Most of your enquiries come by WhatsApp or phone, and you cannot say which ads brought the people who paid.
- Meta shows "conversations started" and Google shows call clicks, but neither tells you who became a customer.
- You want to know what the WhatsApp Business app can measure, and whether you need the WhatsApp Business Platform (API).
- You advertise in the UAE, where Google forwarding numbers are not listed, or in India, where they have limits.
Best with: A chat AI for the plan; your CRM or a spreadsheet for the log. Attach counts by channel with names, phone numbers and chat text removed.
What you get
- What each channel can and cannot measure here
- Lead and customer definitions
- CRM source fields
- Meta plan (labels or Conversions API)
- Website button and call tracking plan
- Terms, consent and recording checklist
- Channel results table
- Questions for a lawyer
The AI will ask you first
Answer these before the AI advises you; each one changes what it recommends.
In which country are you and your customers, and in the UAE, are you on the mainland or in a free zone such as DIFC or ADGM?
Google forwarding numbers are listed for India but not the UAE. The UAE data law excludes free zones that have their own data law, and India’s main data duties start later.
If unknown: Assume the UAE mainland or India as stated, list every other place as not checked, and ask a lawyer about free zones.
Do you use the WhatsApp Business app on a phone, or the WhatsApp Business Platform (API) through a provider?
The app measures through labels within 7 days of the ad click. The Platform can store a click ID for each ad chat and send events through the Conversions API.
If unknown: Assume the app, and plan labels first.
Which ads and pages send people to WhatsApp or a phone number, and how much do you spend on each a month?
Each route has its own tracking: click-to-WhatsApp ads, a website button, a Google call asset, or a number shown on your site. For Instagram or Facebook ads, check whether the ad uses Meta’s WhatsApp destination (a click-to-WhatsApp ad) or just a wa.me link. Only the first is counted in conversations started and in label attribution; a wa.me link in an ad is tracked like the website button, with a source code.
If unknown: List channels and label spend as ASSUMPTION until you read it from the ad accounts.
What counts as a lead, a qualified lead and a paying customer for you, and where is that written down with its date?
Without one definition, conversations and call clicks get counted as customers.
If unknown: Lead = a real person asking about your service. Qualified = they gave a date, a place or a budget. Customer = they paid. Log the source and date for each.
What does your first job or sale usually bring in, and how long after the first chat or call do people usually pay?
Meta labels count only within 7 days of the click. Longer journeys need the CRM to tell the real story.
If unknown: Use the average of your last 10 to 20 paying customers, labelled ASSUMPTION. Assume some sales land after 7 days. Do not divide annual revenue by monthly bookings, since that includes returning customers; use amounts from first visits or first invoices only.
Do you record calls, make follow-up marketing calls, or send promotional messages? From which numbers?
The UAE requires recording and a notice on marketing calls, set hours and registered local numbers. India restricts promotional calling from normal 10-digit numbers, and TRAI’s 2026 amendment allows calls and SMS based on an enquiry only for 7 days and only if the enquiry was made in writing or digitally and is kept.
If unknown: Assume no recording and no outbound marketing. Do not turn on either until the checks here are done and a lawyer has confirmed them.
What do you sell, and do chats or calls ever include health details, card or ID numbers?
WhatsApp bars some goods and sensitive identifiers, and Meta says not to share sensitive data in events.
If unknown: Ask. If yes to any of these, you may still build your own log and the website button click event, keeping the log to the columns in the output template, with no health details, card or ID numbers. Apart from that click event, do not turn on activity sharing or automatic events, and do not upload any log or other event to a platform, until a lawyer has confirmed it for your sector.
Who is the admin of your Meta Business Suite, Google Ads account and website tags, and which CRM or provider can see your chats?
Labels, sharing settings, call reporting and tags change data sharing and spend, so the admin must decide. WhatsApp also limits who may receive chat data.
If unknown: Assume the owner is the admin and no third party has access. Confirm before any setup.
The procedure, step by step
Read this before you run it, so you can check the AI actually followed the method.
Map the routes
List every ad, page and number that leads to WhatsApp or a call, with spend, country and WhatsApp tool. Remove nothing yet.
Check what each country allows
UAE: no Google forwarding numbers listed, so use call clicks plus a separate ad number. India: forwarding numbers with limits. Meta: labels on the app, Conversions API on the Platform. Check automatic events in your own Business Suite.
Write definitions
Chat, lead, qualified lead and paying customer, each with who marks it and where the date is saved.
Build the source log
CRM or spreadsheet columns from the rule above, with a fixed list of channels. Train staff to fill it in during the chat or call.
Set up WhatsApp measurement
App: the owner turns on activity sharing, staff use predefined labels within 7 days of the click. Platform: the partner stores ctwa_clid, the ad ID and the WhatsApp user ID (user_id), and sends LeadSubmitted, QualifiedLead and Purchase, deduplicated.
Track the website button
wa.me links with a source code in pre-filled text; Tag Manager Just Links trigger; GA4 whatsapp_click event as a secondary measure. Consent setup follows conversion-tracking-ga4-consent-capi.
Set up calls
Add call assets. Where forwarding numbers work, turn on call reporting, set a minimum call length, and add the website snippet if needed. In the UAE, use a separate local number and the call-click measure.
Run the terms and law check
WhatsApp opt-in, data sharing, AI and prohibited goods; UAE or India consent, recording and marketing-call rules. Write the questions for the lawyer and keep recording off until answered.
Review every week
Chats and calls by channel, compare with Meta and Google numbers, then cost per lead and cost per paying customer. Monthly: decide budget changes, and send outcomes back with lead-quality-offline-conversions.
Platform settings(show)
| Platform | Path | Setting | Note |
|---|---|---|---|
| WhatsApp Business app | Tools > Your customers’ activity | Allow Meta to receive information about events | Shares order details such as status and dates; not message or call content, names, emails or phone numbers. |
| WhatsApp Business app | Chat > Labels (shown as lists in some versions) | Predefined labels: Lead, New customer, Follow up, New order, Pending payment, Paid, Order complete | Label within 7 days of the ad click; custom labels may not be attributed. |
| Meta Ads Manager | Ad set > Conversion > Performance goal | Maximize number of leads through messaging; Maximize number of purchases through messaging | Needs 10 or more events shared in 30 days. Leads goal is being gradually introduced. |
| Meta Ads Manager | Columns: Performance > Customize columns > Conversions > Leads | Leads, Meta leads, Cost per lead | |
| Meta Business Suite | Settings > Accounts > WhatsApp accounts > [account] > Summary > Privacy and data sharing | Automatically identify order, lead & other events from conversations in this account | Applies to all partners with access to that account. Availability varies by country. |
| WhatsApp Business app | Tools > Lists > Auto-created lists | Turn on or Turn off (automatic events in the app) | Disconnects linked devices and may limit broadcast lists, disappearing messages, greeting and away messages, and message editing and deletion. |
| Google Ads | Admin > Account settings > Call reporting | On (uses a Google forwarding number); Off (shows your own number and third-party tracking) | Forwarding numbers are listed for India but not the UAE, as of November 2026. |
| Google Ads | Campaigns > Assets > + > Call | Add a call asset at account, campaign or ad group level | The most specific level is used. Creating one means agreeing to the Call Ads Supplemental Terms. |
| Google Ads | Goals > Summary > + Create conversion action > Conversions from phone calls | Calls from ads, Calls from website visits, or Calls via uploads | Calls via uploads is not available in the Phone call lead category. |
| Google Ads | Goals > Summary > Phone call leads > AI-qualified call leads > Edit > Lead qualification | Minimum call length in seconds | |
| Google Ads | Admin > Account settings > Call ads > Call recording | On or Off | On by default, but recording only works when both numbers are in the US or Canada. |
| Google Ads | Campaigns > Insights and reports > Report editor > Ads and assets > Call details | Call details report: start time, duration, status, call source and type | Caller number is available for most calls over 15 seconds, except in India and Japan. |
| Google Tag Manager | Triggers > New > Trigger Configuration > Just Links > Some Clicks | Click URL contains wa.me | Fires on the click, not on a chat. Pair it with a GA4 event tag. |
| Google Analytics 4 | Admin > Data display > Events | Mark an event as a key event with the star icon | Up to 30 key events on standard properties. |
Worked example
The figures below are illustrative. Use your own numbers and facts.
Scenario: A car-servicing garage on the Sharjah mainland runs Meta click-to-WhatsApp ads and Google Search ads with a call button, and has a WhatsApp button on its website. It uses the WhatsApp Business app and a shared spreadsheet, and does not record calls.
Input: One month. Meta: AED 3,000 spend, 200 conversations started, 90 chats labelled Lead, 36 paying customers in the log, of which 24 were labelled Paid within 7 days of the click. Google: AED 2,400 spend, 120 call-button clicks to a second local number used only in the call asset, 70 answered calls logged, 28 paying customers. Website button: 60 GA4 whatsapp_click events, 40 chats with the pre-filled code, 10 paying customers. Average first job AED 450.
Output excerpt: Covered: UAE. Other places not checked. Tools: Google forwarding numbers are not listed for the UAE, so call clicks plus a separate ad number replace call length conversions. Meta: 3,000 / 200 = AED 15 per conversation; 3,000 / 90 = AED 33.33 per lead; 3,000 / 36 = AED 83.33 per paying customer; revenue 36 x 450 = AED 16,200, or 16,200 / 3,000 = AED 5.40 per AED 1 spent. Google: 2,400 / 120 = AED 20 per call click; 2,400 / 70 = AED 34.29 per answered call; 2,400 / 28 = AED 85.71 per paying customer; revenue 28 x 450 = AED 12,600, or AED 5.25 per AED 1 spent. Paid channels together: 5,400 / 64 = AED 84.38 per paying customer. Website button: 40 / 60 = 66.7% of clicks became chats; 10 paying customers, AED 4,500, left out of the paid totals because the traffic is mixed. All channels: 74 paying customers, AED 33,300. Reading: AED 83.33 and AED 85.71 are a tie, so keep both budgets. 50 of 120 call clicks (41.7%) have no logged call, so check missed calls before changing bids. Meta will show about 24 purchases against 36 in the log, a gap of 12 from labels after 7 days, so judge on the log. 24 purchase events in 30 days passes the 10-event bar; look for the purchase goal in the ad set dropdown and test it. Replies sent from the app carry no Platform fee; the app’s marketing messages are charged per delivered message, so add them to cost if used. Law: log consent and source (PDPL Articles 4 to 6); keep recording off until a lawyer confirms the wording; treat reminder or offer calls as marketing calls: 9 am to 6 pm, local numbers registered to the company, DNCR check, and a recording notice, and ask a lawyer about the approval and whether calling back an enquiry counts. This is a first-pass check, not legal or tax advice. Confirm with a qualified accountant or lawyer for your country.
Check your result
Before you trust the AI's output, confirm each of these.
- ☐ Every channel row shows spend, chats or calls, leads, paying customers and cost per paying customer, with the source of each number.
- ☐ A test chat from each ad or code, and a test call to each number, appears correctly in the log.
- ☐ Meta labels or events appear in Ads Manager or Events Manager, and the gap against the log is explained.
- ☐ The Google call setup matches the country: forwarding numbers only where listed, and the minimum call length is written down with its reason.
- ☐ Opt-in date and source are stored for each lead, and opt-outs are honoured.
- ☐ Recording, outbound marketing and any upload outside Meta are off, or have a written answer from a lawyer.
- ☐ The output says it is a first-pass check, not legal or tax advice, and names the places covered and not checked.
What you'll get(show template)
## WhatsApp and call lead tracking: [BUSINESS], [DATE] Covered for legal rules: [UAE / India]. Not checked: [every other place involved]. ### What each route can measure here Route | Tool | What is measured | What is not | Setting or owner ### Definitions Stage | Meaning | Who marks it | Date field ### Source log columns First contact date | Channel | Later contact and date | Campaign or code | Status | Amount | Payment date | Opt-in date | WhatsApp user ID (Platform only) ### Meta plan Tool: [app labels / Conversions API through partner] | Sharing on: [by, date] | Events: [Lead, Purchase] | Events in the last 30 days vs 10: [ ] | Goal: [ ] ### Website button and calls wa.me links and codes: [ ] | GA4 event: [whatsapp_click, secondary] | Forwarding numbers available: [yes, limits / no] | Call conversion: [type] | Minimum call length: [seconds and why] | Tracking number: [ ] ### Channel results (from the log) Channel | Spend | Chats or calls | Leads | Paying customers | Revenue | Cost per lead | Cost per paying customer | Platform figure | Gap ### Terms and law checklist [ ] WhatsApp opt-in logged | [ ] No third-party sharing beyond the Solution Provider | [ ] No AI training on WhatsApp data | [ ] No sensitive identifiers | [ ] Restricted goods checked | [ ] Privacy notice updated | [ ] Recording: [off / approved wording] | [ ] Marketing calls: [none / rules met] | [ ] India dates checked ### Questions for a lawyer 1. [Question] ### Outcomes back to platforms Platform | Route | Stage | Owner | Start date (see lead-quality-offline-conversions) This is a first-pass check, not legal or tax advice. Confirm with a qualified accountant or lawyer for your country.
Quality checks built into the prompt
- • Never treat a button click, a call click or a conversation started as a customer.
- • State the country next to every Google forwarding number or Meta feature claim.
- • Never ask for or paste real names, phone numbers or chat text; use counts and column names.
- • Label the result a first-pass check, not legal or tax advice, and say other places are not checked.
- • Every number labelled FACT, ESTIMATE or ASSUMPTION; claims outside attached evidence tagged [UNVERIFIED].
Decision rules
If/then rules the AI should apply. Heuristic rules are a practitioner's rule of thumb, not a platform rule.
| If | Then | Type |
|---|---|---|
| You run click-to-WhatsApp ads and answer in the WhatsApp Business app. | The app shows reach, ad clicks, cost per link click and conversations started; results can take up to 48 hours. To see leads and sales, turn on Tools > Your customers’ activity > Allow Meta to receive information about events, then use the predefined labels: Lead, New customer or Follow up for leads; New order, Pending payment, Paid or Order complete for purchases. Custom labels may not be attributed. A chat must come from the ad and be labelled within 7 days of the click. Creating or updating an order in the app also counts as a purchase, but this is not available in India, Malaysia or Pakistan (as of November 2026). Meta receives order details such as status and dates, but not message or call content, names, emails or phone numbers. Rule of thumb: if people pay at an appointment more than 7 days after the chat, label the chat New customer (a lead label) when the booking is made and keep payment in your own log; Paid will rarely fall inside 7 days.Threshold: 7 days from the ad click | Platform rule |
| You read "Messaging conversations started" in Ads Manager. | It counts accounts that messaged you for the first time or after at least 7 days of inactivity, attributed to your ads. For WhatsApp Business it includes only conversations started from clicks on your ad, and it leaves out ads delivered to or from Europe or Japan. Rule of thumb: report it as chats, never as leads or customers, and compare it with your own log each week.Threshold: 7 days of inactivity | Platform rule |
| You want Meta to optimise click-to-WhatsApp ads for leads or purchases rather than chats. | Maximize number of leads through messaging needs 10 or more lead or purchase events shared within 30 days; Meta says it is being gradually introduced. Maximize number of purchases through messaging needs 10 or more purchase events in a prior 30-day period. Events can come from the app or the Conversions API. Each Facebook Page must qualify separately, and sharing from every WhatsApp number on a Page helps it qualify sooner. Look for the goal under the ad set’s Conversion section; Meta’s page names different objectives in different places, so check your own dropdown. Run for at least 7 days and judge purchase campaigns on Meta purchases and cost per on-Meta purchase. Rule of thumb: stay on conversations until you reach 10 events.Threshold: 10 events in 30 days | Platform rule |
| You use, or are moving to, the WhatsApp Business Platform and want ad-level results. | The Conversions API for business messaging exists as of November 2026 and works through a partner or a direct integration on Cloud API. Store the click ID (ctwa_clid) from the referral object of the first ad message with the conversation, along with the ad ID (source_id). Send events with action_source "business_messaging" and messaging_channel "whatsapp". Supported events include LeadSubmitted, QualifiedLead and Purchase. These events are only for things that happen in the chat; a sale on your website or app goes through that product’s Conversions API. Meta does not deduplicate these events, so do it yourself. Only one dataset can link to a Page. Since April 2026 Meta puts a business-scoped user ID (BSUID) in the user_id field of all messages webhooks, and WhatsApp says it will start rolling out usernames gradually in 2026. If a person turns on a username, their phone number is left out of webhooks unless that business phone number messaged or called them, or received a message or call from them, in the last 30 days, or they are in your contact book. The ID is unique to your business portfolio and changes if the person changes their phone number; Meta then sends a system message webhook with the new ID and, when available, the old one. Rule of thumb: ask your provider to store user_id with each chat as its main key and update it from that webhook, keep the phone number only when you have it, and do not plan CRM matching or the hashed-phone route below on phone numbers alone. | Platform rule |
| You have no click ID for a chat, for example it began before you stored it, or it came from a WhatsApp Status ad. | Status placements leave out ctwa_clid entirely. You can instead send page_id plus at least one SHA-256 hashed customer value such as phone or email; external_id alone does not count. This path attributes only to an ad interaction in the past 7 days, match is not guaranteed, and it is available in a subset of countries that Meta does not list on this page, so test before relying on it in the UAE or India. First check the rules on sharing WhatsApp data below.Threshold: 7 days | Platform rule |
| You are thinking of turning on Meta’s automatic events. | Meta analyses new chat threads from click-to-WhatsApp ads and labels leads and orders. It is optional, available only in certain countries, and not available in the EU, UK, Japan or South Korea. On WhatsApp it helps labels and reporting; Meta says using it for ad optimisation is only for Messenger and Instagram Direct "at this time". In the app it may limit broadcast lists, disappearing messages, greeting and away messages, and message editing and deletion. It also disconnects linked devices and adds a notice to chats that the business uses a secure service from Meta. Purchase webhooks carry no value or currency, so you must add the amount yourself. Rule of thumb: spot-check 20 labelled chats against your log before you trust the counts, and have the privacy notice reviewed first. | Platform rule |
| You consider moving from the app to the Platform for better tracking. | An existing app number can connect to Cloud API through a partner (Meta also calls this Coexistence), using app version 2.24.17 or higher. Messages sent from the app stay free, while Cloud API messages follow Platform pricing, and the 24-hour window applies only to Cloud API messages. The business can choose to share chat history with the partner. After the switch, disappearing messages are turned off in one-to-one chats and broadcast lists are disabled (existing ones become read-only), so check this before you switch. Rule of thumb: stay on the app and labels until you handle more chats than staff can label, or you need ad-level source in the CRM automatically. | Platform rule |
| You count WhatsApp costs, or still report by billable "conversations". | Platform pricing has been per delivered message, not per conversation, since 1 July 2025, and rates may change on the first day of each quarter. Since 1 October 2026 service messages and utility messages inside the customer service window are charged again, with 1,000 free service messages per business phone number each month. If you reply within the window to someone who came from a click-to-WhatsApp ad on the Android or iOS app, a free entry point window can stay open for up to 7 days, except for Meta Business Agent messages. UAE marketing rates rose on 1 October 2026 and India’s on 1 January 2026; check the rate card for figures. On the WhatsApp Business app, marketing messages (called business broadcasts in some countries) are charged for each message delivered to a contact within five days of being sent, priced by the recipient’s country code. If your Sold-To country is India, move Messaging accounts to INR by 31 December 2026, or Meta stops delivering their messages from 1 January 2027. Since API version 24.0 the status webhook has no conversation object outside free entry point windows, so rebuild reports that rely on it. | Platform rule |
| You follow up with a chat lead, on the app or the Platform. | WhatsApp’s policy (last updated 23 September 2026) lets you contact people only if they gave you their number or username and you have opt-in confirming they want later messages or calls from you. You alone must make sure the opt-in meets local law. Respect every opt-out, on or off WhatsApp. On the Platform you may reply freely within the 24-hour window, and outside it you may send only approved templates. WhatsApp’s best practice is a separate opt-in for each message category and for calls. Rule of thumb: an ad chat lets you answer that question; ask before you add the person to reminders or offers, and log the opt-in date in the CRM.Threshold: 24-hour customer service window | Platform rule |
| You log WhatsApp data in a CRM, report on it, or send it to other tools. | The Meta Terms for WhatsApp Business Platform (last modified 23 September 2026, section 4.1) bar using Platform data, other than the content of your message threads, to track, build or augment profiles on individual users. They also bar sharing Platform data, including anonymous, aggregate or derived forms, with third parties, except a Solution Provider. The policy, which also covers the app, says not to use data obtained from WhatsApp about a person, other than thread content, beyond what is reasonably necessary to support messaging them. Rule of thumb: use a CRM connected through your Solution Provider, send WhatsApp outcomes only to Meta, and before uploading numbers or outcomes from WhatsApp chats to Google or other tools, ask a lawyer or your provider. On the WhatsApp Business app there is usually no Solution Provider, so as a rule of thumb log only what staff write down themselves (first contact date, source answer, status, opt-in date, and amount from your own invoices), never chat exports or contact lists from the phone, and ask a lawyer before any automatic sync from the app to a CRM. Report sales to other platforms only from your own invoices, and only for leads that came through those platforms. | Platform rule |
| You want AI to read or score chats or call notes. | Section 4.7 of the terms lets you retain an AI provider as your Solution Provider, but WhatsApp Platform data, including anonymous, aggregate or derived forms, may not be used to create, develop, train or improve AI models, except to fine-tune a model for your exclusive use. Providers whose main product is AI, such as general-purpose assistants, may not offer it through the Platform except in the countries Meta lists. Rule of thumb: do not paste chat exports into a general AI tool; use counts and fields with contact details removed, and check the tool with ai-data-safety-checklist. | Platform rule |
| Your product, or what customers say in chats, may be restricted or sensitive. | The policy bars full payment card, financial account and personal ID numbers in chats. It prohibits listed goods and services, including alcohol, drugs, medical and healthcare products, gambling, dating and multi-level marketing, whatever licences you hold, with limited country exceptions on the Platform and none on the app. As of November 2026, the policy lists India as an allowed country for over-the-counter drugs on the Platform only, lists the UAE for none of the exceptions, and bars such messages to people under 18. Using a catalog also brings in Meta’s Commerce Policy. The terms bar giving Meta legally protected data and warn that the Platform makes no promise to meet health, financial or legal confidentiality duties. Meta also says not to share sensitive data when you set up messaging events. The policy also says not to use WhatsApp for telemedicine, or to send or request health related information, where applicable regulations prohibit sending it to systems that do not meet heightened requirements for health information. Rule of thumb: clinics should ask a lawyer whether patients’ health questions may be handled on WhatsApp at all before building tracking on those chats. | Platform rule |
| You put a WhatsApp button or link on your website. | Use a click-to-chat link in the form https://wa.me/<number>, where the number is the full phone number in international format; WhatsApp says to omit any zeroes, brackets or dashes, and its example drops the plus sign and the leading 00. Add ?text= with URL-encoded text for a pre-filled message. Track it with a Tag Manager click trigger of type Just Links, firing on Some Clicks where Click URL contains wa.me, and send a GA4 event. You can mark it as a key event in Admin > Data display > Events. Rule of thumb: also drop the local 0 before a mobile or area code, so 050 123 4567 in the UAE becomes https://wa.me/971501234567. Name the event whatsapp_click and do not send generate_lead, since GA4 sees only the click and not whether a chat began. Keep it secondary in Google Ads until your log shows how many clicks become chats. Put a short source code in the pre-filled text, one per page or campaign, and log it; customers can delete it, so expect some unknowns. | Platform rule |
| You want Google call tracking and advertise in the UAE. | As of November 2026 the UAE is not on Google’s list of countries with Google forwarding numbers. Calls from ads, calls to a number on your website, and imported calls all require those numbers, so plan without them. Options: "Clicks on call ads and assets", which counts a click based on Google’s estimate of whether a meaningful call happened; clicks on a number on your mobile website, which tracks clicks and not calls; and the "call clicks" metric in Smart campaigns. Check which appear in your account. Rule of thumb: put a second local number, used only in the call asset, on your ads so staff can log the source; Google verifies that numbers belong to your business. Ask any tracking vendor for numbers from a UAE-licensed telecom company. | Platform rule |
| You want Google call tracking and advertise in India. | Google forwarding numbers are listed for India, with limits (as of November 2026). Call details do not give you the caller’s number in India. On some calls, caller ID shows a Google number and not the customer’s. Importing call conversions works for only a portion of Indian calls. So rely on call length conversions, and do not plan a call-back list or a phone-number match from Google’s report. Call recording and AI-qualified call leads work only when both numbers are in the US or Canada, so they do not apply in India. | Platform rule |
| You set the call length that counts as a conversion, where forwarding numbers work. | Calls that last at least your minimum length count as conversions; shorter calls still show as phone calls. Google shows no default on the pages checked, and gives examples of 30 seconds and 2 minutes. Its advice: look through your call history, ask staff how long a good call lasts, and time your own call through any menu. Phone calls are reported on the day they happen and call conversions on the day of the ad click, so the dates can differ. Manually dialled calls from tablets and computers show only in All conversions and cannot be used for automated bidding. Website call conversions count calls for up to 60 days after the ad click. Rule of thumb: start at 60 seconds, then adjust from your own booked and unbooked calls.Threshold: Your own minimum length, in seconds | Platform rule |
| You show a tracking number on your website. | With Google forwarding numbers, add the Google tag and the phone snippet that swaps your number for people who clicked an ad. Only one number can be tracked per page with the default tag. Tag Manager’s website call tag does not accept international number format, so use the national format without a plus sign. These numbers belong to Google and may change, so do not print or reuse them elsewhere; early-media phone menus can show as missed calls. With a third-party tracking number (dynamic number insertion), Google cannot verify the number from your page source, so link Search Console (recommended) or place the Google tag directly in your HTML to avoid an "Unverified Phone Number" disapproval. Call details forwarding gives a click ID for calls over 15 seconds, but it needs account-level call reporting and one of Google’s listed call analytics providers, and Google routes these calls through a Google forwarding number, so do not plan it where forwarding numbers are not listed, including the UAE (as of November 2026). | Platform rule |
| You collect or log personal data of people in the UAE (UAE PDPL, Federal Decree-Law 45 of 2021). | Article 4 prohibits processing without consent, with exceptions including steps to perform or conclude a contract at the person’s request. Under Article 6 you must be able to prove consent, it must be clear and simple, and the person must be able to withdraw it easily. Article 5 requires a specific purpose, only the data needed and no keeping it after the purpose ends. Article 17 lets people stop direct marketing, including profiling for it. Article 2 excludes free-zone companies with their own data law, and health data that has its own law. Executive Regulations were due under Article 28, and Article 29 allows six months after they are issued to comply. Rule of thumb: legal commentary reports that those regulations were still not issued as of mid-2026, but this was not confirmed on an official page. On 14 June 2026 the UAE announced an Artificial Intelligence and Data Authority that takes over the functions of the UAE Data Office; the announcement does not mention this law, so ask a lawyer which body now oversees it and for the current position. Log consent and source for each lead, and do not rely on the exceptions without advice. | Legal rule |
| You are a clinic or other healthcare provider in the UAE, or your log holds treatments or health details (Federal Law No. 2 of 2019 on the use of ICT in health fields). | The PDPL excludes health data that has its own law. This law applies to all use of information and communication technology in health fields in the UAE, including free zones (Article 2). It requires all health data and information to be kept confidential and circulated only in permitted cases (Article 4(1)), and allows health data related to health services provided in the UAE to be stored, processed, generated or transferred outside the UAE only in cases set by a decision of the health authority in coordination with the Ministry (Article 13). Rule of thumb: keep the source log free of treatments and health details (only the columns in the output template), keep anything with treatments in your clinic system, and do not turn on WhatsApp activity sharing or upload bookings to Google or Meta until a UAE health-data lawyer confirms it. | Legal rule |
| A company licensed in the UAE, including in a free zone, makes marketing calls (Cabinet Resolution 56 of 2024). | The Ministry’s summary lists these duties: prior approval from the competent authority, trained staff, local numbers registered to the company, calling only consumers who chose to receive marketing, not calling numbers on the Do Not Call Register (DNCR), calling only from 9 am to 6 pm, stating who you are and why you are calling, asking whether the person wants to continue, keeping a record of calls, and recording marketing calls with a notice at the start. If someone refuses, do not contact them again; unanswered or ended calls are limited to once a day and twice a week. Individuals may not telemarket from their own numbers. The Ministry describes 18 violations with fines from AED 10,000 to AED 150,000, and AED 5,000 for an individual calling from a personal number. Rule of thumb: the full resolution could not be read on the official portal, so ask a lawyer whether calling back someone who enquired counts as a marketing call, and whether the resolution also covers WhatsApp marketing messages (law-firm commentary says its scope includes marketing messages through social media applications), and treat reminder and offer calls as marketing.Threshold: 9 am to 6 pm | Legal rule |
| You want to record calls with people in the UAE, outside the marketing-call rule above. | Rule of thumb, not checked on an official page: the official text of the UAE cybercrime law (Federal Decree-Law 34 of 2021) and the Crimes and Penalties Law (Federal Decree-Law 31 of 2021) could not be fetched. Legal commentary says recording a call without consent can be a criminal offence, even if you are on the call, and sources differ on details and penalties. Keep recording off until a UAE lawyer confirms your wording. If approved, say so before the conversation starts, and offer a way to continue without recording. | Heuristic |
| You process digital personal data of people in India (DPDP Act 2023). | G.S.R. 843(E), dated 13 November 2025, sets the dates. Sections 3 to 5, 6(1) to (8) and (10), 7 to 10 and 11 to 17 come into force 18 months after publication, from 13 May 2027. Section 6(9), which requires every consent manager to register with the Data Protection Board, comes into force one year after, from 13 November 2026; that duty falls only on consent managers themselves. Until 13 May 2027 these duties have not started, but build for them now. You may process data with consent or for certain legitimate uses (section 4). Consent needs a notice of the data and purpose (section 5) and must be free, specific, informed and limited to the data needed (section 6). Section 7(a) allows use for a purpose the person volunteered their data for, such as asking for help, and that use ends when they say they no longer need help. Under section 8 you stay responsible for processors, need a valid contract with them, must protect the data, report breaches, and erase data when the purpose ends. Rule of thumb: an enquiry does not cover sending data to ad platforms or later marketing; ask for consent for those. MeitY consulted in 2026 on shorter dates, so confirm them on its website.Threshold: 13 May 2027 | Legal rule |
| You make promotional or service calls, or send commercial SMS, in India (TRAI TCCCPR 2018, amended February 2025 and September 2026). | TRAI’s February 2025 amendment restricts normal 10-digit numbers for telemarketing: the 140 series is for promotional calls and the 1600 series for transactional and service calls. Consent for an ongoing transaction lasts only 7 days. After an opt-out you may seek consent again only after 90 days. People can complain within 7 days of a call or message. Action against a sender starts at 5 complaints in 10 days; a first violation bars outgoing services for 15 days, and later ones mean disconnection for a year and blacklisting. TRAI’s Third Amendment Regulations, 2026, dated 18 September 2026 (Press Release No. 119/2026), add three points. Commercial communication based on a customer’s inquiry is allowed only for 7 days from the inquiry, and only if the inquiry was made in writing or through digital means and you keep it in a verifiable form. Action can also start at 3 or more complaints from different people in 10 days if any of your numbers was also flagged by the telecom companies’ AI system as a suspected spam sender in those 10 days. Calls placed by an application, software or automated platform without a person dialling, including autodialled, robo and pre-recorded or artificial-voice calls, must be declared to your telecom provider with the numbers used, or they are treated as spam. These changes start in stages after publication in the Official Gazette: the enquiry rule 30 days after, the advance declaration of automated calls 60 days after, and the 3-complaint rule 90 days after. The text TRAI posted is marked to be published in the Gazette, so confirm the Gazette date with your telecom provider; if it was published on 18 September 2026, the stages start around 18 October, 17 November and 17 December 2026. Rule of thumb: until your provider confirms which change is in force, treat the 7-day enquiry limit as already applying, and collect consent on your forms for calls after day 7. Rule of thumb: answering someone who phoned you is not the same as a promotional campaign, but sales staff calling lead lists from a mobile is the risk here, so register through your telecom provider. Keep the chat, form or email that holds each enquiry, with its date, and stop enquiry-based calls and SMS after 7 days unless the person gives consent. TRAI’s notes cover calls and SMS; they do not say how this applies to WhatsApp, so follow WhatsApp’s opt-in rules there and ask a lawyer.Threshold: 7 days; 90 days; 5 complaints in 10 days (3 if AI-flagged) | Legal rule |
| You want to record calls with people in India. | Rule of thumb, not checked on an official page: no recording rule was read for this method. A recording is personal data, so announce it at the start, say why, keep it only as long as needed, and restrict access. Ask an Indian lawyer before you start, and treat it under the DPDP duties above. | Heuristic |
| You set up the source log in your CRM or spreadsheet. | One row per person, with: first contact date, channel (Meta WhatsApp ad, website button, Google call, organic, referral, unknown), campaign or code, status (lead, qualified, paid, lost), amount, payment date and opt-in date. Channel is where the person first came from. If they later move to WhatsApp or a call, record that in a separate Later contact field with its date; do not overwrite the first channel. On the Platform, also keep the WhatsApp user ID (user_id) your provider stores, because some chats will arrive with no phone number. Staff ask "How did you find us?" only when the source is blank. Keep "unknown" as its own row; do not share it out across channels. Rule of thumb: if unknown goes over 20% of leads, fix logging before you change any budget.Threshold: 20% unknown (rule of thumb) | Heuristic |
| You compare channels. | Compare cost per paying customer, using your own log, over at least 30 days and at least 20 paying customers per channel. Cost per chat or call click misleads. Treat small differences as a tie; only move budget when the gap is large and lasts for two months. Add the Platform’s message fees, any paid marketing messages sent from the app, and any provider fees to the cost. If you have fewer than 20 paying customers a month in total, compare channels on running totals over 3 months or more, and report each channel’s count next to its cost so a difference of one or two customers is not read as a trend.Threshold: 30 days and 20 customers per channel (rule of thumb) | Heuristic |
| You want to send outcomes back to the ad platforms. | Meta: use labels or the Conversions API as above. Google: only for leads that came from Google, using your own sales records, through the upload route in lead-quality-offline-conversions. Do not send lost leads as conversions. Note that Calls via uploads is not available in the Phone call lead category. | Heuristic |
| Customers or business are outside the UAE and India. | Say that the legal rules were not checked for that place. Note WhatsApp and Meta rules still apply, and some features are unavailable for Europe, Japan and South Korea. Ask a local lawyer about consent, recording and calling rules before you start. | Heuristic |
Failure modes
Common mistakes with this method, how to spot them, and how to fix them.
| Mistake | Symptom | Fix |
|---|---|---|
| Reporting "conversations started" or call clicks as leads. | Cost per lead looks great while sales stay flat. | Use your log for leads and paying customers; keep the platform figures in their own row. |
| Using custom labels in the WhatsApp Business app, or labelling after 7 days. | Meta shows far fewer leads or purchases than your log, and goals stay out of reach. | Use the predefined labels, and label during the chat or at the end of each day. |
| Assuming Google forwarding numbers work in the UAE. | You plan call length conversions or an import that cannot run. | Use call-click measures and a separate local number for ads, and read the country list before planning. |
| Planning an Indian call-back or import list from Google’s call report. | Caller numbers are missing, or imports match only part of your calls. | Use call length conversions, and log the source when the call is answered. |
| Copying a Google forwarding number onto flyers or other ads. | The number changes, and calls fail or are lost. | Use it only through call reporting and the website snippet; print your own number. |
| Sending WhatsApp chat exports or numbers to Google, a spreadsheet tool or a general AI app. | Possible breach of the WhatsApp terms and privacy law; account limits or removal. | Keep data with your Solution Provider, send WhatsApp outcomes only to Meta, share counts elsewhere, and ask a lawyer before any other upload. |
| Turning on call recording or automatic events without checking first. | Legal risk, linked devices disconnected, and app features lost. | Do the consent and recording review first, tell customers, and test on one number. |
| Sales staff making follow-up calls from personal mobiles. | UAE: fines and suspended numbers. India: spam complaints, barred outgoing services and blacklisting. | Use registered company numbers or the right number series, follow hours and opt-outs, and take legal advice first. |
| Counting a website button click as a lead. | GA4 shows many leads, but few chats arrive. | Keep the click as a secondary event, and compare it with chats carrying your source code. |
| Leaving source blank in the log. | Unknown grows, and budget choices rest on guesses. | Make source a required field, ask new customers, and keep unknown visible. |
Agent mode: if an AI agent runs this unattended
May do without asking
- • Build the route map, definitions and source log columns from what the user describes.
- • Calculate cost per lead and cost per paying customer from counts with names and numbers removed.
- • Draft the wa.me links with source codes, the tag plan and the questions for a lawyer.
- • Read reports or diagnostics that the user exports and attaches, and compare them with the log.
Must stop before (the user decides and does these)
- • Spending money, or changing a budget, bid, campaign goal or performance goal.
- • Publishing or changing ads, website code, tags or call assets.
- • Sending messages or templates to customers, or calling them.
- • Uploading or sharing customer, chat or call data with any platform, CRM, AI tool or vendor.
- • Accepting terms, including WhatsApp, Meta Business Tools or Google Call Ads Supplemental Terms, or connecting a provider.
- • Turning on activity sharing, automatic events, call reporting, call recording or the move to the Platform.
- • Changing billing, payment methods or currency, or account or DNS settings.
- • Deleting chats, labels, recordings, conversion actions or anything else.
Evidence for this method
This method runs on your own material: your files, brief or code. If your task needs market or economic numbers, attach a sourced context file from the evidence library alongside the prompt.
Browse evidenceRun next
Methods that chain well after this one.
Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment decisions need a qualified professional.