Service Scout is the service-discovery feature in QookieQloud. It helps you find existing analytics and marketing services and prepare their base installations for loading through your consent banner.
How to use Service Scout
- Open your domain’s banner customizer and select Services. Start the website scan using the scan button. The feature name may not yet appear in the interface.
- Review the detected services, their IDs and “Show source” evidence. Each result indicates whether its ID was found before or after confirmed consent. An observed ID is not, by itself, proof that tracking took place.
- Select the services you want to add. Existing QookieQloud entries are marked as already added. Back up the current installation before making changes.
- Remove the matching base installation from your page code, theme, plugin or platform settings. For GTM, include the noscript snippet. Service Scout does not remove website code for you.
- If GTM is present, review the container’s consent settings and whether it already loads the selected services. Avoid loading a service both directly and through GTM.
- Confirm that you removed the old base installations and, where required, reviewed GTM. Activate the selected services. Publish any website changes, then test before a choice, after rejection and after acceptance.
What the scan checks
The scanner visits your domain’s home page in two separate browser sessions: before a choice and with an attempted acceptance using the V3 consent-clicking engine. If acceptance cannot be confirmed, only initial-state findings are included. An unidentified dialog or incomplete result does not establish that no other services exist. Services on other pages may need to be added manually.
Supported services
Supported IDs can be discovered for: Google Analytics 4, Google Tag Manager, Meta Pixel, Google tag, Google Ads, LinkedIn Insight, Hotjar, Microsoft Clarity, Segment, Matomo, HubSpot, Fathom Analytics. Matomo also requires its tracker URL; HubSpot results include the detected region. Activation requires an available QookieQloud loader for the service.
Keep events and consent settings in view
Only the base installation is added. Purchase events, conversions and custom events need separate review and adjustment. In strict mode, services load after consent to their category. With Google Consent Mode, Google tags may load before consent with denied signals; GTM tags still need correct consent settings.
A completed discovery scan does not verify the migration. Check for duplicate requests and confirm that your events reach the relevant service after the move. Results older than seven days must be scanned again before activation.
