Guides
How to set up journeys, integrations and checks in AnalyticsProof, and how to read their results.
Working with journeys
How to record a journey that replays reliably
How to record a website journey so the scanner replays it the same way on every scan. Cookie banner, step types, waits, fragile steps and the journey limit.
The expected state and how to read a diff
How a journey's expected state is built, what a scan compares and what it does not, what each change type means, and why a person must review the first one.
Broken steps and selector fixes
What the step outcomes after a journey replay mean, why the replay never clicks a covered element, and how to review a proposed selector fix.
Integrations
The GitHub pull request check
Connecting GitHub to a test, where the preview URL comes from, letting the scanner past a password or allowlist, and what the pull request check reports.
CI/CD with the API
Run a journey against a preview from any CI, wait for the result, design the gate and get SARIF. Plus when the GitHub App or the ready-made action is enough.
Platforms
Testing Android apps
Which file to upload, what the scanner does to your app, what it sees with certificate pinning and integrity checks, and how to record an in-app journey.
Reference
How the compliance score works
Which criteria make up a website scan's technical score, why its base is not always 100 points, how it differs from the verdict, and when there is no score.
Which tools the scanner detects
The analytics and advertising tools and consent platforms a website scan recognises, how it recognises them, and what happens when yours is missing.