Destination Rotator

A rotator turns one short link into a front door for up to twenty destinations. The address stays fixed — printed on a poster, pasted into a bio, embedded in a placement — while what sits behind it changes as often as you need.

The rotator is a paid capability, configured in the Rotator tab of the link dialog.

Destinations

Each destination carries:

| Field | Meaning | | --- | --- | | URL | Where this destination sends people | | Weight | Its share of traffic relative to the other destinations | | Active | Off takes it out of rotation without deleting it | | Total cap | Stop after this many clicks in total | | Daily cap | Stop after this many clicks today, then resume tomorrow | | Start / end | The window during which this destination is a candidate | | Countries | Restrict this destination to specific countries | | Devices | Restrict this destination to desktop, mobile or tablet |

A destination that has used its cap steps aside and the others absorb its share according to their weights. A destination whose window has not opened is not a candidate yet. When every destination is unavailable, the fallback address catches the remainder; without one the link serves its main destination.

Sticky visitors

Rotation without stickiness produces nonsense: someone opens the link twice, sees two different offers, and the funnel report becomes fiction. The sticky window keeps one visitor on the destination they first received.

The choice is derived from the visitor's fingerprint rather than stored per visitor, so it survives without a session and without a database row. Set the window to zero to rotate on every visit.

Health checks

Destinations rot: a partner takes a page down, a certificate expires, an offer is pulled. A scheduled check watches destinations and takes an unhealthy one out of rotation automatically, leaving the others to absorb its share.

Removal is visible rather than silent — the destination is marked as auto-disabled, and an alert rule can notify the workspace the moment it happens. Re-enable it by hand once the page is back.

Counting across an edge network

Caps only mean something if they hold when the same link is opened simultaneously in a dozen countries. Counters live in a shared store with a reservation step ahead of the redirect, so a destination limited to a thousand clicks does not deliver fourteen hundred because fourteen data centres each counted to a hundred.

Counter snapshots travel inside the link's cached configuration, so the redirector does not need a round trip to know roughly where a destination stands; the authoritative reservation happens only for destinations that actually have caps.

Reading the results

Every click event records which destination served it. Clicks, unique visitors and — with conversion tracking enabled — revenue can all be broken down per destination, which turns "which of these five pages actually earns" from an argument into a table.

Order of evaluation

The rotator runs after expiry, password and social-preview handling, and after traffic rules. Within destination selection the order is: candidates filtered by active state, window, caps, country and device, then the sticky choice, then weights.

Limits by plan

Plans can cap the number of destinations per link. As with every other paid capability, the cap applies to adding destinations: a link that already has more keeps working and stays editable after a downgrade.