Start with a decision, not a dashboard
Before collecting scan data, write the decision it will support. You might want to know whether a counter sign or a delivery insert brings more visits to a service page. That question needs placement-level counts over comparable dates, not names, exact locations, or a detailed history of each visitor. A narrow question makes the campaign easier to evaluate and reduces the temptation to collect information simply because it could be interesting later.
Define success separately from scanning. A scan may lead to a page visit, but it does not prove a purchase, completed application, or satisfied customer. If your real goal is quote requests, document how those requests will be counted in the receiving system. Treat that as a separate measurement process with its own notice and permissions. Do not imply that QR scan analytics automatically observe everything someone does after leaving the redirect.
Understand static and dynamic measurement
A static QR contains its content directly. QR Code + Pages does not collect scan data when someone scans a static code because the scan does not pass through its servers. If that code opens your website, the website may separately record visits under its own analytics setup. Those visits are not the same thing as a built-in record of every scan, and their handling needs its own privacy consideration.
A dynamic QR points through a managed short link before reaching the destination. QR Code + Pages counts those scans and lets you change the destination without replacing the printed symbol. Dynamic codes require an account and active service. Decide on this approach before printing if measurement matters: a static code already on a flyer cannot be remotely converted into a dynamic redirect by changing settings in an unrelated dashboard.
Set up comparisons that answer the question
Use a separate dynamic code for each placement you need to compare. For example, label one code for the checkout counter and another for the delivery insert. Keep their destination, offer, and reporting period comparable when you want to understand the effect of placement. If the two codes advertise different services, a difference in scans cannot be confidently attributed to the location of the printed material alone.
Maintain a simple campaign record with the code name, physical location, launch date, responsible person, and any changes. Record when a sign moves or a batch runs out. Exclude your own testing from interpretation where possible, and note known test activity rather than assuming every event came from a prospect. Compare complete periods, not a full weekend for one placement against a single weekday for the other.
Read the available metrics with limits in mind
QR Code + Pages analytics include total and unique scans, scans over time, approximate country and city, device, operating system, and browser, with CSV export. Total scans are activity, not a census. One person may scan several times, and a shared device can serve more than one person. Unique counts are estimates based on the system's counting method, not verified identities or a reliable head count for an event.
Location is approximate and derived from the internet connection, not GPS. Mobile routing, corporate networks, and privacy tools can make the apparent city differ from where the person actually stands. Use broad patterns to understand reach, not to accuse someone of being in a particular place. Device and browser information can help prioritize testing, but it cannot tell you a visitor's income, intent, or reason for not completing an action.
Collect the minimum and explain it plainly
The privacy policy states that dynamic codes and hosted pages record date and time, approximate location, device information, operating system, browser, language, and referring app when available. IP addresses are used to derive location and detect bots and abuse; customer analytics are aggregated and do not show full IP addresses. QRP does not ask scanners to sign in, use GPS, or build advertising profiles of people who scan.
Explain the measurement in language your audience can understand, and link to a relevant privacy notice at the destination. The appropriate notice and consent requirements depend on your audience, jurisdiction, and other tools used on the destination. Do not assume a QR eliminates those duties. Public hosted QRP pages do not set tracking cookies, but a separate website or service you link to can have different practices and must be assessed independently.
Protect exports and avoid unnecessary identification
A CSV export is useful for comparing weeks or sharing a short campaign report, but it also creates another copy of the data. Save exports only where authorized staff can access them. Share an aggregate summary when a colleague needs trends rather than underlying records. Review workspace roles so people who only need to read results do not receive broader editing permissions just for convenience during a busy launch.
Do not put names, phone numbers, medical details, or customer identifiers into campaign URLs to make reports more detailed. Those values can leak through logs, forwarded links, and screenshots. Establish a review and deletion routine for your own exports. QRP's policy describes scan retention as lasting for the life of the code or as defined by the plan, with possible retention in aggregated non-identifying form; do not invent a universal short retention period.
Report honestly and improve one thing at a time
Build a short report around the original question: period, placement, total and unique scans, relevant downstream results, and known limitations. Include operational context such as a closed location or missing sign. Avoid dividing scan counts by an invented audience estimate to produce a precise-looking response rate. If you know how many inserts were distributed, explain that scanning more than once and sharing links can still affect the interpretation.
Change one variable for the next round, such as the invitation wording or the sign's position, while keeping other conditions reasonably stable. Use QR Code + Pages dynamic QR codes when you need editable destinations and scan analytics. Keep the measurement proportional to the decision: a useful report should help you make the next improvement, not create a database of identifiable people who simply wanted to open a link.