Launch measurement scorecard for in-store Experiences

An in-store launch scorecard should separate Deployment evidence, recorded Experience activity, Product exploration and onward actions. Agree each metric’s source, definition, scope and owner before go-live. Review operational issues early, then interpret Interaction patterns alongside stock and sales context without treating Sessions or clicks as purchases.

Agree the question and reporting scope

Choose the decisions the scorecard must support: launch readiness, support priorities, useful Product information or a later rollout decision. Record the Retailer, markets, planned stores, Touchpoint formats and date window. Confirm which measures are available in the proposed configuration.

The Brand and Retailer agree the commercial question, the deployment owner supplies installation and status evidence, and the Product and data owners approve reporting definitions. Keep metrics needing further definition out of external performance claims.

Copy this scorecard structure

| Area | Measure | Definition to complete | Source and owner | Action | | --- | --- | --- | --- | --- | | Deployment | Verified installed locations | Locations meeting the agreed evidence requirement / planned locations in scope | Installation evidence; deployment owner | Investigate incomplete installations | | Device communication | Communicating Devices where applicable | Defined communication freshness and reporting window | Device telemetry; support owner | Check communication exceptions | | Recorded activity | Sessions by entry format | Approved start, end and exclusion rules | Analytics; data owner | Review activity with trading context | | Product exploration | Supported comparison or finder use | Defined Event and eligible denominator | Experience analytics; Product owner | Improve unanswered questions | | Onward action | Retailer click-out or supported handoff | Defined action count or eligible Session rate | Tested journey analytics; Experience owner | Check destination and next-step usefulness | | Commercial context | Sales and stock information | Retailer-provided scope and definitions | Retailer or account owner | Interpret alongside Interactions |

The table is a reporting template, not a claim that every field is automatically available. Complete the definitions and remove measures unsupported by the Deployment.

Define rates before populating results

For a finder completion rate, define an eligible start and a completed result, then calculate completed eligible starts divided by eligible starts. For a Session-based onward-action rate, count eligible Sessions with at least one qualifying action divided by eligible Sessions. Do not divide total clicks by Sessions and label it the same rate if repeat clicks are possible.

Report the numerator, denominator and period with the percentage. Use the same definitions when comparing stores or periods. Distinguish QR access Events from QR-origin Sessions, and keep each format visible rather than combining unlike counts.

Separate operational checks from performance interpretation

During launch, verify placement and destinations and follow up reporting exceptions. Choose review frequency according to campaign risk and support arrangements. A zero-activity location warrants investigation; it is not automatically an installation failure.

Once sufficient comparable data is available, review which Products and modules participants explored. Do not require every question to wait until day 30, or present a short, sparse sample as an established trend. Keep dates and observation windows clear.

Include the limitations that change the conclusion

Sessions do not identify distinct Shoppers. Online status does not establish physical compliance. A shared code may support only cohort-level reporting. A selected comparison or finder result does not prove purchase intent.

Sales can be reviewed alongside Interactions, with stock, price, placement and promotion context. Avoid claiming incremental sales without a suitable evaluation design. Describe the actual data and privacy configuration using approved wording rather than assuming all analytics are anonymous or exempt from review.

Scorecard setup checklist

• Decisions, scope and reporting periods agreed
• Each measure has a source, definition and owner
• Availability confirmed against the actual implementation
• Rates have valid denominators and repeat-use rules
• Deployment, Device status, Interactions and sales kept distinct
• Review actions and escalation responsibilities assigned

Define useful reporting before go-live

MyPlayer helps make parts of the physical shopping journey observable through Interaction. Scope the scorecard around the supported Experience and the decisions your retail team needs to make. Discuss your launch scorecard.