Every event, on the record.
Clicks, scans and redirects stream out of rii.link the moment they happen — into your analytics, your channels, your code. This is what the wire looks like.
Illustrative event feed: rows of link events — QR scans, clicks, redirects and agent expansions — each showing the time, the event type, the short link, where in the world it happened, and which destinations rii.link delivered it to (Google Analytics 4, Slack, Zapier, Meta, or a webhook). The sample is synthetic; the columns are the fields a real delivery carries.
14 connections · 3 live · anything else via signed webhooks — see the full catalog ↓
Everything on the wire, spelled out.
What connects, what flows which direction, and how deep the setup goes — honestly labeled: Live works today, In build is on the bench, Roadmap is dated.
Analytics & Pixels
2- Google Analytics 4Native · TargetSee which channels actually drive scans, not just clicks.click + redirect events ⟶ GA4 conversionsclick + redirect events ⟶ GA4 conversionsIn build
- Meta PixelNative · TargetCount offline scans toward ad ROAS and retarget clickers.conversion events ⟶ Meta Ads Managerconversion events ⟶ Meta Ads ManagerIn build
Automation
3- Zapiervia webhooksTrigger zaps on new links and clicks — no code. Until the listed app ships, Zapier's own webhook trigger does the job.new click / new link ⟶ 6,000+ appsnew click / new link ⟶ 6,000+ appsIn build
- Makevia webhooksFeed rii.link events into visual scenarios.link + scan events ⟶ Make scenarioslink + scan events ⟶ Make scenariosIn build
- WebhooksnativeThe platform primitive — every event, signed, to any endpoint.any event ⟶ your endpoint, HMAC-signedany event ⟶ your endpoint, HMAC-signedLive
Communication
2- Slackvia webhooksA message the moment a campaign crosses its threshold.scan / click threshold ⟶ channel messagescan / click threshold ⟶ channel messageIn build
- Email forwardingnativeCatch-all forwarding on your link domain.anything@your-domain ⟶ your real inboxanything@your-domain ⟶ your real inboxLive
CMS & Commerce
2- WordPressvia APICreate branded short links without leaving the editor.shorten + route from the post editorshorten + route from the post editorIn build
- Shopifyvia APIEvery product and collection gets a trackable short URL.product links ⟶ tracked short URLsproduct links ⟶ tracked short URLsIn build
Developer
4- REST APInativeEverything the dashboard does, scriptable.full CRUD on links, domains, analyticsfull CRUD on links, domains, analyticsLive
- Node SDKNative · TargetFull type safety across the API surface.typed client — no raw HTTPtyped client — no raw HTTPIn build
- Python SDKNative · TargetPydantic models across the API surface.typed client — no raw HTTPtyped client — no raw HTTPIn build
- CLINative · TargetPipe link management into scripts and CI.create + manage links from the terminalcreate + manage links from the terminalIn build
Three flows teams actually ship
End to end: a real-world trigger, through rii.link, into the tool where your team already lives.
- QR scan in Berlin → Slack #growth
Know the poster works the hour it goes up.
QR scan — flyer, Berlinqr_scan eventrii.link/berlin-flyerwebhook → Slack#growth · "🔗 Scan — Berlin, DE"today: signed webhook → Slack incoming webhook
- Click on /renew → Zapier win-back
React to interest the second it happens.
Click — churned customerclick event · returningrii.link/renewzap triggerZapier — win-back emailtoday: Zapier's built-in webhook trigger
- QR scan → GA4 conversion
Offline to attribution, without an app.
QR scan — packagingqr_scan eventrii.link/unboxga4.event('conversion')GA4 — attributed conversiontoday: webhook relay → GA4 Measurement Protocol
Not listed? Point a webhook at it.
Anything with an HTTP endpoint is an integration. Every line in the ledger above POSTs the same signed JSON — your code decides what happens next.
# x-rii-signature: sha256=9f2c81… { "event": "qr_scan", "link": "rii.link/berlin-flyer", "country": "DE", "device": "ios" }
Every payload carries an x-rii-signature header — verify it in one line.
click, qr_scan, redirect, expand — one schema across all of them.
Exponential backoff for 24h, replay any delivery from the dashboard.
Don’t see your tool?
Tell us what you run and what should flow. We read every request and build in order of demand — no promised dates; when it ships, it lands in the catalog above.
Your request lands in the same queue our roadmap is built from.
Demand decides order — the more teams ask, the sooner it ships.
Meanwhile, signed webhooks reach the tool today.
Your stack is already compatible.
Connect GA4 and Slack in minutes, wire the rest with webhooks — free while you try it.