Skip to main content

QR Codes That Open Your App: Install Fallback, Edits After Print and Scan Tracking

A QR code on a box, a poster or a table card is the one link you cannot correct after it ships. A wrong address in a post can be edited. A wrong address on packaging stays wrong until the last pack is sold.

This guide treats the printed code as a deep link on paper. A deep link is a link that opens a specific screen in an app instead of a web page. It covers what has to happen on each device that scans the code, why the destination must stay editable after printing, and how to tell scans apart from other traffic.

The printed code is only a web address

For an app campaign, the data in a QR code is a web address. Apple's instructions for iPhone say to hold the device so the code appears in the Camera app, then tap the link to open the content. Google's instructions for Pixel phones say to point the camera at the code, then tap the link that appears.

So a scan is a tap on a link. The code cannot know which phone is reading it, whether your app is installed, or whether the campaign has ended. That is decided after the tap, by the phone's rules for links and by the server behind the address.

The three cases on scan

The address has to work in three cases.

The app is installed

Apple calls links that open an app universal links: the system sends the link to the app without going through the browser, after checking a file on your web server that allows it. Android calls them App Links: Android verifies the association through a file hosted on the website, then routes matching links directly to the app.

Both need setup in the app and on the link's domain, and scanner apps vary in how they open a link, so test this case on real phones. If a scan opens the browser or a store although the app is installed, see why a link opens the store or the browser instead of the app.

The app is not installed

Apple's page says that without the app the system opens the address in the browser, and Google's says that with App Links such users go to your website. The server behind the address then has to send the phone to the right store.

