Analytics and testing
How to track events in Div-idy Analytics
Published Div-idy apps automatically record supported actions, including button clicks, link clicks, form submissions, AI interactions, database actions, and recognized ad clicks. Open Analytics and use What people do to inspect these events. You do not need to add a tracking script for ordinary supported controls.
Give controls meaningful names
Use clear button and link text in your app so recorded events are recognizable. For example, ask the builder for a button labeled “Calculate delivery cost” instead of several unrelated buttons labeled “Go.” Button labels can come from their accessible name or visible text; link labels can include the destination. Keep names free of personal information and use distinct names for actions you want to compare.
Test the published interaction
Publish the page and use its live version. Click a button, follow a link, or submit an actual form to test the corresponding action. Supported AI and database operations can also produce events. A visually clickable card is not necessarily a standard button or link; if an expected click is missing, ask the builder to use an accessible button or link for that control and test the published update.
Find events in Analytics
- Open Analytics and choose Refresh data.
- Set the date and page filters to include your test visit.
- Under What people do, search the event or button name.
- Choose an event type and sort by activity, visitors, recency, or name.
- Expand an event to inspect its pages.
Use the page breakdown when the same button label appears across several screens.
Interpret occurrences and reach
Occurrences counts repeated actions. Visitors counts estimated browsers that triggered the event, and Visitor reach is their share of visitors in the selected visits. If one browser presses Calculate five times, that can produce five occurrences from one visitor. A submit button and its form may generate separate click and submission events, so adding every event together does not produce a count of completed tasks.
Check the outcome separately
A form submission event records the action, not proof that its data was successfully saved. An AI interaction does not establish that the answer satisfied the user. Verify your app’s success message and saved records when the outcome matters. For a quote request, compare recorded submissions with the records visible in Database. Use the Analytics assistant to explain the selected data, then review its reasoning against the numbers and these measurement limits.