BROWSER SIGNAL REVIEW
Evidence checklist, not a detector or an ad-platform upload format.

DEFINE THE OBSERVATION
Website, route, period, time zone and source export:
Original peer address and trusted client-IP resolution policy:
Raw User-Agent value and source field:
JavaScript observation: received / absent / unknown; reason known or unknown:
Reported navigator.webdriver: true / false / not observed:
Consent, script loading, browser errors and collection scope:
Request rows versus distinct observed click identifiers:
Business-event reference and actual CRM outcome, if available:

KEEP INFERENCES SEPARATE
A chosen User-Agent value is not verified software or a physical person.
Received JavaScript is evidence of that observed execution/report, not a sale.
No JavaScript report does not establish which failure or client caused absence.
webdriver=true reports cooperating automation, which can include legitimate QA.
False/missing webdriver does not certify human identity or lead quality.
An address can be shared or reassigned; a location/network label is context.
Website observations alone do not identify billed invalid clicks or refunds.

CONTROLLED FOLLOW-UP
Reproduce on an appropriate test environment with a known test event:
Record actual source acceptance, event identity and destination/action:
Inspect tag execution, request delivery and reporting independently:
Check legitimate automation, monitoring and shared-network cases:
Specific rule or integration fix, owner, scope and rollback:
Unresolved facts and follow-up cutoff:
Use supported platform diagnostics for ad charges and actual exclusions.

LOCAL LAB RECORD
Node/Playwright/Chromium versions printed by the lab:
Same chosen User-Agent / same loopback peer observed:
HTTP request, JavaScript-enabled browser and disabled-JavaScript browser results:
The local lab does not test Google filters, production bots or visitor fraud.