Analytics and testing
How analytics session tracking works
Div-idy records visits and supported interactions on published pages. Analytics distinguishes recorded sessions from estimated unique browsers. Time on page is an elapsed-time measurement, and events describe recorded actions; neither metric proves that a person completed your business goal.
Open the project’s analytics
Open your project’s Analytics tool and choose Refresh data. Start with an appropriate Date range, then choose Apply filters. The overview shows Visits, Visitors, Average visit, and Events. Use a live page for a test visit. Interactions in the private editor preview do not represent ordinary published-page traffic.
Distinguish visits from people
Visits counts recorded sessions. A fresh page load can create another visit; refreshing repeatedly does not necessarily mean more people arrived. Visitors estimates unique browsers using an anonymous browser identifier. One person using two browsers can appear as two visitors. Clearing storage, private browsing, or restricted embedded storage can also affect continuity. Treat the number as a browser estimate rather than a count of identified customers.
Interpret recorded time on page
The published runtime sends an initial visit update shortly after loading, periodic updates while the page remains open, and a final update when it leaves where the browser permits. Average visit summarizes recorded elapsed time. It is not an attention score: a tab left open can accumulate time, and a browser that closes abruptly may miss its final update. Compare time alongside relevant actions and actual user feedback.
Read the selected audience
Filter by dates and device, or expand the filters for Page path, Traffic source, and Minimum visit length. Events are examined within the selected visits. Changing an event search changes the actions shown without redefining the whole audience as converters. A source may be a referring site, a campaign source from the link, or Direct / unknown when no usable source was recorded.
Check a visit you can explain
Open a published calculator, keep it open briefly, and press its clearly labeled calculation button. Return to Analytics, refresh, and use a date range that includes the test. Look for the page and button activity. Record what you did so you can interpret the result without expecting an exact person count. Your own live-page tests can contribute data, so separate test activity from evidence about a real audience.