Conversion tracking for WhatsApp, Telegram and call leads

What it does

A WhatsApp or Telegram button sends the visitor out of your site and into an app. A phone link opens the dialer. From that moment no website tag sees what happens next: whether the person actually wrote, what they asked, whether they came to an interview. So for messenger leads the website can only measure intent, which is the click on a contact button. That is still valuable, because it is the last moment you can connect the lead to the ad that brought it, through the click ID and UTM tags in the page address.

There are three classic ways to count those clicks. In GA4, a Tag Manager click trigger on links that start with wa.me, t.me or tel: sends an event such as generate_lead, which you mark as a key event. In Google Ads, a website conversion action fires on the same trigger, so bidding learns which searches bring contacts. On Meta, the pixel sends a Contact or Lead event on the button click, so ad sets can optimize for it. All three see the click and the session. None of them sees the conversation, and all of them depend on the tags being published and not blocked by the browser or by missing consent.

The gap between “clicked WhatsApp” and “real customer” is where budgets get wasted: a campaign can produce cheap clicks from people who never write. Closing it needs a record of the click that you can update later with the outcome. If you keep the Google click ID (gclid) and Meta's click marks with each lead, you can send the real result, such as an interview or a sale, back to Google Ads as an offline conversion and to Meta through the Conversions API. Personal data is not needed for that; technical marks are enough to match a result to a click. Also remember that Meta ads which open WhatsApp or Messenger directly skip your site, so website tags never see those leads.

AdAce Ads covers both layers. The Tag Manager plan can add a GA4 lead event, a Google Ads conversion and a Meta pixel lead event on clicks of phone, messenger and email buttons, published only after your password and second factor. The lead tracking script from “Analytics” → “Leads” is one line on the site: it counts clicks on Telegram, WhatsApp, phone, email and form buttons as leads and stores only technical marks, namely channel, page address and language, UTM tags, gclid, gbraid, wbraid, fbc and fbp. Each lead goes to the client's topic in the agency Telegram group with status buttons, and “interview” or “hired” is sent back to Google Ads as an offline conversion and to Meta as a server event.

Why it helps

• Messenger and phone leads are counted instead of disappearing outside the site.
• The blind spots of each method are clear, so reports are read correctly.
• Real outcomes, not just clicks, can train Google and Meta bidding.
• The lead script stores no names, phone numbers or emails.

How to set it up

1. Run the tracking audit for the site and open the Tag Manager change plan.
2. Add the GA4 event, the Google Ads conversion and the Meta lead event, then publish with your password and second factor.
3. Copy the lead tracking script from “Analytics” → “Leads” and add it to the site.
4. Mark leads with the buttons in the client's Telegram topic: “wrote”, “interview”, “hired” or “not a fit”.
5. Let interviews and hires flow back to Google Ads and Meta as conversions.
6. Compare cost per interview and per hire by campaign.

Good to know