Illustration: scattered campaign artifacts — a bit.ly link, a linktree, a flyer PDF, a hand-typed UTM spreadsheet cell, a paid-social tracking URL — converge one by one into a single branded link, go.acme.com/spring-sale, which feeds one scoreboard counting 3,606 taps and scans across four channels.
Track & route every campaign.
Most campaigns scatter into bio links, QR flyers and newsletter buttons that all report somewhere else — so nobody can say which one worked. One rii.link carries the campaign from launch to scoreboard: routed per visitor, measured per channel.
One link becomes the whole campaign.
Follow go.acme.com/spring-sale from brief to results. The card on the left is the same link the entire way — it never gets recreated, it just picks up new jobs.
Interactive: one campaign link, go.acme.com/spring-sale, followed through four stages. The card on the left is the same link the whole way — Plan sets the campaign tag on the destination with the UTM builder and gives each channel its own utm_source on the short link; rii.link records both at click time; Launch activates four routing rules (OS, country, time of week); Measure counts 3,606 taps and scans across four channels, Optimize reads the numbers in the dashboard or over MCP and edits the same link mid-campaign. Outbound webhooks are on the roadmap for Q1 2027; there are no native GA4 or Meta connectors.
Same link, four jobs. Nothing was duplicated, re-tagged or re-printed between stages.
One link. UTMs written once.
Set the campaign tag on the destination once with the UTM builder. Add ?utm_source per channel on the short link — every click records both, and one switch forwards the channel tag to your site.
Change the destination — or the campaign tag inside it — mid-campaign and every printed QR, bio link and newsletter button follows, because they all point at the link.
A branded domain tells people who's behind the link before they commit a click — recognition a generic shortener can't earn. Same routing, same analytics, your name on the door.
works on rii.link out of the box — or connect your own domain via DNS
Same link, right door for every visitor.
One link goes everywhere — add ?utm_source per channel, and the routing rules still decide what each visitor lands on. No second link to create or keep in sync.
The QR and the link are the same object — change the destination after printing and the flyer follows. Reprint nothing.
Every channel, one honest scoreboard.
Each bar is the same link, split by the utm_source on the short link each visitor clicked — a Destination tab beside it counts the campaign tags on the page they were sent to. Illustrative: the dashboard's 30-day view of the campaign's domain — your AI agent can narrow it to one link.
Illustrative analytics view for the campaign's domain, go.acme.com, over the last 30 days: 3,606 human requests (212 known bots excluded), mobile traffic 71% (2,560 requests), top browser Safari, 978 QR scans (27.1% of visits). Campaign tags by utm_source: newsletter 1,284, instagram-bio 942, flyer-qr 978, partner 402 — read from the short link each visitor clicked. Devices: iOS 44%, Android 27%, desktop 29%, across 14 countries.
Put the numbers to work.
Ask your AI agent for any link's numbers over MCP, or build on the REST API and its live click stream for links you create there. No native GA4 or Meta connectors yet — outbound webhooks are on the roadmap for Q1 2027.
Every click with path, device and country — a live view refreshes every 3 s.
Ask your AI agent for one link's clicks, split by utm_source, country or device.
Stats by country, device, referrer or rule for links you create over the API.
Each click on your API-created links as a server-sent event, UTMs included.
Push delivery of every click to your own endpoint — on the roadmap.
No logo wall. Receipts instead.
We're new, and borrowed stats aren't ours to claim. What we can show you is the method — how attribution actually breaks, and the discipline that fixes it.
Your next campaign is one link away.
Plan it, launch it, measure it, optimize it — from a single rii.link on your own domain.