Refactor/ctas and utm tracking

[LeonardoVieira1630]

Summary

• Refactored CTA buttons to use dynamic URLs pointing to specific AntiCapture pages (proposals, delegates, voting power) instead of the generic homepage
• Added UTM tracking parameters (utm_source, utm_medium, utm_campaign) to all notification button URLs for engagement tracking across Slack and Telegram
• Passed triggerType metadata through each trigger handler so consumers can build UTM params per notification type
• Extended buildButtons to accept daoId, address, and proposalId for constructing context-aware URLs

Changes

• packages/messages/src/triggers/buttons.ts — Replaced static CTA URLs with dynamic URL builders per trigger type (e.g., link to specific proposal, delegate page)
• packages/messages/src/formatters/utm.ts — New utility to append UTM query params to URLs
• apps/consumers/src/services/bot/slack-bot.service.ts — Applies UTM params to button URLs before sending Slack messages
• apps/consumers/src/services/bot/telegram-bot.service.ts — Applies UTM params to button URLs before sending Telegram messages
• apps/dispatcher/src/services/triggers/* — Updated all trigger handlers to pass daoId, address, proposalId, and triggerType metadata

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
flow-editor	Ready	Preview, Comment	Mar 4, 2026 9:07pm
notification-system-dashboard	Ready	Preview, Comment	Mar 4, 2026 9:07pm

[PedroBinotto]

looks good to me