Getting started with AuraScope Analytics

AuraScope Analytics measures pageviews from real browsers with one deferred install line, and can also observe requests that never run JavaScript through a forwarder. Choose your stack page first; it gives the exact placement and, where supported, the forwarder wiring.

Any stack not listed works the same way: put the install line in the template every page shares. Tell us which stack you run and we will validate it end to end before publishing its guide.

The managed proxy is decided and in build. At onboarding we give you a managed-proxy hostname such as <label>.<your-domain>, name one CNAME record, and tell you when it is active. There is no self-serve dashboard yet. If your Content Security Policy must remain same-origin, stack pages show the permanent /px/t.js rewrite alternative.

What we collect

• The browser install line measures pageviews, not people. It sets no cookies, stores no local identity, and does not track across sites.
• Visitor counting uses a salted daily hash that cannot be reversed or joined across days.
• A forwarder records compact request metadata needed to identify crawlers: method, path including the query string, user-agent, and address evidence. It does not read request or response bodies. Query strings are sanitised centrally with per-parameter accounting, so a redaction improvement does not require a redeploy.
• Crawler fetches are requests, never pageviews. AI-referral counts are always at least the displayed number.

Bots are invisible by construction. The install line only runs where JavaScript runs and contains no user-agent detection. Non-browser fetches never execute it, which is a stronger guarantee than filtering.

Every verdict is backed by evidence, and counts are never inflated by our own monitoring traffic.

How we check the install line

The install line is a deferred script sourcing /px/t.js with your data-site, anywhere in the document. When we check your install, we parse the rendered page rather than pattern-match its text, so templating frameworks, attribute reordering, and minifiers are fine. There is no self-serve check yet; we complete this check with you during onboarding.

What it cannot do to your site

The install line is deferred and the beacon is fail-open. Forwarders observe without blocking or changing requests, then queue and ship outside the response path. If our service is unavailable, your site continues as it did before; measurement may wait in a durable queue or, only at capacity exhaustion, be lost with that loss counted.

The first-party path is not a way around anyone’s browser settings. Ad blockers can still prevent browser measurement, and that loss is disclosed rather than hidden.

Continue with your stack page, then use Verify your install when its steps are complete.