Site Analytics
Site Analytics troubleshooting
Diagnose collection, origin, CSP, duplication, and goal-matching problems.
Start with the browser Network panel and Optimly's installation health. Do not debug by adding extra payload fields or logging visitor data.
No events arrive
- Confirm the production page contains exactly one Optimly snippet.
- Confirm the script request succeeds.
- Confirm the configuration request uses the expected public site key and browser origin.
- Check CSP
script-srcandconnect-src. - Check that the Site Insights site is not disabled.
- Verify the exact configured scheme, hostname, and port.
HTTP responses
| Status | Meaning | Next action |
|---|---|---|
202 | Event accepted; inspect accepted and duplicate | Continue to goal matching if needed |
400 | Invalid key, configuration request, or event schema | Copy the canonical snippet and remove custom payload fields |
403 | Origin not authorized or collection disabled | Correct the allowed origin or site state |
429 | Bounded collector rate exceeded | Stop synthetic loops and retry after the window |
Data arrives but a goal stays at zero
- Confirm the goal is active for the event time.
- Confirm the tested path, hostname, destination, form key, or event type matches the rule.
- Remember that
link_clickandform_submitare engagement signals unless a stronger success signal
is also observed.
- Confirm test traffic is not being compared with live reporting.
Unexpected duplicates
Search the shared layout, tag manager, page embeds, and platform custom-code areas for another copy of the snippet. Do not install a route-level copy in a single-page application.