Back to help
04

History, deletion, and reuse

A link can change over time without losing its identity. clk.ms keeps the destination history, notes for each change, who changed it, when it changed, and which version was active during a period. Owners can roll back to an earlier destination. When a link is deleted, expires, reaches its click limit, or is removed because it stayed inactive for a long time, visitors receive a clear status message where appropriate. Freed identifiers can be used again for new links, while deleted-link history helps explain what happened.

Short links often live longer than a single destination page. A campaign page can move, a product URL can change, a seasonal offer can end, or a mistake can be corrected. Destination history lets the short link keep its identity while recording how the target changed over time. A history entry should answer practical questions: what was the previous destination, what is active now, when did the change happen, who made it, and why was it changed.

Deletion and expiration are also part of the link lifecycle. When a link is removed, expires, reaches its click limit, or is cleaned up after long inactivity, the short identifier may become available again for future use. At the same time, history helps explain that a link once existed. This is important for support, audits, campaign reviews, and user trust.

Example: /black-friday first points to a teaser page, then to the main sale page, and later to an archive page. Each change includes a note such as teaser launch, sale started, or sale closed. If the archive page is wrong, the owner can roll back to the previous version without creating a new short link.

Best practice: write short but meaningful notes for destination changes. Treat public short links as durable assets: avoid deleting them during active campaigns, prefer expiration for planned endings, and use rollback when a previous destination is known to be correct.

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.