Before you start #
Availability and permissions
- Permission to view the workspace’s QR analytics.
Have these ready
- Choose a date range and reporting timezone. Add campaign and placement information to make comparisons useful.
What to do #
- Open analytics for the workspace or an individual QR code. Set dates and available code, campaign, placement, geography, device and traffic filters.
- Read the metric definitions. A redirect request is not proof of a camera scan by a person; bots, prefetches and automated traffic are classified separately.
- Review trends, busy days/hours, destinations, devices and available approximate geography. Unknown location is an honest result when approved enrichment is unavailable.
- Use estimated unique/repeat activity only with its displayed method and limitations. It does not identify a person. Purpose describes your campaign context, not the scanner’s motivation.
- Export PDF, CSV or XLSX using the same filters and cutoff. Keep reports private where campaign information is sensitive.
What to know #
No precise GPS is requested by default. Country/region/city are approximate when available, never a street-level location.
No analytics result proves a sale or conversion unless a separate supported conversion measurement actually recorded it.
What success looks like #
You can explain the report’s time range, traffic definition and limitations when sharing it.
If something goes wrong #
- No activity? Check date filters, paused status and whether the printed code uses HIVE’s managed URL. Never invent demonstration scans in customer reports.
To share a specific section, use the # link beside its heading and copy the address. To save or print this guide, use your browser’s Print command.