Back to help
18

Lifecycle automation

clk.ms handles routine link lifecycle tasks automatically. Links stop working when their start date has not arrived, when their expiration date passes, or when their click limit is reached. Old inactive links can be removed, temporary bans can expire automatically, and permanently blocked addresses remain blocked. Short identifiers released by expired or deleted links can become available again, helping the service keep short links compact over time.

Deletion, expiry and code reuse

The link stops regular clicking on the link when it expires or reaches the limit. If a fallback destination URL is configured after completion, it may open. Otherwise, the service shows an unavailable state; background procedures may subsequently delete the master entry.

Removing from “My Links” is a separate action. Check the selected line and confirmation. After removal, the usual click on the link and associated tools may no longer be available. Historical information is not a promise of full recovery through the interface.

The service also clears links that have not been used for three years. For a link without a single click on the link, the period is counted from creation, otherwise - from the last click on the link. Having a forever mode or fallback URL does not override this inactivity rule.

The released short identifier can be reused. Therefore, deleting an old link cannot be considered a way to permanently reserve its address. For a long-lasting printable QR, keep the active link and change its target URL instead of deleting and re-creating it.

Publication checklist

• The link has been created in the desired account; the domain and ID correspond to the location.

• The target URL opens and contains the correct UTMs.

• Dates are recalculated in UTC, the limit corresponds to the plan, and the completion of the campaign is provided for.

• For each significant language, device, and time, the rule selection is tested; There is a working default option.

• The comments in the diagnostic report were studied; saved JSON if you need a startup log.

• In the new session, the real password chain, OTP, referrer, warnings and link click are checked.

• The exported QR and proof print are scanned; The link/vCard mode was chosen deliberately.

• Test conversion and webhook are checked where they are needed; messages reached through the selected channels.

• Colleagues were given the necessary rights, the recipient's report was checked without the owner logging in.

• Once published, actual link clicks and the status of the destination URL are tracked; old printed links are not removed without assessing the consequences.

To consistently master these actions, go to Practical course.

Complete user guide ยท Practical course

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.