Integrations

Integrations that follow the recorded choice

Consent Guru connects a published purpose model to Google Consent Mode, script controls, and the endpoints you operate.

Create a workspace View consent platform pricing

An integration that ignores purposes will undo the banner

Connecting a tag manager without mapping purposes just moves the compliance problem into another tool. The integration should read the same categories the visitor saw.

In the workspace, connecting Google Consent Mode, Google tag, or IAB items updates runtime signals the SDK consumes. Other catalog entries store connection state for the tools you enable.

What you can connect

Step 1
Purposes first
Create the purpose catalog before you connect a tag. The mapping needs somewhere to point.
Step 2
Consent Mode
Enable Google Consent Mode per website when you use gtag or Consent Mode-aware tags.
Step 3
Script control
Known loader URLs can be paused when their purpose is denied. In-container tags still need consent checks.
Step 4
Your stack
Use webhooks or the API for CRMs, warehouses, and apps that are not in the browser.

Key capabilities

Google Consent Mode

Purpose-to-signal mapping for ads and analytics storage, including Consent Mode v2 fields.

Tag manager loaders

The SDK can pause GTM or gtag loader URLs. It does not rewrite tags that already live inside a container.

IAB TCF and GPP

Where enabled, the SDK can emit IAB-style signals from the purposes and vendors you configure.

Webhooks

A general integration path for systems that should hear about consent and rights events.

What teams use it for

One purpose list for the banner and the integration.
Fewer tags that fire before a choice.
A webhook path when no native connector exists.
Connection state you can see per website.

Analytics tags

Allow measurement only when the analytics purpose is granted.

Advertising

Keep advertising signals aligned with an opt-in or opt-out purpose you defined.

Internal tools

Push verified events into the systems your privacy team already uses.

Privacy considerations

A connector does not review your vendor contract. If a tag receives identifiers for advertising, your team still has to decide whether that is a sale, sharing, or consent-based purpose.

Third-party scripts that run before the SDK, or from a domain you did not map, will not be controlled by the integration.

Questions

1.Which integrations are built in?

Google Consent Mode, Google tag loader control, and IAB TCF/GPP signaling are product features you enable. Other tools are connected through webhooks or the API.

2.Will connecting GTM block every tag?

Pausing the loader URL stops that loader. Tags already present in the container, or injected another way, need their own consent checks.

3.Can we integrate a custom stack?

Yes. Use the consent API and signed webhooks rather than waiting for a named connector.

This page describes how Consent Guru supports privacy operations. It is not legal advice, and using the product does not by itself make an organization compliant with GDPR, CCPA, CPRA, the DPDP Act, or any other law.