Point the telescope at any URL. Beacon Inspector maps every analytics vendor, tracking pixel, and tag manager — then the Auditor plots your mission.
The Debugger is your telescope. The Auditor is your mission control.
CDP Inspector scans the page you submit, then uses an AI model to analyze, interpret, and surface insights from what it finds. Here's how that works and what you should know.
When you run an inspection, CDP Inspector scans the page's own HTML for known tracking patterns to detect the vendors in use. That scan runs directly against the page and is not sent to a third party. The written analysis is generated by an AI model through Base44's built-in AI integration, which evaluates the vendors detected in the scan against known data schemas, common configuration patterns, and data quality best practices.
The analysis provided by CDP Inspector is generated by a large language model (LLM) and is offered on an "as-is" basis. While we work to surface accurate, actionable results, LLM outputs can occasionally be incomplete, imprecise, or incorrect. CDP Inspector is a debugging and auditing aid — not a guarantee of implementation correctness. You should independently verify any findings before making changes to your production environment.
The page URL and the vendors detected in the scan are sent to the AI model to generate the analysis. CDP Inspector does not store your event data beyond the duration of your active session unless explicitly stated otherwise.
Nothing provided by CDP Inspector constitutes legal, technical, or professional consulting advice. Use of this tool does not create a client-advisor relationship of any kind.