Troubleshooting

• Check the key: the data-keyin your page must be the tracking key from this site's Settings, Installation. A key from another site writes to that other site.
• Check the HTML actually served: a caching layer or CDN can serve pages from before you added the tag. View source in the browser and search for oa.js; purge caches if it is missing.
• Check the origin allowlist: if your site has domains configured in Settings, events are accepted only from those hosts. Testing from staging or localhost? Add that host, or use an empty list while installing.
• Verify on the realtime view, not the charts: it shows a visit within seconds. Add data-debug="true" temporarily and the browser console reports any transport failure.

• Privacy-signal visitors are absent by design: someone sending GPC or DNT is not measured at all, while cookie-based tools count them. Respecting the opt-out is the product working.
• Bots are filtered before billing and before charts.
• Visitors here means people, counted with a daily identifier: a tool that counts cookie lifetimes or device installs will read higher on the same traffic.

The one way to double-bill a click is describing it twice yourself under the same name with two mechanisms: a data-oa-event attribute plus an oa.track() call of the same name on the same element. Pick one. A dashboard rule with the same name is safe; the rule wins and exactly one event fires. Details on the custom events page.

Use data-test-mode="true" on staging and local environments: that traffic never bills and never appears in charts. There is no per-person exclusion cookie, because the product does not recognise people; excluding an environment is the honest version.