Common issues

Tracker source signal with no known CMP source signal

The homepage evidence referenced tracking technology without an observed consent-tool reference. This is a review trigger, not proof that tracking executed or that no consent interface exists; a banner may be injected dynamically.

Known CMP source signal

A consent-tool reference was observed. Its presence does not prove that a banner appeared, choices were equivalent, consent was valid or technologies were blocked as configured.

Pre-interaction third-party cookies

Where a result includes browser observations, read their scope and observation time. This does not determine their purpose, necessity, exemption or legal status.

Verify in a clean browser across first visit, reject, accept, granular preferences and withdrawal, and reconcile the observations with your organisation's authoritative technology, purpose, retention and legal-basis records.

Practical follow-up

Ask the responsible maintainer to identify the tool or tracker referenced by the evidence and the pages on which it operates. Check your organisation’s authoritative privacy records and obtain qualified guidance for legal decisions. Behavioural tests should use a clean browser context and cover refusal and withdrawal as well as acceptance.

Do not remove a necessary implementation solely because a discovery signal exists, or declare the Site compliant because no signal appeared. Repeat the Flowpane check after a public change, keeping its bounded scope distinct from your separate tests.