How to measure touchscreen Sessions and module depth

Measure touchscreen use by defining how activity starts, ends and groups into Sessions, then recording the supported actions inside each module. Keep Device communication status separate from Shopper activity. A Session represents activity under those rules, not necessarily one distinct Shopper, and playback alone does not establish attention.

Define the Session before comparing stores

A shared retail screen can serve multiple people, store demonstrations and assisted conversations. A browser or Device identifier cannot by itself tell you how many people used it. Agree the reporting rules with the Product and data owners before the launch scorecard is finalised.

| Definition | Decision to document | | --- | --- | | Session start | The implemented Event or condition that begins activity | | Session end | Timeout, explicit reset or other supported termination rule | | Inactivity | What counts as activity and how reading or playback is handled | | Reset | Which selections clear and whether a new Session starts | | Exclusions | Tests, known demonstrations, automated and system Events | | Reporting scope | Device, Touchpoint, store, trading period and content version |

Use the configured, approved values. Do not introduce a separate “qualified Session” threshold unless its purpose and rule have been formally agreed. Report definition changes with the affected date so apparent trends are not confused with methodology changes.

Map Events to the Shopper task

Create an Event inventory with the Experience designer and analytics team. Include only actions the implementation actually records. A planning label such as “comparison opened” should not be presented as a production Event name until it is mapped to the real taxonomy.

| Module | Useful behaviour to record if supported | Interpretation limit | | --- | --- | --- | | Story | Start, eligible card view, navigation, completion | A card view does not prove understanding | | Product Finder | Start, answer, result, no-match outcome | Answers describe participants, not all store visitors | | Product Comparison | Open, selected models, onward selection | Comparison is not confirmed preference | | Video | Selection and supported playback milestones | Playback is not verified human attention | | Continuation | Retailer click or supported QR access | A link action is not a completed purchase |

Calculate depth on a consistent basis

Use a defined measure such as eligible Sessions opening a comparison divided by eligible Sessions in the same period. State whether the numerator counts each Session once. For finder completion, define the start and result conditions, then divide eligible completed starts by eligible starts.

In an illustrative example, 12 completed eligible finder starts from 15 eligible starts gives an 80% completion rate. This is arithmetic, not a MyPlayer benchmark. Counts, percentages and the observation window should appear together.

Describe Session duration as elapsed or active time according to the implemented rule. Do not rename it Attention Time without an approved measurement definition.

Keep operational and Shopper reporting separate

A Device heartbeat indicates communication under a defined freshness rule. It does not verify screen visibility, correct physical placement or a person’s presence. A disconnected Device may still play cached content if that configuration supports it.

Report Device availability and Interaction activity side by side. If comparing activity per active Device-day, define an active day and also show planned Device-days so unavailable locations remain visible. Test offline playback and Event recovery separately; do not assume either.

Handle assisted use and mobile continuation carefully

Long Sessions or repeated specification views do not reliably identify staff assistance. Use an agreed method if assisted use must be distinguished, or state that the data combines uses.

Where a tested QR handoff carries Session context, report the supported linkage. Without it, report screen activity and mobile entries separately. Neither method establishes a distinct person across devices by itself.

Measurement setup checklist

• Session and inactivity rules signed off by Product and data owners
• Actual Event names mapped to supported module actions
• Reset, reading, replay and offline cases tested
• Test traffic and repeated Events handled consistently
• Rates include denominators, period and exclusions
• Device state, Interaction and sales outcomes reported separately

Plan measurement with the Experience

MyPlayer’s Interaction analytics can help explain what people explore before the sale. Confirm the supported Events and reporting definitions for your proposed Deployment before agreeing external metrics. Discuss touchscreen measurement.