How Tailor honors visitor cookie consent

Configure your consent provider

Consent gating applies only to domains where your consent provider is configured in Tailor. In the dashboard, go to:

For each domain, select the consent management platform it uses. Tailor reads consent from the following platforms:

• OneTrust
• Cookiebot
• Usercentrics
• CookieScript
• CookieYes
• HubSpot

No additional tags or snippets are required. If a domain has no consent provider configured in Tailor, consent gating does not apply on that domain, and Tailor follows the browser's standard cookie behavior.

If your consent provider is not listed, contact us. We can add support for additional providers quickly on request.

Loading the Tailor script before consent

Tailor evaluates consent at runtime and does not identify or measure a visitor until consent is present. Because of this, the Tailor script can be loaded before consent is collected. You do not need to block or consent-gate the Tailor tag itself: the script loads, but it does not track or identify an individual visitor until that visitor grants consent through your CMP.

How Tailor classifies consent

For each visit, Tailor evaluates whether the visitor has granted consent to be tracked. It reads the consent categories recorded by your CMP and treats consent to either analytics / performance cookies or marketing / advertising / targeting cookies as consent to track. Each platform labels these categories differently, so Tailor maps each platform's categories to these two groups.

• Consent granted: Tailor identifies and measures the visit, and the visit counts toward your experiment results.
• Consent declined, not yet given, or unreadable: Tailor does not track the visit, and the visit does not count toward your results.

When consent is unknown, Tailor does not track

Where a consent state is absent or cannot be determined, Tailor does not track the visit. This applies in the following cases:

• The CMP has not finished loading. Tailor does not track the visit until the consent state is available.
• The visitor has not yet responded to the consent banner. Tailor does not track the visit until consent is recorded.
• The consent state cannot be read or returns an error. Tailor does not track the visit.
• A consent provider is configured for the domain, but its banner does not load. Tailor does not track the visit and flags the condition for our team.

Region-specific consent requirements

Some consent providers apply only in specific regions. When the CMP indicates that a visitor is outside the region where consent is required, Tailor measures the visit, because the provider does not require consent for that visitor.

Responding to consent changes during a session

Tailor re-evaluates consent if it changes during a session. If a visitor grants consent after initially declining or ignoring the banner, Tailor begins tracking from that point. If a visitor withdraws consent, Tailor stops tracking. Tailor applies the change during the same session, without requiring a page reload.

Effect on your reporting

Your experiment results include only visits from consenting visitors:

• Visits from consenting visitors are identified, measured, and counted in your results.
• Visits from visitors who decline, have not yet responded, or whose consent cannot be read are not tracked and do not appear in your results.
• Before a visitor responds to the consent banner, the visit is not tracked, so no visitor is measured ahead of their consent decision.