Live
API SHAPESAnalytics & UTM
rii.link records campaign tags on every click from two places: the UTMs on the short link someone clicked, and the UTMs on the destination they were sent to. Tag destinations with the built-in UTM builder (or the utm field in the API), share the link, and read both breakdowns side by side.
HOW CAMPAIGN TAGS WORK
→The builder: in the dashboard, open “Campaign tags (UTM)” under a destination — in the Links page shorten form, or on a redirect in the workflow editor. Fill source, medium, campaign, term and content, check the live preview of the tagged URL, then press Apply→Consistent tags: values are trimmed and source and medium are lowercased, so “Email” and “email” stay one row. A tag already on the URL is replaced, never duplicated, and every other query parameter is left as it was→API and MCP: send utm on POST or PATCH /v1/links and the tags are written onto url; every link response returns them in utm (null when absent). On PATCH only the keys you send change, null removes one, and "utm": null strips them all. MCP create_link and update_link take utm too, and build_utm_url previews a tagged URL without saving→Short-link tags: add ?utm_source=newsletter (or any utm_*) to the short URL you post in each channel — or set it as a QR code’s additional parameters — and each click records it. Use this for the channel→Destination tags: the UTMs on the destination actually served for a click — after routing rules and splits — are recorded with it. Tag each rule destination on its own if you want its clicks to carry different tags→Reading the breakdown: dashboard → Analytics, pick a domain and period, then the Campaign tags card. The Short link tab counts the tags on the URL people clicked; the Destination tab counts the tags on the page they were sent to. Each tab splits by source, medium, campaign, term and content. A single request in the request log shows both sets→The two tabs answer different questions: Short link says which channel copy was clicked; Destination says which campaign the landing page was tagged with — the same values your site’s own analytics will see. A click can carry both, one, or neither→Raw data: the click-log export (Settings → Export, or GET /v1/export/request-logs) has utm_* columns for the short link and dest_utm_* columns for the destination. MCP analytics_summary returns utm and destination_utm. GET /v1/links/{id}/stats groups by country, device, referrer or rule — not by UTM
The utm field in the reference→ API · Links
Create and update with utm, the PATCH rules, and the utm object on every link.