Key Takeaways
- Installing Secure Privacy comes down to one step on every platform: pasting a single script tag into wherever that platform lets you add custom code to your site's <head>.
- Where that custom-code panel actually lives, and what restricts it, varies by platform: Squarespace requires a Core plan or higher, Wix and GTM route well-known marketing pixels through a separate panel, and Joomla's default editor strips <script> tags unless you change a setting or use a different module.
- Adobe's tag-management product has been renamed since older installation guides were written. "Adobe Dynamic Tag Manager" is a discontinued product; the current one is Adobe Experience Platform Tags.
- Webflow has no native custom-code restrictions beyond requiring a paid site plan, and its custom-code panel works the same way as most modern site builders.
Every platform Secure Privacy installs on uses the same underlying method: one script tag, pasted into wherever that platform lets you add site-wide custom code. What actually differs is where that panel lives, what plan tier unlocks it, and a handful of platform-specific gotchas that aren't obvious until you hit them. Below: the script itself, and the exact current path for each platform, verified against each one's own documentation rather than carried over from an old guide.
Secure Privacy is a cookie and consent management platform that generates the consent banner and blocks tracking scripts until a visitor consents; the installation step below is what connects that banner to your actual site.
The Script You're Installing
Every platform below uses the same script tag, generated from your own Secure Privacy dashboard once your account and scan are set up:
<script src="https://app.secureprivacy.ai/script/YOUR-SITE-ID.js"></script>This is an illustrative example; your actual script includes your specific site ID and comes from your dashboard, not from a generic snippet copied from this page. Once it's placed correctly (see your platform below) and the site is published, Secure Privacy scans the site, categorizes what it finds, and displays the banner, blocking non-essential scripts until the visitor consents.
Shopify
Go to Online Store → Themes, select your current theme, open the "..." menu → Edit code, and open theme.liquid. Paste the script inside the <head> section, placed right after the {{ content_for_header }} object rather than replacing or editing it, since Shopify's own documentation warns that object's behavior can change between theme updates. Save, and the script applies site-wide.
Wix
In your site's dashboard, go to Settings → Custom Code, click Add Custom Code, paste the script, set the scope to All Pages, and choose Head under "Place Code in." One thing worth knowing: Wix's own documentation steers well-known marketing pixels (Google Analytics, Meta, TikTok) toward a separate Marketing Integrations panel rather than Custom Code. A CMP script like Secure Privacy's isn't one of those pixels, so Custom Code remains the correct method here.
Squarespace
Go to Settings → Advanced → Code Injection, and paste the script into the Header field. This is gated to Squarespace's Core, Plus, and Advanced plans; it isn't available on the entry-level tier. It's also worth knowing that injected code doesn't run on Squarespace's checkout pages, which matters if you need consent-gated scripts to cover a store's full purchase flow.
Joomla
Joomla has no single settings field for this; use either a Custom HTML module (Content → Site Modules → New → Custom, assigned to display globally) or a template override editing the site's head output directly, which is the cleaner method for guaranteed placement. The gotcha worth knowing before you troubleshoot a script that "isn't working": Joomla's default TinyMCE editor strips <script> tags automatically unless you remove "script" from the Prohibited Elements list under Extensions → Plugins → Editor - TinyMCE, or use the Custom HTML - Advanced module instead, which doesn't filter it.
Google Tag Manager
Create a Custom HTML tag, paste the script (wrapped in <script></script> tags if your GTM template requires it), and attach the Initialization - All Pages trigger, the trigger GTM itself recommends for anything that needs to fire early and site-wide. Enable "Support document.write" only if your specific script needs it.
Adobe Experience Platform Tags
If you're looking for "Adobe Dynamic Tag Manager," that product no longer exists; Adobe replaced it years ago with what was called Launch, since renamed Adobe Experience Platform Tags. Inside a Rule, add an Action with Action Type Custom Code (available from the Core extension on every account tier), and paste the script into the code editor there. Rule-based actions run in the order you configure, and Adobe minifies the content on publish.
Webflow
Go to Project Settings → Custom Code, and paste the script into the Head Code field, which applies site-wide and carries a 50,000-character limit. This requires a paid Webflow site plan; the free tier can't add custom code at all. A dedicated breakdown of what GDPR actually requires of a Webflow cookie banner, beyond just where the script goes, covers the legal side in full.
What If Your Platform Isn't Listed?
The same underlying method applies to essentially any platform that lets you edit a site's <head> or add custom HTML: find where that platform exposes custom code or header scripts, paste the script there, and confirm it's not scoped to a single page if you need site-wide coverage. The specific navigation path is the only thing that changes; the script and what it does once installed stay identical.
FAQ
Does Secure Privacy require a specific plugin or app on my platform?
No. Secure Privacy installs the same way on every platform, as a single script tag placed in that platform's custom-code or header area. Some platforms (Wix, Squarespace) also have marketplace apps for other tools, but Secure Privacy's own installation doesn't depend on one.
Why isn't my consent banner showing up after I added the script?
The most common causes are: the script placed on a page-scoped element instead of a site-wide one (common on Wix and Webflow, where both options exist), a plan tier that doesn't support custom code (Squarespace specifically gates this), or, on Joomla, the default editor silently stripping the script tag.
Is Adobe Dynamic Tag Manager still a thing?
No. Adobe discontinued DTM years ago in favor of what's now called Adobe Experience Platform Tags. Any guide still referring to "DTM" by that name is describing a product that no longer exists.
Can I install Secure Privacy on a Squarespace site without upgrading my plan?
No. Code injection on Squarespace is only available on the Core, Plus, and Advanced plans, not the entry-level tier. There's no workaround that keeps custom code on a lower plan.
Does the installation script need to go on every single page individually?
No, as long as it's placed in each platform's site-wide header/custom-code area (Project Settings on Webflow, theme.liquid on Shopify, the Header field on Squarespace, and so on) rather than a page-specific embed element, which several platforms also offer but which only applies to that one page.
Sources
- Shopify Help Center: Edit code in the Shopify code editor
- Wix Support: Embedding custom code on your site
- Squarespace Help: Using code injection
- Joomla Documentation: Adding JavaScript
- Google Tag Manager Help: Custom HTML tags
- Adobe Experience Platform Tags: terminology and product updates
- Webflow Help Center: Custom code in project settings
