The VeloConnect link shortener wraps any URL you send into a short, trackable redirect. It’s built in — no third-party shortener to wire up, no separate analytics tool to reconcile against. Clicks land on your campaign report and on the contact’s activity timeline alongside everything else you know about them.
How it works
When you compose a campaign (or a one-off message in the inbox), toggle Add tracking link in the composer and paste the destination URL you want the recipient to land on. VeloConnect generates the short version automatically — something like velo.gg/x7Qp2k — and substitutes it into the message body in place of the long URL.
When the recipient taps the short link, VeloConnect logs the click against that recipient (or against the campaign as a whole, depending on the mode you picked), then 302-redirects them to the original destination. The redirect happens in well under 100 ms — the customer doesn’t notice it’s there.
Per-message vs per-campaign
Two modes, picked at compose time:
- Per-message — each recipient gets their own unique short URL. Click data is attributed to the individual contact. Best for sales follow-up, account-level outreach, or anything where you want to see which named customer engaged.
- Per-campaign — every recipient gets the same short URL. Click data is aggregated. Useful for high-volume marketing blasts where per-recipient detail is overkill (and where the message-volume cost of generating unique URLs adds up).
Default is per-message for campaigns under 10,000 recipients, per-campaign above that — both can be overridden.
What you see in the report
The campaign report panel adds a Links section when tracking is enabled. Across the date range of the campaign:
- Total clicks — every tap, including repeats by the same person.
- Unique clicks — distinct recipients who tapped at least once.
- By date — daily click curve, useful for spotting how quickly a campaign’s engagement decays.
- By country — clicks bucketed by the recipient’s country (from the contact, not the IP).
- By contact — the per-recipient list, with click count and timestamp of the first click. Click through to the contact’s profile to see the whole history.
On the contact side, the activity timeline shows the click as a discrete event alongside the message that contained the link — see Notes and the activity timeline.
Webhooks for downstream systems
Admins can subscribe a webhook to the link.clicked event so the click pushes into a downstream system the moment it happens — CRM (HubSpot, Salesforce, Zoho), an attribution engine, a BI warehouse, an internal ops tool.
Setup is in the developer settings under API → Webhooks. Add a destination URL, pick link.clicked from the event list, and save. VeloConnect signs each payload with an HMAC header so your receiver can verify it. Payload shape, retry behaviour, and signature verification are documented at docs.veloconnect.me.
A practical note
For most teams, per-message tracking is the right default — the contact-level data is what makes campaigns measurable. The exception is bulk newsletter sends where the cost of generating tens of thousands of unique short URLs outweighs the analytical value. The shortener toggle lives next to the composer (shown contextually in Creating a campaign, Fig. 2).