When the app later opens for the first time, the scanned address is no longer there to read. Carrying it across the install is called deferred deep linking: the link service records the tap, an SDK (the service's library inside your app) reports the first launch, and the two are matched.

The address is opened on a computer

Printed addresses get typed into laptops, and links get forwarded to people at a desk. Send computers to a web page, or show a page that lets the visitor continue on a phone.

Print a short link you can change

Two kinds of address are tempting to print, and both are mistakes.

  • A store address. It points at one listing in one store, so it cannot name a screen in your app. The visit never reaches a server of yours, so there is nothing to count or change.
  • A long address. The full address of a web page with campaign labels attached is frozen once printed. It also makes a bigger code: qrcode.com explains that more data needs more modules, the black and white dots.

Print a short link instead. The address never changes, and what it does is a record on a server that you can edit.

What stays fixed and what stays editable

In AdTo a link is https://<username>.adto.app/<slug>. The slug (the last part of the address) and the app a link belongs to cannot be changed after the link is created. What a scan leads to can be changed through the API, and for most of these fields in the dashboard's Edit link drawer:

  • the route the app opens (an iOS and an Android deep link path) and the link's metadata, free-form values for the app;
  • where a phone without the app goes: the store by default, or a custom address;
  • where a desktop visitor goes: a custom address, the app's Fallback URL, or AdTo's branded QR page;
  • the link's target, the web address used as the last fallback;
  • routing rules by country, language, date range or share of visitors;
  • an expiry.

The app sees those edits too. When a link opens the installed app, the SDK looks the link up on the server and hands the app its target, metadata and route. After an install credited to the scan, the app receives the matched link and its metadata.

Two actions break a printed code. Pausing a link gives every scan that reaches the server a "Link paused" page and records nothing. Deleting it gives a "Link not found" page. Resume and Restore undo them; Delete permanently cannot be undone.

Telling scans apart from other traffic

AdTo records a scan as an ordinary click. If the link on the poster is also the link in your bio, their numbers cannot be separated.

A link per placementLabels in the address
Labels after printingEditable, because they are saved on the linkFixed, because they are printed
Where you read itPer-link numbers in the Links listThe Overview's charts and Breakdown, by UTM value

The first two addresses are a link per placement; the third carries labels.

https://acme.adto.app/box
https://acme.adto.app/poster

https://acme.adto.app/get?utm_source=poster&utm_campaign=spring

A link per placement is the better default for print. An AdTo link can carry its own UTM values (labels such as utm_source), and a click whose address has none stores the link's. The Overview's installs by campaign and by source charts read utm_campaign and utm_source, so set those two. Labels printed in the address win over the link's own values. Every parameter AdTo reads is under URL parameters.

Scans against installs: what each number means

These are the per-link numbers in AdTo's Links list, for a link that exists only on paper.

NumberWhat it countsFor a printed code
ClicksEvery web tap, every click the SDK reports, and every click rebuilt from an install referrerScans, including those by people who already have the app, and visits from a computer
OpensTimes the link opened the already installed appScans that opened the installed app
InstallsFirst installs matched to one of the link's clicks, with reinstalls listed separatelyFirst installs credited to the code
conv.First installs divided by the click counterThe share of clicks that led to a first install
  1. An install is a first launch. The SDK reports it when the app first opens. Someone who downloads the app and never opens it is not counted.
  2. Not every install can be matched. The match is exact on Android, where the SDK reads the click id back from Google Play's install referrer, and on iOS when the scan went through the tap-to-store page, a page with a Get button in front of the App Store that you turn on for the app. Otherwise AdTo compares the tap and the first launch by fingerprint (a scored comparison of the two) and credits only a unique high-confidence match. An unmatched install counts as organic, so a link's install number can undercount. How attribution works has the detail.
  3. The counter counts taps. One person scanning twice adds two. Bots and link-preview crawlers add nothing. The per-link numbers are all-time totals; for a date range, use the Overview's Breakdown by link or by UTM value.

Short campaigns and links that expire

Paper outlasts the campaign it was printed for, so decide before printing what a late scan gets. AdTo has three tools.

  • An expiry on a permanent link. Set Expires at and After expiry, send visitors to. Later scans that reach the server go to that address, or to a "Link expired" page when none is set. An expired link records no clicks.
  • A scheduled routing rule. A rule with a start and an end replaces the link's destinations for that period and then steps back. It suits a pack whose offer changes.
  • A temporary link. The dashboard offers lifetimes of 5 minutes, 1 hour, 1 day or 7 days, and the API accepts up to 30 days. The expiry cannot be changed afterwards, and the Links list shows no click or install numbers for it. See Temporary links.

A temporary link fits a card for a one-evening event. For packaging and posters, use a permanent link with an expiry.

Test before you print

  1. Make the code from the final address. Test the exact code that goes to the printer.
  2. Scan with the app installed. Use a real iPhone and a real Android phone, with the built-in camera and any scanner app your audience uses. The app should open on the right screen.
  3. Scan without the app. The right store listing should open. Install, open the app, and check the first screen.
  4. Open the address on a computer. It should show a page you chose.
  5. Change the destination and scan again. Prove the edit works before the print run.
  6. Scan the printed proof. Use the real material at the real size.
  7. Keep test taps out of the numbers. Scans of the real code count as clicks. For checks by hand, AdTo routes a link opened with ?adto_nt=1 exactly like a real tap and records no click. Never print that parameter.

Doing this with AdTo

AdTo is a hosted link service for mobile apps. Every tap is routed by device: the installed app, the App Store or Google Play, a fallback address, or a branded QR page on desktop. The Flutter SDK, flutter_adto, reports the first launch so an install can be matched to the scan.

For print, the link itself is the payload: encode the link's address with any QR library. The only code AdTo draws is on the branded QR page, which desktop visitors get when neither the link nor its app has a desktop fallback address. That page shows a code of the link without any parameters, store badges and "Open in app" buttons, and scanning it counts as a new tap on the same link. A phone sees that page only when it has no destination at all, so add the app's store addresses before you print.

Create an AdTo account, make one link per placement, and run the test list before the file goes to the printer. Social previews and the QR page describes the desktop page, and How a tap is routed gives the full decision order.