docs: explain how to track clicks on HSM Dynamic URL buttons

[SangeetaMishr]

Summary

Fixes #265

Adds a "Tracking clicks on a URL button" section right after the Dynamic URL example in the HSM Templates doc, explaining:

• Why Glific can't show click counts for Static/Dynamic URL buttons: WhatsApp never sends an event back to Glific when a contact taps a URL button (unlike Quick Reply buttons, whose taps come back as a message).
• The workaround: embed a unique per-contact value in the Dynamic URL and route it through a redirect/link-tracking service that logs the click before forwarding the contact to the real destination.
• A pointer to use Quick Reply buttons instead, if the flow itself needs to branch on whether the contact engaged.

Verification

Confirmed against glific/glific:

• lib/glific_web/providers/gupshup/router.ex only routes an inbound button_reply (Quick Reply) webhook to the message controller — there is no equivalent inbound route/handler for CTA/URL button taps, so Glific never learns a URL button was tapped.
• This matches the existing caveat already in this same doc file ("clicks on this button won't be recorded, as the link opens outside and does not send a response back to the flow"), which this PR generalizes into concrete guidance.

Test plan

• Docs site renders the new section and :::note admonition correctly
• Reviewer confirms this matches what's told to orgs on Discord/support

[coderabbitai]

Warning

Review limit reached

@SangeetaMishr, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 38 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 0d62866f-54e8-4373-b996-e4c8f2b39d9f

📥 Commits

Reviewing files that changed from the base of the PR and between 42f330a and 4e8b9ab.

📒 Files selected for processing (1)

• docs/4. Product Features/06. HSM Templates.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🚀 Deployed on https://deploy-preview-642--glific-docs.netlify.app