Documentation

Analytics that answer page questions

Read visits, visitors, CTR, sources, devices, countries and campaign data without chasing vanity metrics.

Last reviewed 24 July 2026

Analytics are useful when they change a decision. OrbitPage separates page traffic from the marketing-site analytics used by OrbitPage itself, so tenant visits belong to the tenant workspace.

Core metrics

Visits, visitors and clicks describe different behavior.

A visit represents a session on the public page; a visitor is an estimated distinct audience member; a click records an interaction with a tracked destination. CTR relates clicks to the available traffic, but its meaning changes with page structure.

No analytics system identifies every person perfectly. Privacy controls, blocked scripts and device changes create normal differences between tools.

Context

Sources, devices and countries explain where a result came from.

Source and UTM reports help compare campaigns. Device information helps diagnose layouts. Country data is approximate and should be used for broad patterns, not individual identification.

Use time ranges long enough to avoid drawing conclusions from a handful of visits.

Decisions

Ask a question before opening the report.

Compare two event campaigns, decide which action belongs first, or check whether mobile visitors abandon a media-heavy page. A dashboard without a question becomes a collection of numbers.

Keep campaign naming consistent. A small set of deliberate UTM values is easier to interpret than a different naming style in every post.

External analytics

Connect GA4 only when the additional ecosystem is useful.

Supported plans can add a tenant-owned Google Analytics tag. That tag belongs to the page owner and is distinct from OrbitPage's own marketing-site measurement.

The page owner remains responsible for consent, disclosure and configuration required by the regions in which the page operates.