Start by identifying which result is missing: a browser event, an edge event, a raw log row, or a daily chart value. These checks happen at different stages, and a fix for one stage may not affect another.
New events are absent from charts#
Consolidated reporting normally ends on the previous calendar day. Today's requests can be received before they appear in charts. Open Analytics → Agent logs for the selected site to inspect its latest 100 edge events.
Agent logs is a recent diagnostic view filtered to the site's current host scope, not a complete raw-event archive. It does not list every browser event. For an external browser embed, inspect the browser's network requests as well.
During onboarding, Record your first visit checks received event data before chart consolidation. Confirm the setup step and the dashboard separately; do not promise an exact chart refresh time based on the first-event check.
No edge events arrive#
For a Cloudflare integration, confirm:
- The hostname's DNS record is proxied through Cloudflare.
- A Worker Route matches the actual hostname, including apex or
wwwas needed. - The Worker runs when you visit the page, using Cloudflare's live logs.
RAILS_URLishttps://app.answer.cloud/analytics/cloudflare_event.- The saved
SHARED_SECRETmatches the onboarding value. - The requested host belongs to the intended Answer Cloud organization.
A workers.dev URL alone does not observe the site's traffic. A normal website response also does not prove the background analytics request succeeded. A 401 indicates an authentication mismatch; do not paste the secret into a support ticket.
Browser events are absent#
Check script loading, settings order, the organization/site target, browser errors, blockers, and consent behavior. analytics.enabled: false disables events; analytics.tracking: false separately controls session/first-touch state. A hosted site uses generated settings, so inspect its plan and supported configuration rather than installing a second script.
Counts look too high or too low#
Check for duplicate embeds, overlapping browser and edge collection, a recently changed hostname, and a different reporting range. Request/page-view counts are not unique people. AI referrals are part of human views, and chat answers are separate from traffic totals.
Edge ingestion keeps successful GET requests with a 2xx or 304 response. Common assets and analytics beacons are excluded from rollups. Host allowlists, aliases, and configured path exclusions can also affect reports. A test on an unrelated subdomain may not count toward the site you are viewing.
Escalate with useful evidence#
Record the site slug, public hostname, approximate time and timezone, expected event type, route or installation method, and response status. Include a request ID when available. Keep credentials, private conversation content, and full browser storage out of shared diagnostics.
See Worker installation, collection differences, and support.