How to track QR code and NFC Interactions by store

Track QR and NFC Interactions by store using a reliable mapping between each physical Touchpoint and its destination context. Give QR and NFC distinct entry identifiers where separate reporting is required. Shared codes support shared reporting; they cannot identify an individual store unless another reliable source supplies that context.

Choose the reporting scope before printing

Agree whether the team needs store, cohort, fixture or Product-level reporting. Store-specific material creates more detailed mapping work; shared cohort material can be simpler but reports at a broader scope. Decide with print production, field operations and analytics before artwork is locked.

Align store identifiers with the Retailer and the reporting team. Do not rely on a free-text branch name if other systems use a stable branch code. Record changes to store names without losing the underlying identifier.

Build a Touchpoint register

| Field | Purpose | Example format | | --- | --- | --- | | Touchpoint ID | Identify the assigned entry point | Internal stable identifier | | Retailer and market | Select approved range and destination | Retailer plus country code | | Store or cohort ID | Define location granularity | Branch code or named cohort | | Placement and fixture type | Describe physical context | Shelf rail, plinth or header | | Product identifier | Select relevant information | Approved local model code | | Entry route | Distinguish access when configured | QR or NFC | | Destination and version | Maintain the journey | Managed route and approved Experience |

These are planning fields, not a claim about mandatory MyPlayer parameter names. Map them to the actual platform and analytics schema with the implementation owner.

Test the mapping from the physical material

Open each representative printed QR and encoded NFC route using the physical proof. Verify the Product, language, Retailer destination and recorded context. Check that test Events can be excluded from live reporting using an agreed method.

For a display carrying both QR and NFC, confirm that the two routes remain distinguishable. Do not assume the analytics system can infer how a shared URL was opened. Reconcile kit labels and encoding records before dispatch, then check placement at installation.

Define access Events and Sessions

A recorded redirect, page load or NFC-origin arrival may each have a different trigger. Define the access Event before naming it “scan” or “tap”. Define the rules that group subsequent actions into a Session, and document repeat use, automated traffic and failed loads.

Do not assume anonymous means no technical identifiers are processed. Describe the actual data, purpose, retention and responsibilities using approved implementation wording. Configure any required information and choices with the responsible privacy team.

Report at the level the evidence supports

Separate stores and cohorts, entry routes and deployment periods. A universal packaging code usually lacks a unique store assignment. A link can also be shared beyond the original placement, so route metadata alone is not verified proof of a person standing in that store.

Where supported, connect entry activity to Story exploration, finder completion, comparisons and onward Retailer actions. A click to a Retailer page is observable within the journey; the later purchase needs separate evidence.

Maintain the register

Assign ownership of replacement codes, moved fixtures, updated destinations and retired Products. Keep a change log so historical reporting can be interpreted against the mapping active during the period. Investigate unexplained shifts before comparing stores or claiming an improvement.

Tracking setup checklist

• Store or cohort scope selected before production
• Stable identifiers and placement fields agreed
• QR and NFC routes distinguishable where required
• Physical proofs reconciled with the register
• Actual Event, Session and exclusion rules documented
• Data wording, change ownership and end-of-campaign routes approved

Make entry context useful for reporting

MyPlayer connects physical Touchpoints with measurable Experiences. Scope the location register, supported entry routes and reporting requirements alongside the print and field plan. Discuss QR and NFC measurement.