Tracking requests
Which supported tools send events, what parameter names they use and whether the browser records transport errors.
Tracking Scout by ReiterWeb
Enter a domain. Scout opens the public website and checks the tracking and consent behaviour it can observe.

A browser check is a starting point for understanding the setup.
Which supported tools send events, what parameter names they use and whether the browser records transport errors.
Storage and consent signals across the choices, reloads and pages the scanner can observe.
Each finding explains the observation and what to investigate. Unavailable checks stay visible.
See the current checks and their sources in Scout’s methodology.
The browser cannot see your account settings or prove that a receiving platform recorded a conversion. Those checks need a separate scope and, where necessary, account access.
Discuss my setupNo. Scout checks the public website using only its domain.
Yes. Scout needs an email address to send your finished report. This does not subscribe you to marketing emails. You can close the page once the scan has started.
No. Available pages, consent controls and supported tracking determine what can be tested. The report shows coverage and unknown results.
Yes. Use the report’s contact link to send the reference with an enquiry. I will review the context and explain the next step.