Analytics and testing
Troubleshooting analytics data in Div-idy
When Analytics looks empty or unexpected, first confirm you tested the published page, refresh the data, and widen the filters. Then repeat one recognizable action. Check visits and events separately: they measure different things and can arrive with different browser timing.
Confirm the page and version
In Publishing, use Refresh status and open the live page you intended to measure. A private preview is not a public test visit. If your new button appears only in the draft, publish that page’s changes before expecting visitors to trigger it. Check the project and page address carefully, especially when you have several similar projects or both Home and child pages.
Remove filters that hide the visit
Open Analytics and choose Refresh data. Try All time, All devices, and empty page/source searches. Clear any minimum visit length, event search, and event-type selection. Choose Apply filters. Once you find the activity, reintroduce one filter at a time. An event cannot appear in the current result if the visit containing it has been excluded by the visit filters.
Create a small, recognizable test
Open the live page, wait several seconds, and click a clearly named button once. Return to Analytics and refresh. Search for the button’s visible or accessible label. If that works, test the missing interaction specifically. A decorative element with a custom click handler may not behave like a standard button for automatic tracking. Ask for an accessible button or link when that is the intended interaction.
Compare standalone and embedded behavior
If an embedded app has missing or inconsistent data, open the same page through its normal live link. Browser privacy settings, extensions, blocked requests, unreliable connections, or restrictions from the containing website can affect measurement. Try another ordinary browser to isolate the condition. Storage restrictions can also make browser identity less persistent. Do not treat a changed visitor count as evidence that additional real people arrived.
Explain differences before reporting a bug
Repeated visits from one browser can increase Visits without increasing Visitors. Repeated clicks increase Occurrences, while a clicked submit button may also generate a form event. Short visits can miss a final duration update; a tab left open can report a longer duration without active attention. If the problem remains reproducible, note the live page, approximate time, browser, filters, expected action, and observed result. These details make a support request much more useful.