Get more from OneTrust with Cressive
Check that visitors’ choices are respected, resolve shared issues across websites and use OneTrust consent data to understand traffic missing from analytics.
Book a 15-minute callHow Cressive works with OneTrust
Support across the six steps of enterprise website privacy compliance
At each step, Cressive’s platform and services give privacy defensible evidence, IT clear fixes and marketing trustworthy data.
Step 1 of 6
Set policy
Applicable regulations, consent rules and site ownership for each market.
OneTrust’s role
- Geolocation rules: banner and consent model set by country or US state.
- Cookie categorisation: known cookies sorted into consent categories automatically.
- Signal settings: Global Privacy Control, IAB TCF and Google Consent Mode.
What Cressive adds
- Policy advisory: consent rules defined for each market and company policy. (services)
- RACI: responsibility and accountability recorded for each website.
- Regulations built in: GDPR, UK GDPR and CCPA rules ready to apply.
Step 2 of 6
Deploy consent
Banner configuration and consent gating of trackers.
OneTrust’s role
- Banner templates: by region and language, with a preference centre.
- Script blocking: tracking scripts blocked until the visitor consents.
- Consent records: a log of each visitor’s consent choice.
What Cressive adds
- Banner configuration: most non-compliant sites have an incorrectly configured banner, not a missing one. (services)
- Tracker fixes: correct categories and source-specific fixes, from video embeds to ad platforms. (services)
- Implementation support: changes made alongside the teams and agencies running OneTrust. (services)
Step 3 of 6
Audit behaviour
Testing what each site does before and after consent choices.
OneTrust’s role
- Cookie scans: scheduled discovery and categorisation of cookies.
- Compliance Assistant: daily checks for tracking before consent or after opt-out, where included.
What Cressive adds
- Independent risk view: own analysis, not OneTrust’s categories, finding misclassified or overlooked trackers.
- Consent states: before consent, after accept, after reject and with Global Privacy Control.
- Evidence: regulator-ready findings, judged against applicable regulations and company policies.
Step 4 of 6
Remediate
Fixing root causes and confirming the fix on each affected site.
OneTrust’s role
- Configuration changes: categories, banner settings and blocking, published from OneTrust.
- Fix guidance: Compliance Assistant’s prioritised next steps for each issue.
What Cressive adds
- Common causes: one fix covers the same issue across many sites.
- Remediation report: fix instructions for the site’s technical stack, including OneTrust, with effort estimates.
- Verification: affected sites rescanned once fixes go live.
Step 5 of 6
Monitor and communicate
Catching new issues, alerting site owners, keeping central oversight.
OneTrust’s role
- Recurring scans: scheduled cookie scans and Compliance Assistant’s daily checks.
- Issue workflows: tasks and owners through wider OneTrust modules, where licensed.
What Cressive adds
- Scan schedule: daily, weekly, monthly or on demand.
- RACI alerts: issues routed to each site’s accountable owner.
- Portfolio view: worst offenders and privacy score trends, showing risk reduction over time.
Step 6 of 6
Model unrecorded traffic
Estimating traffic missing from analytics due to consent choices.
OneTrust’s role
- Consent records: logs of accepted and rejected consent, by category.
What Cressive Analytics Rebuild adds
- Proprietary modelling: analytics and consent data combined, without Google’s minimum traffic thresholds.
- Clear reporting: recorded and modelled traffic shown side by side.
- No extra tracking: built from data already collected.
Frequently asked questions
Running Cressive Privacy Compliance alongside OneTrust, and what is needed to start.
Working alongside OneTrust
Does Cressive replace OneTrust?
No. OneTrust is a broad privacy suite, and its cookie banner stays in place on each site. Cressive Privacy Compliance checks that the banner works: it audits each site, finds shared causes across the portfolio, routes issues to each site’s owners and tracks risk over time. Cressive’s services help configure OneTrust correctly, and Analytics Rebuild estimates the traffic that consent choices remove from analytics.
Why add Cressive Privacy Compliance when OneTrust already scans websites?
Because it gives a separate view of risk. OneTrust checks a site against its own cookie inventory and categories. Cressive Privacy Compliance runs its own analysis without using OneTrust’s categories or rules, so it finds trackers that were misclassified, overlooked or interpreted differently. For a DPO, that is an independent third-party risk assessment.
Which OneTrust setups does Cressive Privacy Compliance support?
OneTrust is one of the cookie banners Cressive Privacy Compliance recognises. The supported technology page lists the cookie banners, tag management tools and regulations covered.
Getting started
What is needed to get started?
A short conversation about the sites, markets and current OneTrust setup. Book a 15-minute call to start.
What does Analytics Rebuild need from OneTrust?
Access to OneTrust consent records and to the analytics account. Both are checked for quality and coverage before modelling starts.
What does the OneTrust setup need next?
Tell us about the sites, recurring issues and gaps in analytics.