Skip to main content

⚖️ Comparisons & normalisation

Compare performance across locations fairly. This page shows what you can compare, how to normalise results, and how to read the output.

Leo avatar
Written by Leo
Updated over 5 months ago

What you can compare

  • Camera metrics: Total People, Entries, Exits, zone totals

  • Kiosk metrics: Sessions, Meaningful sessions, Conversion rate, Total content viewed

  • Mixed context: filter by Experience, Campaigns, Countries, Locations, Deployment Type

Default charts use raw values per kiosk or per camera.

Normalisation methods

Normalisation is available on demand. Use it when store sizes or opening hours differ.

Per open hour

rate_per_hour = total_value ÷ open_hours_in_range

Use for fair day-to-day comparisons when stores have different trading hours.

Per m² (floor area)

rate_per_m2 = total_value ÷ floor_area_m2

Use when stores vary in size and you want density rather than absolute totals.

Per staff on duty

rate_per_staff = total_value ÷ avg_staff_on_duty

Use for labour productivity views. Provide average staff numbers for the period.

Notes

  • Kiosk Engagement Rate is already a ratio and usually does not require extra normalisation.

  • Provide open hours, floor area, and staff counts for each location to enable these views.

How to run a comparison

  1. Open Analytics and set Time Range.

  2. Select Countries and Locations to include.

  3. Pick Deployment Type: Camera or Kiosk.

  4. (Optional) Select Experience and Campaigns for a focused view.

  5. Toggle a normalisation method if provided for your tenant.

  6. Review the ranked table and charts. Click a row to drill into the store.

Interpreting results

  • High footfall, low kiosk KPIs: strong attraction near the kiosk but weak pickup. Improve on-screen CTA or placement.

  • Low footfall, high kiosk conversion: good kiosk experience but quiet zone. Consider signage or relocation.

  • Per-hour spikes: align with Busiest time to staff correctly.

Best practices

  • Keep the same time window when comparing periods.

  • Use per hour for mixed trading hours, per m² for size differences, per staff for productivity.

  • Pair camera totals with kiosk metrics to spot attraction vs interaction gaps.

Limitations

  • Cameras do not backfill when offline: gaps appear as lower totals.

  • Normalisation requires store metadata: open hours, floor area, staff counts.

  • Analytics time is UTC. Campaign scheduling uses London time.

Permissions

  • Admins: global access across countries.

  • Managers and Viewers: scoped to assigned countries. Results are automatically filtered.

Did this answer your question?