Analytics and privacy
Configure visitor consent under Privacy and read reports under Analytics. Built-in reports and optional GA4 help you understand visits, clicks and campaign traffic.
Built-in analytics
| Report | Details |
|---|---|
| Period | Choose an available reporting window and compare it with the previous period |
| Traffic | Separate visitor, visit and card-click metrics, with interactive line and bar charts |
| Duration | Estimated visible time per measured visit; hidden tabs and withdrawn consent stop collection |
| AI discovery | Recognized AI referrers and UTM tags, with AI-search sources shown separately |
| Acquisition | Tagged campaigns and QR visits |
| Audience | Device breakdown; country data only when supplied by the infrastructure |
Dashboard activity is excluded. New pages have no historical data. A click count and a visitor count measure different actions; browser blockers, consent and reporting delays can affect totals.
OrbitPage manages reporting for the selected workspace. The plan controls available detail and 7-, 30- or 90-day reporting windows; check Plan for the current allowance.
- Visit details require analytics consent.
- Click totals work without consent, with no visitor identifier, referrer, device, or campaign attached.
- Raw IP addresses and user-agent strings are not stored.
Duration appears only for new consented visits and cannot be reconstructed for historical rows. It is capped at four hours per page session and requires browser session storage. Visits are deduplicated within the same tab, page and query. Country data comes from the trusted hosting infrastructure; missing countries stay unknown.
AI discovery is a referrer/tag estimate, not a count of search prompts, AI answers or crawler reads. Untagged visits cannot reliably be identified. The table below the charts exposes the plotted values.
Campaign and QR traffic
Use tagged campaign links and QR codes from Publish to distinguish placements. QR reporting counts consented visits when the destination loads, not camera scans. Newly generated QR codes include a campaign marker; regenerate older codes without it to distinguish their traffic.
Google Analytics 4
- Configure privacy/cookie policies and consent behavior in Privacy.
- Enter the GA4 Measurement ID, such as
G-XXXXXXXXXX, in Analytics. - Use a fresh browser session to test accepting and rejecting analytics.
The tag runs on public pages only and follows Google Consent Mode. It does not replace your privacy policy.
Consent providers
Use the built-in controls or configure iubenda, CookieYes, Cookiebot, OneTrust or a custom CMP. The consent-management guide explains the fields, category mappings and public-page checks. Avoid installing the same analytics tag in both OrbitPage and custom scripts or a tag manager.
Privacy changes require the workspace's Privacy editing permission. Only use trusted provider snippets. Review imported settings and test consent on the public page after restoring a backup. See Team and permissions.
Consent settings do not control search indexing. Use the page's indexing controls.
