{"id":916,"date":"2026-10-29T13:47:12","date_gmt":"2026-10-29T13:47:12","guid":{"rendered":"https:\/\/vectalk.com.br\/blog\/whatsapp-template-utm-tracking\/"},"modified":"2026-10-29T13:47:16","modified_gmt":"2026-10-29T13:47:16","slug":"whatsapp-template-utm-tracking","status":"publish","type":"post","link":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-template-utm-tracking\/","title":{"rendered":"Dynamic URL button with UTM in WhatsApp templates: track clicks and sales in GA4"},"content":{"rendered":"\n

Updated on October 29, 2026<\/em><\/p>\n\n\n\n

To measure clicks and sales from a WhatsApp template in GA4, use a URL button with a dynamic suffix: the approved template has a fixed address ending in {{1}}<\/code>, and on each send you pass a value that identifies the campaign (and, if you want, the individual send). That value becomes UTMs (utm_source=whatsapp<\/code>, utm_medium<\/code>, utm_campaign<\/code>), either directly in the URL or through a redirect on your own domain, and GA4 attributes the session and the purchase to the campaign. On the WhatsApp side, you match this with the status webhook and Meta’s template analytics to get the full funnel: delivered, read, clicked and sold.<\/p>\n\n\n\n

This guide covers Meta’s rules for URLs in templates, two ways to set up UTMs, the send payload and a report template.<\/p>\n\n\n\n

Meta’s rules for the URL button<\/h2>\n\n\n\n

According to the template components documentation<\/a>:<\/p>\n\n\n\n

Rule<\/th>Limit<\/th><\/tr><\/thead>
URL buttons per template<\/td>Up to 2<\/td><\/tr>
Button text<\/td>Up to 25 characters<\/td><\/tr>
URL length<\/td>Up to 2,000 characters<\/td><\/tr>
Variables in the URL<\/td>At most 1, always at the end of the address<\/td><\/tr>
Sample value<\/td>Required when the URL has a variable<\/td><\/tr>
Special characters<\/td>Must be percent-encoded (e.g., a space becomes %20<\/code>); unencoded characters can make the send fail<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The practical consequence matters: you can’t put the variable in the middle of the URL or have two variables (one for the campaign and one for the contact). All tracking has to fit in a single suffix at the end.<\/p>\n\n\n\n

Two ways to pass UTMs<\/h2>\n\n\n\n

Option 1: fixed UTMs in the URL, variable in the last parameter<\/h3>\n\n\n\n

The template is created with the campaign’s UTMs, and the variable fills only the last parameter:<\/p>\n\n\n\n

https:\/\/www.store.com\/offers?utm_source=whatsapp&utm_medium=template&utm_campaign=bf2026&utm_content={{1}}<\/code><\/p>\n\n\n\n

On send, {{1}}<\/code> gets something like sneaker_offer_a<\/code>. Pros: simple, no server needed. Cons: utm_campaign<\/code> is locked into the template, so each new campaign requires a new template (and a new approval); and the value you pass must be URL-encoded.<\/p>\n\n\n\n

Option 2: redirect on your own domain (recommended)<\/h3>\n\n\n\n

The template has a short URL on your own domain:<\/p>\n\n\n\n

https:\/\/www.store.com\/w\/{{1}}<\/code><\/p>\n\n\n\n

On send, {{1}}<\/code> gets a short code, such as k7Qm2x<\/code>. Your server stores what that code means (campaign, template, destination, send ID) and replies with a 302 redirect to the final URL with all the UTMs. Pros:<\/p>\n\n\n\n