From print to phone: planning a QR campaign and measuring response

1. Define the benefit and destination before creating the code

Choose one action suited to the printed item: viewing a service list, reading product details, booking through an available channel or requesting a quote. Add a specific instruction such as “See available sizes” instead of only “Scan here”. The visitor should quickly find the promised information or action after opening the page.

Review the page on a phone in the audience’s relevant languages. Check the heading, contact buttons, form and confirmation message. When details change often, consider a stable address you control and update its content, rather than printing the address of a temporary file or a page outside your control.

2. Use organised links to distinguish campaign sources

Google explains that UTM parameters help Analytics identify traffic sources and campaigns. Use consistent source, medium and campaign names; utm_content can distinguish two designs. Uppercase and lowercase values may be recorded separately, so agree one naming convention before creating the codes.

As a planning example, a reception brochure and exhibition poster can use different links that reach the same page. Keep a record of the item, version, link and distribution date. Ask the website owner to verify measurement setup and data reception; adding parameters to a URL does not create an analytics system by itself.

• A campaign name the team understands and keeps unchanged throughout the test.
• A separate link for each source you want to compare, without personal details.
• A destination and measurement test before approving the print file.

3. Make the code scannable in its real setting

DENSO WAVE specifies a clear margin around a standard QR code that is four modules wide on every side; a module is one of the small squares making up the code. Keep text and decoration out of that margin. Start with clear contrast and an undistorted code, then test its final size for the code density, viewing distance and material.

Print an actual-size sample and test it with the intended finish, on more than one phone and under lighting similar to the display location. Check glare, folds and curvature, and keep the code away from cutting lines or inaccessible positions. Scanning from the designer’s screen is not enough to approve an item that will sit behind glass or on a glossy surface.

4. Read the results against the question you want answered

A page visit is not an order, and opening a messaging app does not prove that a message was sent. Agree with the measurement owner what you will record: a campaign-associated visit, a successful form submission or an enquiry confirmed by staff. If sales happen in-store, you need a separate way to connect them with the campaign, such as an offer code recorded when used.

Record how many items were actually distributed, their locations and display period, using a consistent response definition. One person may visit repeatedly or share the link, and measurement tools may miss visits. Do not label website sessions “people who scanned” without verification or attribute all period sales to the printed item. Compare versions with similar distribution conditions to make the observations useful.

5. Review privacy and keep the destination working

Google Analytics guidance prohibits sending personally identifiable information, such as email addresses or phone numbers, in page URLs or campaign parameters. Use general item and location labels, and review the fields and events sent to analytics. Tell visitors clearly what a form requests and why, and review the privacy and consent settings appropriate to your site.

If you use a redirect service or a code with an editable destination, check who owns the account and what happens when the subscription ends. Test the link while the printed items are in circulation and plan a suitable page after the offer ends. Remove the expired offer while leaving useful guidance rather than sending visitors to a missing page.