diff --git a/docs/4. Product Features/06. HSM Templates.md b/docs/4. Product Features/06. HSM Templates.md index 928d1ceeb..c68c69a00 100644 --- a/docs/4. Product Features/06. HSM Templates.md +++ b/docs/4. Product Features/06. HSM Templates.md @@ -4,7 +4,7 @@ 10 minutes read Level: Beginner - Last Updated: April 2026 + Last Updated: July 2026 @@ -139,6 +139,18 @@ Here's a simple explanation with examples: Screenshot 2024-07-01 at 5 13 14 PM +Tracking clicks on a URL button + +WhatsApp does not send any signal back to Glific when a contact taps a URL button - the button simply opens the link on the contact's phone. Because of this, Glific has no way to show you how many contacts clicked a Static or Dynamic URL button. + +To track clicks yourself, don't point the button straight at your destination page. Instead: + +- Use a Dynamic URL to add a unique value for each contact to the link, for example the contact's ID: `https://yourdomain.org/track/{{1}}` +- Point this link to a redirect page you control, or a link-tracking tool (such as Bitly or Rebrandly), that records every click along with that unique value before sending the contact on to your real destination page. +- Match the recorded clicks back to your contacts using the unique value, to see who opened the link. + +Please Note : If you need the flow itself to react to whether a contact engaged (for example, to send a different follow-up message), use Quick Reply buttons instead of a URL button. Unlike URL buttons, Quick Reply taps send a response back into the flow and can be captured with a `Wait for Response` node. + j. `Category` - Select the most relevant category from the dropdown. Ex. Utility or Marketing. - Utility: Used for transactional messages to keep your customers in the loop with essential order updates, shipping status, about their accounts, orders, appointment reminders, and important alerts.