One control point for every script.
The gateway already decides whether each script may run. Tag Management lets you add, change and remove those scripts from the same dashboard, so you can retire a separate tag manager.
// one tag, managed in the gateway { "tag": "LinkedIn Insight Tag", "category": "advertising", "loads": "after opt-in", "pages": "all except /admissions/*", "version": "v4 · published" }
Sample rule on a fictional site.
Two systems decide what runs on your site.
A tag manager loads scripts. A consent tool is meant to stop them. When the two disagree, scripts slip through.
Consent rules live somewhere else
Tag manager triggers and consent categories are set in different tools, often by different people, and drift apart.
A container can add anything
Anyone with publish access can add a tag. It may load on every page, including intake and insurance pages.
No single record of changes
Showing which tag ran on which page on a given day is hard when changes happen in two places.
From new tag to live page in four stops.
Paste the vendor's script into the dashboard. It is stored in the gateway, not in your page source.
Assign a consent category and the pages it may load on. Sensitive paths can be excluded.
Each change is saved as a new version with who made it and when, so you can roll back.
On the live site, the tag loads only on its pages and only after the visitor opts in to its category.
What Tag Management does.
Every script in one list
Tags you add and scripts already on the page appear in one inventory, each with its category and status.
Page rules
Choose where each tag may load. Keep it off paths such as intake forms or insurance checks.
Versions and rollback
Every change is a version, with the person and the time. Roll back to any earlier version. [VERIFY]
Consent built in
A tag cannot load outside its consent category. There is no second rule set to keep in sync.
Publishing roles
Decide who can add, edit and publish tags. [VERIFY]
Many sites, one policy
Agencies and health systems can apply the same tag rules across every site they manage.
Each tag, with where and when it loads.
The tag list shows every managed script, its category, its pages and its live version.
Sample dataTags
site_0000 · example.org- Google Ads tagPublished
- LinkedIn Insight TagPublished
- Google Analytics 4Published
- Heatmap scriptNeeds review
- Session recordingBlocked by policy
- Category
- Advertising
- Loads
- After opt-in
- Pages
- All except /admissions/*
- Published
- 14 Nov 2026, 10:05 ET
One snippet replaces the container.
Add the gateway first in your site's head. Tags you manage in the dashboard load through it, so the separate tag manager container can come out.
WordPress and Webflow guides<!-- First in <head>, before any other script -->
<script src="https://gateway.compli3d.ai/v1/gateway.js" data-site="site_0000"></script>Fictional site ID shown. Your dashboard gives you the snippet with your own site ID. [VERIFY SNIPPET]
About Tag Management.
Do I have to retire my tag manager?
No. The gateway holds scripts loaded by a tag manager the same way it holds any other script. Moving tags across is optional.
Can you help move tags over from Google Tag Manager?
Yes. We recreate each tag in the gateway with you, check that it loads as expected, and then you remove the container. [SETUP TIME]
Can a tag load on some pages and not others?
Yes. Each tag has page rules, so you can keep it off paths such as intake or insurance pages.
Who can publish a tag?
People you give the publish role. Every change is recorded with who made it and when. [VERIFY]
Does managing a tag here make it safe for health pages?
It gives you control over where and when each tag loads. Whether a tag belongs on a page is a decision for you and your counsel.