Most of the tags live in the tag manager. So does most of the trouble.
GTM consent problems are almost always ordering problems: the consent state arrives after the tags that depended on it. DotCensus initializes early and publishes consent as events your existing triggers can use.
Status today: In beta. Consent initialization and consent events are implemented; a published template is planned.
What it is
Google's tag management system, where marketing and analytics tags are configured and deployed without changing site code — which is also why the site owner frequently does not know what is in it.
What DotCensus controls
- Consent initialization ahead of tag firing
- Consent state published as data-layer events
- Built-in consent checks on supported tag types
- Diagnostics for initialization ordering
How it is installed
- Add the DotCensus runtime as early as possible — before the GTM container where you can
- Point your triggers at the DotCensus consent events
- Map GTM tag categories to DotCensus categories
- Preview, publish, then verify with a scan
How you verify it
- The ordering diagnostic reports whether consent was initialized before the container
- Reject-path testing confirms no marketing tag fires after a refusal
Limits worth knowing
- A tag added directly to the container outside your process will still fire unless its category is mapped — which is why the scan matters more than the configuration
Other integrations
Connect the rest of the stack
Know what runs before you ask visitors to trust it.
Start with a scan of what your website loads today. The list is usually longer than the team expects, and that is the useful part.
No code to install for a scan Public pages only DotCensus runs on DotCensus