How to install Secure Privacy with Google Tag Manager (GTM)
Websites using Google Tag Manager (GTM) can easily deploy Secure Privacy by following these step-by-step instructions.
Websites using Google Tag Manager (GTM) can easily deploy Secure Privacy by following these step-by-step instructions.
We assume that you have already created a GTM account, created a website container in GTM and added the GTM container snippet to your website as required: https://support.google.com/tagmanager/answer/6103696
Implementing Secure Privacy in GTM
1. In your GTM container create a new tag by clicking Tags > New > Custom HTML Tag.
2. In the “HTML” field, insert the script tag from your installation page.
3. Choose “All pages” as a trigger and apply a name to your tag at the top of the configuration page, e.g. “Secure Privacy Script”. Click “Save” to create the tag. This is what your tag configuration should look like (except for the value of the API key):
4. Finally, click “Publish” to push your changes live to your site.
The consent banner is now active on your website.
Other Tutorials
- JavaScript block third party cookies
- Install Secure Privacy with Adobe Dynamic Tag Manager
- How to install Secure Privacy on Joomla
- Google’s Consent Mode API and Secure Privacy
- How to install Secure Privacy on Wix
- How to install Secure Privacy on SquareSpace
- How to install Secure Privacy on Shopify
- How to integrate Secure Privacy with Hubspot
OneTrust vs Secure Privacy vs Osano: Privacy Governance Platform Comparison
Choosing between OneTrust vs Secure Privacy vs Osano determines whether your privacy program achieves genuine governance maturity or merely checks compliance boxes. OneTrust dominates enterprise segments with €290 million in GDPR fines imposed partly due to organizations lacking proper consent infrastructure. Osano targets mid-market simplicity. Secure Privacy differentiates through AI-powered automation delivering 60-80% faster DPIA completion while supporting 130+ global privacy laws in unified pricing.
- Legal & News
- Data Protection
Do Not Track (DNT): Why the First Browser Signal Failed
In 2012, Do Not Track (DNT) promised a simple solution: a single browser setting that would tell every website to stop following you across the internet. Major browsers adopted it within months. Millions of users enabled it. Yet by 2019, the standard was officially dead, and browsers began removing the feature entirely.
- Legal & News
- Data Protection
How to Automate Privacy Impact Assessments
Your privacy team receives 50 new processing activity requests monthly. Each requires comprehensive risk assessment documentation. Manual workflows using spreadsheets and email coordination consume weeks per assessment. Business stakeholders complain about delays. This operational reality drives organizations to automate privacy impact assessments (PIAs and DPIAs).
- Legal & News
- Data Protection
- GDPR
- CCPA