OneTrust integration for cookie consent
Admins replace Intellum’s default cookie banner with OneTrust’s banner and preference center, so analytics scripts load only after people consent. A OneTrust admin configures it, then an Intellum admin turns it on.
Common uses of the OneTrust integration
- Learners in the EU get a compliant banner where they can accept, reject or configure cookies.
- Privacy teams block analytics scripts and pixels until a learner accepts the matching consent category.
- Learners get privacy-friendly video embeds: YouTube switches to youtube-nocookie and Vimeo adds do-not-track.
How the OneTrust integration works
Your OneTrust admin scans and categorizes cookies in OneTrust, sets templates and geolocation rules, and publishes the production script. An Intellum admin clicks Enable OneTrust in Settings › Apps and pastes that script. Intellum rejects any submission that includes unrelated script tags.
From then on, platform scripts such as GA4, Google Tag Manager, Gainsight PX and Facebook Pixel run only after a person accepts the matching consent category.
How to set up the OneTrust integration
Your OneTrust admin configures OneTrust. An Intellum admin turns it on in Settings › Apps and pastes the script. Configure each subdomain separately.
- Your own OneTrust Cookie Compliance account
- The OneTrust production script, plus the test script for non-production environments
- Required Intellum cookies p_auth, p_auth2, p_path and p_destination categorized in OneTrust
How the Intellum and OneTrust integration handles access and data
- Method: script blocking through the OneTrust production script. Google Consent Mode is unsupported.
- Data: consent and cookie control only. No records sync between Intellum and OneTrust.
- Strictly necessary cookies: declare _base_session, jstztimezone and user_id_for_logging as Strictly Necessary if the scan misses them.
- Custom scripts: only scripts that use Intellum’s consent helper are gated, so new custom scripts must use it.
- Changes: template or rule changes need republishing and can take up to 4 hours. The script value is hidden in Settings › Apps after saving.
What to know about the OneTrust integration
- Revoking consent stops scripts only after the page reloads.
- OneTrust’s Do Not Sell button, Cookie Settings button script and Cookie List scripts are unsupported. Use the persistent Cookie Settings hover button and the preference center’s cookie list.
- Ask OneTrust support to stop the banner from focusing the first navigable element.
Questions about the OneTrust integration
Platform scripts including GA4, Google Tag Manager, Gainsight PX, Facebook Pixel and Intellum’s own tracker run only after a person accepts the matching consent category. Custom scripts are gated when they use Intellum’s consent helper.
No. The OneTrust integration blocks scripts until a person consents, and Google Consent Mode is unsupported. If a person revokes consent, scripts stop after the next page reload.
Your own OneTrust Cookie Compliance account and its published production script, plus the test script for non-production environments. Categorize Intellum’s required cookies p_auth, p_auth2, p_path and p_destination before going live.
Yes. Intellum offers three banner options: its default cookie banner, custom JavaScript such as Cookiebot, or OneTrust.
See the OneTrust integration working with your stack
Walk through this integration, and the questions IT will ask, with an Intellum expert.