CLIENT AUDIT TOOL ยท STEP 74
Build a Tracking Audit Report
Upload evidence from the Guided Website Audit or add diagnostic evidence collected with permission. The tool explains each finding in plain language and suggests a possible correction service. It does not scan or crawl a website by itself.
1. Add audit evidence
Use the sample first to see how the report works. For a real client, replace the sample with evidence collected from approved website and tag tests. Do not include customer names, emails, phone numbers, order IDs, IP addresses or secret keys.
Required: website name, domain and a list of checks. Evidence type must say whether a result was observed live, tested locally or not tested.
REPORT PREVIEW
Tracking Audit Report
Not scoredLive health score
0Observed live issues
0Verified live passes
0Synthetic findings
Findings and recommended actions
Potential service work
How to use this safely
- Get permission from the website owner before testing.
- Collect evidence from Tag Assistant, browser developer tools, consent tests and the relevant platform test tools.
- Mark a result live_observed only when you actually checked the real website.
- Mark local simulations synthetic. They must never be presented as confirmed client-site faults.
- Review the report before sending it to a client. A suggested service is an opportunity to investigate, not a guaranteed sale.