Measure visits, clicks and campaign sources from the page
Measure public visits, clicks, click-through rate, traffic sources and tagged campaigns from the managed OrbitPage workspace.
Last reviewed 5 August 2026Page analytics are most useful when they answer a small operational question: which campaign brought visitors, which action they opened and whether the page structure made the next step clear.
Read visits and clicks together.
A visit shows that the public page was reached. A click shows which destination or action attracted attention. Click-through rate relates those signals, but it should be read alongside the job of the page and the visibility of each block.
A lower-positioned contact link cannot be compared fairly with a primary booking action without considering hierarchy and intent. Analytics guide a review; they do not explain the visitor’s motivation by themselves.
Use tagged URLs to separate channels and creative variants.
UTM parameters can distinguish a profile, newsletter, QR code, partner or individual campaign while keeping one durable public page. Use a consistent naming convention before publishing links so the reports remain readable.
Change one meaningful variable at a time when possible. If the page order, offer and traffic source all change together, the resulting click pattern will be difficult to interpret.
Keep platform analytics and optional external analytics distinct.
Managed page analytics provide aggregate signals for the workspace. Optional external analytics, when configured, follow their own consent, retention and provider rules.
Collect only the measurement needed for a decision and keep privacy information consistent with the tools that are actually active. A larger dataset is not automatically a more useful one.
Turn the report into one deliberate edit.
Move the primary action only when the page’s goal supports it. Rewrite a label when it does not describe the destination. Retire expired campaigns so current sources remain understandable.
Review changes over a comparable period and preserve enough history to avoid reacting to a single unusual day. The aim is a clearer visitor path, not a permanently rising counter.
