STEP 75 · MANUAL EVIDENCE COLLECTION

Guided Website Tracking Audit

Use this checklist to record what you personally verify on a client website. It is designed for a non-coder operator. It does not crawl the website, inspect accounts automatically, send events or change tags.

Audit boundary: This checklist covers basic page access, consent behaviour and tracking diagnostics. It is not an SEO audit, legal compliance review or ad-account performance audit. Test purchases, refunds and provider test events require separate written authorisation and an approved test environment.

1. Website and audit details

Client or website label

Website domain onlyDo not include https://, page paths, email addresses or tracking IDs.

Auditor name or team label (optional)

Audit date

Approved audit scope

Permission record reference (optional)Enter a file label only. Do not upload or paste the permission letter.

I confirm written permission is on file from the website owner.The permission covers the checks I will perform, the test environment and any approved test actions. This is my attestation, not an independent verification by this tool.

2. Record each check

For each item, choose Pass, Issue found, Not tested or Not applicable. Pass and Issue found require an evidence method and a reference such as a screenshot filename. Not applicable requires a reason. Do not enter customer names, emails, phone numbers, order IDs, IP addresses, event IDs, payloads or credentials.

3. Validate and export evidence

The JSON file can be imported into the Client Audit Report builder. Only Pass or Issue found answers with an evidence method and reference are labelled live-observed. Not tested items stay unverified. Not applicable items are retained in the checklist summary and excluded from issue scoring.

Open report builder

All answers stay in this browser tab until you download the JSON. This page does not save data to a server or browser storage.