Analytics & link tracking

Two things are measured, and it's worth knowing which is which. Clicks are measured per group, and they're the honest signal for interest — someone chose to tap. Delivery and read receipts are measured per recipient, so once your number has been sending for a while you can also see how many people a send actually reached and how many opened it. Neither is a vanity number, and where a figure isn't measured the page shows nothing rather than a guess.

Analytics unlocks after your first send.

How link tracking works#

Any http(s):// URL in an outgoing message is rewritten into a short tracking link, separately for each group. Group A and group B get different short links pointing at the same destination.

That per-group split is the whole trick: when someone clicks, we know which group it came from, and therefore which tag — which is how the app can tell you that alumni clicked and second-years didn't.

You don't configure anything. Paste the real URL and it gets rewritten on the way out. (On a self-hosted deployment with no short-link host configured, URLs go out untouched and no clicks are recorded — the hosted service has this set up.)

Recipients see a promotionbot.net/r/... link. On the Pro plan you can use your own domain instead, so links carry your name.

Tracked links are reported against your plan's monthly figure in the billing panel, though that figure isn't currently enforced (Plans & billing).

What the page shows#

Pick a range — last 7, 30, or 90 days, or lifetime — and you get:

Four headline numbers: messages delivered, link clicks, groups reached, failed sends. The clicks tile is a count, not a percentage — deliberately, since there's no per-send reach figure to divide by.

Delivery & engagement over time — messages and clicks on one chart. The useful read is the gap between them: sends going up while clicks stay flat means you're increasing volume, not attention.

Performance by audience — per-tag click rate with a volume cue underneath each bar. Rows are ordered by click volume, so read the rate rather than the position, and read the volume cue too: a 40% click rate on one group of nine people is not a strategy.

Click rate by campaign and top campaigns — which campaigns actually work.

Delivery outcome — delivered versus failed.

Best send time — the day and hour that historically get you the most engagement, in your own timezone. Use it, then re-check it next term; it moves.

Top groups — ranked by clicks, with each group's click rate alongside. Click any row for a per-group drilldown.

Everything is exportable to CSV.

Event funnel#

For events, a funnel view showing how the timeline performed slot by slot — which message in the ladder actually drove the clicks. This is how you find out that your reminders do the work and your save-the-dates don't.

What isn't measured#

Being straight about the limits, because they affect how you read the numbers:

• Receipts only exist going forward. Delivery and read receipts are recorded per recipient, but only for messages sent after this was switched on. Older sends show "Messages sent · no delivery receipts yet" — that blank is deliberate. An empty cell means not measured, never zero and never an estimate.
• Read means opened, not read. A read receipt says the message was opened on someone's phone. It does not say they took it in, and a recipient with read receipts disabled never generates one — so treat the read rate as a floor, not a headcount.
• Reach is people where receipts exist, groups where they don't. Delivery and read rates use a recipient (people) denominator drawn from receipts. Click figures are still per group. Don't mix the two in one sentence to a board — say which you're quoting.
• No per-person data. A group broadcast has no per-recipient identity, so there's no way to know who clicked — only which group.
• No RSVP or attendance tracking. Sign-up links redirect to whatever you point them at; what happens there is that tool's business.

Team visibility#

Non-admins see their own number's clicks. Send volume is org-wide (it isn't recorded per number), so a member sees the organisation's send totals alongside their own click data. Admins can toggle team-wide stats.

Send failures#

Sends fail — a group the account was removed from, a media upload WhatsApp rejects, a network blip. Failures are recorded with the reason and the group, rather than disappearing into a log.

Check this page after any large send. A cluster of failures on one number is worth investigating before your next send; see Troubleshooting.

Monitor#

Available on Team and Pro. Monitor watches incoming messages on your number and alerts you on things you care about — keywords, and optionally competitor activity in shared groups.

Two parts:

• Alerts — keyword matches in incoming group messages, with a per-day breakdown so you can see whether a topic is heating up.
• Competitors — a list you maintain; Monitor flags their activity where your number can see it.

You can pause Monitor without losing its configuration. On Starter the tab shows an upgrade prompt rather than pretending to have data.