See what visitors do

Open Activity to review your creator page, forms and published tools. Choose seven or thirty UTC days, then choose the asset you want to understand. Use its daily chart and table to compare activity within that window.

What each number means#

Page and form loads count eligible requests to open a public page. Reloading can count again. A page load does not establish that a person clicked a shared link on YouTube, Instagram or another app. Source labels on forms come from valid Ready campaign-plan tags, not verified social referrers.

Page-link clicks are reported activations of the links, form cards, banner and section buttons on your published creator page. The actual link keeps its normal destination. A blocked or failed analytics request does not stop navigation. A checkout-link click does not establish a purchase.

Saved form submissions come from retained answers in the selected window. Reviewed and actioned counts describe those answers' current review state. They do not describe when a review happened. A response replay does not create a second saved answer. Responses per recorded load is an aggregate ratio; it can exceed one and is not a person-level conversion rate.

Tool loads count eligible opens of a specific published tool version. A result interaction means the browser reported its first valid result after the visitor changed an input. The automatic starting result is excluded. This is one interaction per page instance, not a unique person or a verified completed task.

Tool copy and download counts describe reported local requests. They do not prove clipboard persistence, a completed file download, an external PDF read or a sale. Visitor-entered numbers and calculated results are not sent with these events.

Keep versions meaningful#

Tool versions keep separate measurements because their methods can differ. The report shows whether a version is currently available. Withdrawal or archive prevents further eligible public measurement for that version.

Page actions are identified by their placement, label and destination. Changing a destination creates a different measured action. Counts that no longer match a current action remain labelled as earlier page configuration, rather than being assigned to a new link. Historical destinations are not stored in the event table.

Coverage and privacy#

Click and tool measurement starts when this collection feature is enabled. Earlier days are shown as before measurement; historical events are not invented. Existing page/form load measurement has its own start time. Activity before either start cannot be reconstructed.

Analytics is best effort. Browser blocking, offline use, privacy preferences, expired event tokens, request limits, storage limits and recognizable bots can affect coverage. Owner, administrator and marked test activity are excluded. Do Not Track and Global Privacy Control are respected. Counters can still be replayed or influenced by traffic; use them to investigate behavior, not as a financial ledger.

The event table retains bounded daily counts for up to thirty-one days, with bounded cleanup batches. It contains asset identifiers, version/action hashes, dates and fixed counters. It does not retain visitor identities, raw URLs, referrers, IPs, user agents, answers, entered numbers or calculated results. Short-lived rate counters use fixed system, owner and asset identifiers. No analytics cookie or tracking pixel is added.

A limited, paused or unavailable collection status is a reason to treat the report as incomplete. A zero means no eligible event was recorded for that measured period. It does not prove that nobody visited. Counts across assets do not identify the same people or create a complete journey from page to purchase.

Create a useful tool · Read form responses · Create your page