For the complete documentation index, see llms.txt. This page is also available as Markdown.

Configure tracker and vendor discovery (Classic scan)

The Didomi tracker and vendor discovery (classic scan) is a tool that enables your organization to receive a compliance evaluation for up to 10 pages of a given domain from a Didomi perspective. In this article, we will cover how to configure a tracker and vendor discovery utilizing a classic scan for a domain.

Click Tracker and Vendor Discovery on the left-hand panel and select Add Domain on the subsequent page.

Select Classic Scan in the next modal.

Use the provided fields to input the following information:

Field
Description

Give this domain a recognisable name

Internal name used to identify the domain

Target domain

URL of the domain that will be scrapped by the Didomi bot for the compliance report Example: https://demosite.com

Launched from

Select country from which the Didomi bot scans. Since the Didomi bot mimics an end-user's behavior (including the location from which the end-user accesses a domain), this field enables the Didomi bot to experience the CMP behavior targeted at end-users in a specific country.

Next, use the provided Behavior cards to select how the collected data from the classic scan is interpreted. The default scenario for the scan will depend on the behavior selected:

The behavior of the classic scan cannot be edited once the domain is saved.

Behavior
Scenario
Description

Opt-in

Accept all

For regulations where consent is required before tracking and is a best fit for compliance concerns regarding European countries and any opt-in consent implementation. Trackers that are fired before the end-user grants consent are treated as violations.

Opt-out

No actions

For regulations where tracking is enabled by default and end-users have to explicitly opt-out of tracking. A best for compliance concerns regarding U.S. privacy laws and any opt-out consent implementations.

Trackers that persist after an end-user has opted out or when a GPC signal is present are treated as violations.

Additional bot scenarios and configurations are available with the Didomi Advanced Compliance Monitoring (ACM) module.

If required, expand the Advanced tab for the following configurations.

Field

URL filter

Enables your organization to direct the bot to scrape only URLs that contain a specific string. For example, if your organization only wants to evaluate compliance on its product pages (all of which contain /products/ in the URL, input the string into the field and the Didomi bot will limit its scraping to URLs that contain /products/ Note: To use regular expression (regex) in the URL filter field, enable The URL filter is a RegEx checkbox. Click here for an overview on how to use regular expression.

N. of pages

Number of pages that the Didomi bot should scan. The maximum number of pages for tracker and vendor discovery (Classic scan) is 10 pages.

Confirm that you own the domain or acting on behalf of the domain owner to run the vendor and tracker discovery and click Save & Run when finished.

Once successfully added, Didomi will begin generating a vendor and tracker discover immediately. Your organization can always manually re-initiate a discovery.

Last updated