Checking AuraScope Analytics

Use the checks in your stack or component guide first. They match the part you installed; this page explains the shared browser and onboarding checks.

Browser measurement

  1. Open a page with browser developer tools on the Network tab.
  2. Confirm t.js loads with 200.
  3. Confirm the beacon request is /px/e and its response is 204. The browser never sees 202 on this path.
  4. Navigate to another pathname and expect one more /px/e request. A query-string or in-page-anchor-only change does not make a new pageview.

The browser can receive 204 even if a relay is misconfigured, because measurement is fail-open. After these checks, ask us to confirm that your test pageviews were durably stored. There is no self-serve confirmation surface yet.

Forwarders

Forwarder guides name their local signal: a queue draining, a healthy metrics snapshot, or worker logs. A buffered forwarder can receive 202 only for its own shipment; that is distinct from the browser beacon above. We confirm durable receipt during onboarding.

Express interest

AuraScope Analytics is pre-launch. Email us and we'll write back.

nic@aurascope.co
Starter message
Hi Nic,

I run [property] in [town or city].

I'd like to know more about AuraScope Analytics — in particular [what you'd like to know].

You can reach me at [phone or email].

[Your name]