Dev.to WebDev 🛠 Dev 👁 0 📖 1 min read

6 Ways Click-to-WhatsApp Ad Tracking Breaks (and How to Fix Each)

You’re capturing the referral object from WhatsApp Click-to-WhatsApp ads, but revenue-per-ad numbers still look wrong. These are the usual reasons. Referral not saved It only arrives with the first message from an ad c

You’re capturing the referral object from WhatsApp Click-to-WhatsApp ads, but revenue-per-ad numbers still look wrong. These are the usual reasons.

  1. Referral not saved
    It only arrives with the first message from an ad click. If your webhook handler skips it, or only processes text, the source is lost for good. Save it before anything else.

  2. Phone format mismatch
    WhatsApp sends 919876543210. WooCommerce stores +91 98765 43210 or 09876543210. Normalise both sides to digits with the country code before matching.

  3. Repeat buyer, old ad
    A customer clicked ad A in March and ad B today. Overwriting the source loses history, and never overwriting credits the wrong ad. Store every touch with a timestamp and pick by your attribution rule.

  4. Order placed from another number
    The chat came from one number, and the order used a family member’s. Add a fallback match on email, or ask for the order number in chat.

  5. No ad ID in reports
    Reports show “Click-to-WhatsApp” as the source but not which ad. Store source_id and map it to campaign and ad names.

  6. Counting chats, not sales
    The dashboard still ranks ads by conversations. Make revenue per ad the default view.

Wabbiyo’s WhatsApp Ads module, a WordPress plugin on the official Cloud API, handles referral capture, matching and revenue reports for WooCommerce: Click here to know more.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.