Consent Docs

Scan your site

Scan a property's site from the DPDP Act check to see what runs before people agree, and read the result there.

How-to2 min readFor privacy, marketing and support teams

A scan visits your site as a first-time visitor in India. It finds the cookies, storage keys and third-party hosts the site sets before and after the visitor agrees. It collects names and hosts only, never values. Scan again after each change to the site's tags.

Before you start#

  • The scan starts from the property's first site address. Add the address to the property first. See Manage properties.
  • The address must be public.
  • A region rule must serve India under the DPDP Act, so the scan visits as someone in India. See Choose regions.
  • If your site blocks automated visitors, allow the scanner. Its user agent contains PIEDAPConsentScanner/1.0.

Start a scan#

  1. Choose the property in the property picker.
  2. Open DPDP Act check in the top bar.
  3. Choose Scan your site. After the first scan, the button reads Scan again.
  4. Wait a few minutes, then open DPDP Act check again.

The console shows Scan started. The scan visits up to five pages. Only one scan runs for a project at a time.

If the console says Add your site’s address to the property first, the property has no site address yet.

What the scan does on your site

The scan opens the first site address and makes no choice, so everything present at that moment ran before consent. If your banner is shown, it presses the accept-all button. It then follows links that stay on the same site and notes what appeared only after accepting.

On each page it records cookies with their lifetime, and keys in local and session storage. It also records the other companies' servers the page contacted. Your own domain and its subdomains are not counted.

Read the result#

The results show in the DPDP Act check. Its summary says Last scanned and when. Before the first scan, it says Your site has not been scanned yet.

The before-consent check lists what ran before people agreed. Its requirement reads Nothing that needs consent runs before the person agrees.

What you see Meaning
Set before any choice was made: and a list of names These need consent and ran before the banner was answered. Bring this list to zero.
Set before any choice and not yet classified: and a list of names The product does not know what these do. If one needs consent, hold it until the person agrees.
The check under Met Only strictly necessary items ran before a choice.

Open How to fix under the check and pass it to your developer, or see hold tags until consent.

When a scan finds something the previous scan did not, your systems receive the scan.changes_detected webhook.

↑↓ to move, Enter to open