What happens when a link is opened

When a visitor opens a short link, clk.ms checks the link status in a clear order: whether the owner account is active, whether the link has started, whether it has expired, whether the click limit is still available, and whether password, email code, referrer, preview, or warning controls apply. If smart routing rules exist, the visitor can be sent to a destination selected by country, region, language, device, browser, time, date, random split, or fallback availability. If no rule matches, the default destination is used.

When a visitor opens a short link, clk.ms evaluates the user-facing controls that determine whether the visitor can continue and where they should go. The link may be paused because the owner account is frozen, not started yet, expired, deleted, or past its click limit. It may also require a password, an email one-time code, an approved referrer, a preview confirmation, or a warning acknowledgement. These checks are visible as clear pages rather than silent failures, so visitors understand what happened.

If the link has smart routing rules, the destination can change by visitor context. Country, region, browser language, device type, browser family, date, time, random split, and fallback availability can all influence the final destination. This means one short link can serve many audiences while keeping analytics and QR identity in one place. If no rule applies, the default destination is used.

Example: /sale can send Serbian visitors to a Serbian landing page, US visitors to an English landing page, iPhone users to the App Store, Android users to Google Play, and everyone else to the default product page. If the main campaign page becomes unhealthy and fallback is configured, visitors can be sent to a backup destination.

Best practice: keep routing rules easy to reason about. Use priority intentionally, document why each rule exists, and test from the main visitor scenarios before sending traffic to the link.

How to apply this section

Each topic explains a feature, the user decision behind it, and how to use it without making the link harder to manage. Read the checklist before changing a link that is already shared.

Before you publish or update

Start from the visitor experience: who opens the link, from where, on which device, and what should happen next.
Check that the destination is correct, opens quickly, and shows the expected page for the intended audience.
Choose only the controls that match the goal, such as expiration, password, referrer, QR design, UTM, routing, or analytics sharing.
Save a short note for important changes so future review, rollback, or teamwork stays clear.
Open the short link in a private browser session and, when relevant, test mobile, desktop, QR scan, and protected access paths.
Review analytics after sharing to confirm real visitors, source quality, device mix, and campaign performance.

Practical example

Example: create a test link for an internal page, add a clear slug, set a short expiration, enable preview if the destination is sensitive, scan the QR code from a phone, then check whether the visit appears in the link statistics.

Next step

After this topic is clear, combine it with one adjacent feature. For example, pair UTM with campaigns, QR with print layouts, targeting with fallback, or webhooks with conversion tracking.