How to Archive QR Campaigns So Printed Codes Keep Working
To archive a QR campaign, you keep two things: a complete record of what you ran, and a live, useful destination for every code still out in the world. The record covers the artwork, the destinations, the dates, the owner and the results. The destination work means redirecting finished campaigns to a sensible fallback page instead of letting them lead to an error. Do both, and a poster, pack or catalogue printed years ago never becomes a dead end.
This guide shows you what to capture, how to organise it, how to test it, and what to do with the code once the offer is over. It also covers how long to keep scan data and what to think about on privacy in the US.
TL;DR
- Archiving a QR campaign means storing its records (artwork, destinations, dates, owner, results) and keeping every printed code pointing at a useful page.
- Use dynamic codes, so you can change the destination after printing and never have to reprint.
- Redirect finished campaigns to a fallback page that says the offer has ended and offers a next step.
- Export scan analytics before you close a campaign, and set a written retention period for the data.
- Check archived destinations on a schedule, because printed codes stay in the field long after the campaign team has moved on.
Table of Contents
- What it means to archive a QR campaign
- What to keep in a QR campaign archive
- How to archive a QR campaign, step by step
- What to do with a code when the campaign ends
- Keeping archived destinations healthy
- How long to keep records and scan data
- Privacy when you archive scan analytics
- Our perspective: a code should outlive its campaign
What it means to archive a QR campaign
Most teams treat a campaign as finished when the last ad runs. The QR code does not agree. A code on a shelf talker, a menu, a trade-show banner or a magazine page can be scanned for months or years after the budget has gone.
Archiving therefore has two halves:
- The record. A saved, searchable account of what the campaign was: which code, which creative, which destination, who owned it, what it achieved.
- The afterlife. A decision about what each code does from now on: keep serving the same page, move to a newer page, or show a clear “this offer has ended” message.
Skipping the first half means the next team cannot learn from your results. Skipping the second means customers meet broken pages, and your brand looks careless in print, where fixing it is expensive.
The cost of getting this wrong is concrete. If a code is static, the destination is baked into the pattern of squares. When the page behind it moves or disappears, the only fix is a reprint. If the code is dynamic, the printed pattern points to a short link you control, and you can change where it leads at any time. That is the reason archiving is practical at all. Our guide to QR redirection stability explains how the redirect works.
What to keep in a QR campaign archive
A useful archive is a single source of truth. One published best-practice guide suggests an inventory that stores the QR ID, short URL, destination URL, creation date, expiration rules, artwork file, print dimensions, owner and status. That is a sound baseline, and you can extend it with results and approvals.
The campaign record
| Item | What to store | Why it matters later |
|---|---|---|
| Code identifier and short URL | The ID and the exact short link printed | Lets you find the code in your platform when someone asks about a flyer from three years ago |
| Destination history | Every URL the code has pointed to, with dates | Shows which page customers saw at any given time |
| Creation and end dates | Launch date, planned end date, actual end date | Settles questions about when an offer was valid |
| Artwork files | Final vector or high-resolution files, colours, logo placement | Lets you reproduce the code in the same style without guessing |
| Print specification | Size, material, finish, quantity, print supplier | Explains why a code scanned well or badly on a given surface |
| Placement | Where the code ran: store, region, publication, event | Makes scan data meaningful |
| Owner and approver | Named person or team, plus who signed off changes | Stops orphaned codes with nobody responsible |
| Status | Active, evergreen, redirected to fallback, retired | Tells you at a glance what needs attention |
| Results | Scan totals, top locations, device split, peak days | The reason to archive in the first place |
Creative and print assets
Save the files you would need to answer the question “can we do that again?” That means the final artwork, a proof of the printed piece, and the print specification. If a code underperformed because it was too small or low in contrast, you want that written next to the result, not remembered by one person. Our checklist for QR code printing covers the print details worth recording.
Performance data
Before you close a campaign, export the numbers. A platform dashboard is not an archive; it depends on the account staying the same. A CSV export of scans by date, location and device, saved with the campaign record, gives you something you own. Add a short written summary: what you expected, what happened, what you would change. Five lines is enough, and it is the part people actually read next year.
How to archive a QR campaign, step by step
Here is a workflow you can run at the end of any campaign.
- Freeze the record. Fill in every row of the table above. If something is missing, such as the print supplier or the original artwork, find it now while the people involved are still around.
- Export the analytics. Download the full scan data and a summary view. Name the files with the campaign name and the date range.
- Decide the code’s future. Pick one of three outcomes: keep it live on the same page (evergreen), redirect it to a newer relevant page, or send it to a fallback page.
- Update the destination. Make the change in your QR platform and log it with the date, the new destination, and who approved it.
- Test on real devices. Scan the printed code, or a clean copy of it, on at least an iPhone and an Android phone, in the default camera app. Confirm the page loads quickly on mobile data.
- Set a review date. Put the next check in a shared calendar, not in someone’s memory.
- Mark the status. Change the status in your inventory to retired, redirected or evergreen, so the next person does not have to guess.
A formal, logged approach to redirect changes also protects you. Recommended practice is to require ownership, approval tracking and change history so that nobody can quietly repoint a printed code and break the journey for scanners. The same guidance suggests testing printed codes across multiple devices before mass production and scheduling reviews after launch.
What to do with a code when the campaign ends
The worst outcome is a code that returns an error. The second worst is a code that keeps showing an offer that no longer exists, because the customer arrives expecting a discount and leaves annoyed.
For most finished campaigns, the answer is a fallback page. Best-practice guidance is to redirect the code to a useful page that explains the promotion has ended and offers a next step, such as current offers or support. A good fallback page is short and does four things:
- Says plainly that the offer has ended.
- Links to the current equivalent: this season’s range, the main product page or the live promotion.
- Offers a way to get help, such as a contact form or phone number.
- Carries the same branding as the printed piece, so the scanner feels they landed in the right place.
Choose the path by the type of campaign:
| Campaign type | Suggested outcome after it ends |
|---|---|
| Time-limited discount or contest | Fallback page explaining the end, with current offers |
| Seasonal product launch | Redirect to the product’s permanent page |
| Event signage or ticketing | Redirect to the event’s recap, or the next event page |
| Product packaging, manuals, labels | Keep live indefinitely, review each year |
| App download poster | Redirect to the current store listing; see our app download QR guide |
| Print ad in a magazine or catalogue | Redirect to a landing page that suits readers who find the back issue later |
If a lifecycle schedule is available in your platform, use it. You can set a code to switch to the fallback on a given date, so the change does not depend on someone remembering. Our article on QR lifecycle management walks through the stages.
Keeping archived destinations healthy
An archive is not a one-off task. Printed pieces outlive websites. Pages get renamed, domains change, product ranges are retired, and the redirect that worked in March can lead nowhere by October.
Two habits prevent most of the damage:
- Validate on a schedule. Guidance for managing dynamic codes recommends periodic validation of destinations and analytics to find and repair broken journeys, which matters most for printed materials that stay in the field. Quarterly checks suit active and evergreen codes. Once a year is usually enough for retired ones sitting on a fallback page.
- Watch the scan data for odd behaviour. A code that suddenly drops to zero scans may be broken, or the print run may have ended. A code that still gets steady scans after you retired the campaign tells you the printed material is still in circulation, so the fallback page matters.
This is the same discipline that good teams apply to any live digital asset. If you are planning how the pages behind your codes fit into a wider content programme, the guide on planning digital campaigns for organic growth is a handy companion for keeping destinations fresh.
Also keep a short list of “what could break a redirect”: a site migration, a change of domain, a new URL structure, a removed landing page, or a change of account owner on your QR platform. When any of these is planned, check the QR inventory first. A change that takes the web team an afternoon can quietly invalidate hundreds of printed pieces.
How long to keep records and scan data
There is no single answer, and we would rather not invent one. The sensible approach is to separate three kinds of material and give each its own rule.
- Campaign records (artwork, destinations, dates, owner, summary results). These are small and valuable. Keep them for as long as the printed material could still be in circulation, and longer if your company has a records policy that covers marketing files.
- Aggregated results (totals by day, region, device). These contain no personal details and are cheap to keep. Store them with the campaign record for year-on-year comparisons.
- Detailed scan-level data. This is the part that deserves a defined retention period, because it is the most likely to touch personal information. Keep it only as long as you have a reason to, then delete it or reduce it to aggregates.
What affects the period: your internal records policy, any contract or regulatory requirement in your sector, how long the printed material stays in circulation, and your privacy commitments to customers. If you work in a regulated sector such as finance, healthcare or advertising of regulated products, ask your compliance or legal team which record-keeping rules apply to your marketing before you set a number. The article on archiving marketing for financial advisors shows how seriously that sector treats long-term marketing records, and the same planning mindset applies to retiring QR campaigns.
Write the decision down: what you keep, for how long, who can access it, and who deletes it. A one-page policy is better than an unwritten habit.
Privacy when you archive scan analytics
There is no single federal privacy law in the US that covers all scan analytics. Several states have their own consumer privacy rules, and their scope, thresholds and wording differ. We therefore recommend confirming with your legal counsel which ones apply to your business and the people who scan your codes, rather than relying on a general summary.
Some practical principles hold up under any of them:
- Collect less. Aggregated location (city or region) and device type usually answer marketing questions without storing anything that identifies a person.
- Be open about it. If a code leads to a page that collects data, your privacy notice should describe what is collected and why.
- Set a deletion point. Tie scan-level data to your retention rule, and remove it when it has served its purpose.
- Limit access. The archive should be readable by the people who need it, not by everyone with a login.
- Keep a record of changes. If you alter what you collect, note when and why.
Privacy-first analytics make this easier. QRlytics offers GDPR-compliant tracking, which means the platform is built around limited, purposeful data collection rather than collecting everything and sorting it out later.
Our perspective: a code should outlive its campaign
We built QRlytics around a simple frustration: too many QR code services treat your printed codes as hostages. Stop paying, miss a payment, or close an account, and the codes you already printed stop working. For anyone who has put a code on packaging, a shop window or a thousand brochures, that is a serious risk.
Our position is different. A code created during an active subscription keeps working, whatever happens to billing afterwards. We think that is the only fair basis for archiving. If you are going to record a campaign carefully and hand it to the next team, the codes in that record need to still work.
Archiving is easier when the tools support it: dynamic destination updates so a finished campaign can move to a fallback page without a reprint, lifecycle scheduling so the switch happens on the date you chose, real-time scan analytics with CSV export so results leave the dashboard and enter your records, and global scan heat maps that show where printed pieces are still being scanned.
We believe a QR code should turn printed material into a measurable channel, and that channel should not disappear when the campaign does.
*The