Back to help
13

Destination versioning and rollback

Every meaningful destination change can include a note. The link history shows the previous destination URLs, the current destination, who made each change, when it happened, and the active period for each version. Rollback restores a selected earlier destination while preserving the history of that rollback. This is useful for campaign launches, seasonal pages, partner URLs, and correcting mistakes without creating a new short link.

Destination history and rollback

The link card → «Settings» → «Destination history» displays address versions, active periods, change type, author and note. History helps determine where a link led during a particular campaign.

To search, specify the UTC moment and press «Find version». The main target URL is checked at this point; choosing a personal routing rule for a specific visitor is a separate issue.

To revert, select an available previous version, provide a note if necessary, and click rollback. Rollback makes the selected address current and saves the change in history; past entries are not overwritten. Check the relevance of the address itself, UTM and rules after the return.

The target URL history is not a backup of all link settings. It does not restore the deleted account, groups, QR design or all access restrictions. To investigate, compare the history with dates in activity and saved reports.

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.