Everything You Need forTealium + Secure Privacy

Follow the documented flow: add the extension, set Pre Loader scope, publish across environments, then rescan your property so declarations stay accurate.

Navigate to Extensions

Inside Tealium iQ, open Extensions from the left navigation as shown in the Secure Privacy screenshots

Use Add Extension to start a new configuration
Switch to the Advanced tab for JavaScript-based injections
Keep naming consistent (“Secure Privacy”) for future audits

Advanced JavaScript Code

Choose Advanced JavaScript Code and paste the Secure Privacy installation snippet

Paste the full script from Domains → Installation
Avoid trimming async attributes unless Tealium policy requires it
Save the extension draft before approval workflow

Pre Loader Scope (Required)

Set scope to Pre Loader so consent executes before the main tag queue

Addresses the FAQ: why Pre Loader matters for GDPR sequencing
Pairs with Tealium load rules for geo-specific profiles
Re-test whenever you add high-priority synchronous tags

Approve & Publish

Move the extension through Tealium’s publish dialog just like other changes

Click Approve for Publish when validation finishes
Select every environment that should enforce consent
Publish and note the version for rollback scenarios

Google & Adobe Neighbors

Tealium often loads Google, Adobe, Meta, and more—Secure Privacy categories gate them all

Pair with the Google Consent Mode guide when Google tags need API signals
If Adobe Launch also exists, align on a single CMP injection strategy
Use Tealium load rules to limit the extension to regions that require banners

QA & Telemetry

Use Tealium debugging tools plus browser dev tools for verification

Trace extension execution order in Tealium’s console
Validate network calls respect consent after choices
Capture screenshots for compliance evidence libraries

Post-Install Rescan

The article reminds you to rescan after Tealium deploys

Navigate to Report → Scan Reports → Rescan
Refresh cookie declarations shown to visitors
Compare before/after to prove blocking works

FAQ Highlights

Built-in answers from the Secure Privacy Tealium article

Why Pre Loader is mandatory for compliant sequencing
Works across dev, QA, and prod when you publish to each
Point stakeholders to the same knowledge base URL

Tealium vs Page Embed

Why Use Tealium iQ

Feature	Tealium Extension	Static Head Snippet
Consent load order control	Pre Loader scope before tag queue	Depends on manual script order
Environment coverage	Publish to dev, QA, prod together	Often prod-only unless automated
Marketer-friendly updates	Tealium users can revise extension	Requires developer deploy
Centralized tag inventory	Same UI as other Tealium tags	Split across CMS + repos
Supports 65+ privacy templates
Requires Secure Privacy account
Documentation reference	Tealium iQ integration article	Generic embed docs
Risk if scope wrong	Higher if not Pre Loader	Higher if placed too late
Post-deploy hygiene	Rescan inside Secure Privacy	Same rescan recommendation
Best for	Teams standardized on Tealium TMS	Tiny stacks without a TMS