Link Launch Checklist: UTMs, QR Codes and Fallbacks

A launch link often appears in several places before the landing page is final: a newsletter draft, a creator brief, a printed insert and a scheduled post. A small mistake can spread to all four. This checklist helps you prepare those links in Lumeraya before distribution, while keeping each placement identifiable.

Start with the destination, then name the placement

Open the final destination on a phone and a desktop. Check the page, its primary button and any sign-up or checkout step. A successful redirect is only the beginning of that journey.

Create a separate short link for each placement you want to measure. For example, a newsletter button and a package insert can point to the same page but use different aliases. Put the related links in one folder and use a tag for the launch date or product release.

Keep a short record of where each public link will appear. That makes it easier to change the correct destination later, especially after printed material has left your hands.

Set UTM tags before sharing links

Agree on a naming pattern before colleagues copy URLs into their drafts. Use utm_source for the source, utm_medium for the channel, utm_campaign for the promotion and utm_content for the specific placement.

A newsletter and a printed insert can share utm_campaign=autumn_launch while using different source and medium values. Two buttons in the same newsletter can differ only by content. Consistent lowercase names keep accidental variants out of your reports.

The UTM campaign parameter is a tracking label. It does not create a Lumeraya Campaign: Campaign creation and campaign reports are Business-only. The Links Help Center explains the available tracking tools.

Check the public launch link and QR artwork

If you use a custom domain, wait until it is Ready. Ownership verification alone does not confirm that DNS routing and HTTPS work.

Open the exact alias you plan to publish, including its spelling. Check any password, activation schedule, expiry date or visit limit you configured. A restricted test link should not accidentally become the address on thousands of inserts.

For a QR code, export the artwork and scan the actual design from a sample at its intended size. Try more than one phone and ordinary lighting. A code that looks attractive on a large monitor may be harder to scan on a small, glossy label.

Decide what happens when the destination changes

A dynamic QR code points through its managed short link. You can update that link's destination while retaining the printed code, provided the link and domain remain active.

For Growth and Business links, consider a backup destination with Monitor. It checks the main destination periodically and can use the backup after confirming an outage; it is not an instant outage detector. Matching Smart Routing rules can take precedence, so test the actual paths you have configured.

Keep your fallback useful. An explanatory product page or an alternative contact form is usually more helpful than an unrelated homepage.

Make the first report interpretable

Write down the launch time and the outcome you want to measure. If you use Growth or Business and need conversions or revenue, connect and test the reporting integration before launch. Those events do not appear automatically just because a shop URL has been shortened.

Separate your preparation period from the launch reporting window. Review clicks alongside estimated unique visitors and the relevant UTM breakdown. Compare equivalent date ranges, and avoid declaring a winner from a handful of visits.

Hand over a small launch checklist

The person who prepares the tracking may not be the person who presses Publish. Give that colleague a compact handover with the final alias, its intended placement, the destination and any date restrictions. Avoid sending a collection of similar test URLs with no indication of which one is approved.

For a printed insert, keep the final artwork beside the short address it represents. For a newsletter, include the destination in the approval note so a reviewer can recognise a mismatch before sending. The public URL should be easy to identify without opening a spreadsheet full of drafts.

Treat the following as separate checks rather than assuming one successful scan proves the whole setup:

• The exact public address opens on an ordinary device without an administrator session.
• The destination offers the action described in the placement, such as downloading a guide or registering for an event.
• The tracking values identify that placement consistently with the rest of the promotion.
• Any conditional destination and fallback have been checked independently.
• The colleague maintaining the landing page knows which published materials depend on it.

If you enable an A/B split, tell the reviewer to expect different destinations and record the variants before distribution. A single test visit only shows one possible outcome. Run enough deliberate checks to inspect each configured destination rather than assuming the other page behaves the same way.

The Lumeraya Links use cases can help you choose a workflow for printed material, creator placements or destination testing. Use the tools that solve a specific launch requirement; a simple promotion may need only a well-labelled short address and one working page.

Diagnose the first day before changing the plan

If clicks arrive but conversions do not, first check whether the reporting integration is connected and whether your test action produced the intended event. Next, inspect the destination and its primary action. Missing outcomes may reflect setup or usability, so do not immediately conclude that the placement brought the wrong audience.

If one placement has little traffic, verify that the published address matches the approved alias and that the post or mailing actually went live. A creator's delayed publication and a mistyped URL need different fixes. Ask for the final placement link or artwork as part of your own review process.

Once the basic checks pass, allow enough time for the promotion's intended response. Save a report with its date range and filters before making substantial changes. That record gives the next review a concrete starting point instead of relying on an impression of yesterday's dashboard.

A prepared launch leaves you with three things: a tested public address, a clear placement label and a plan for destination changes. Build that foundation in Lumeraya Links before the first newsletter is sent or the first QR code is printed.