GDPR and Compliance
Netvigie Tracking is a powerful ally to help you verify that your implementation respects the GDPR and data privacy rules.
Alert on personal data collection by a third party
- Objective: Ensure that personal data (email, name, IP, etc.) are not sent to third-party partners without authorization.
- Functioning:
- Mark sensitive data: When creating a collector that retrieves personal data (e.g. a CSS collector for the email field in a form), check the "Sensitive data" box.
- Detection: During a crawl, if Netvigie Tracking detects the value returned by this collector in the parameters of a third-party tag, a "Sensitive data" type alert will be generated.
- Exception management: It is sometimes legitimate to send data (like a client ID) to a partner (like your analytics solution). In Tags > Sensitive data > Exception management, you can create a rule to authorize a specific collector to be sent to a specific tag, which will disable the alert for this specific case.
Alert on user consent non-compliance
- Objective: Verify that tags requiring consent only fire when the user has given their agreement via your cookie banner (CMP).
- Configuration:
- Create a collector that reads the consent state (usually a Cookie type collector that reads the cookie placed by your CMP). The value of this cookie indicates which partners are authorized.
- Go to Tags > Tag Management and edit the tag you want to verify (e.g. "Criteo").
- In the "Consent" box, add a consent constraint.
- The constraint will use your cookie collector. Example of rule:
{{Consent Cookie}}must containcriteo. - This means that the Criteo tag will only be considered legitimate if the value
criteois present in the consent cookie.
- Verification:
- Create a "Cookie Refusal" Crawl Mode that uses a preparatory scenario to refuse consent on your CMP.
- Launch a crawl with this mode. If the Criteo tag is detected, Netvigie Tracking will verify the consent constraint. As it will not be satisfied, a "Non-consented tag" alert will be raised.
Blacklisting a tag
- Objective: Declare that a tag must never be present on your site (or on a specific context).
- How?
- Go to Tags > Tagging Plan.
- In the table, on the row of the tag to ban and the column of the desired context (or "All contexts"), click on the
+to add a rule. - Click on the
...and select "Forbid this tag". - Save.
- If the tag is detected during a future crawl, its score will drop to 0 and an alert will be generated.