Do this short decision step **before** copying the [Quickstart](/quickstart/) snippet. Lightning can either connect a tag to consent with a bridge or block it until consent; the right choice depends on where that tag is managed. > **Tip — Want a guided answer?** > Open the [Lightning configurator](https://demo.lightning-consent.io/) to walk > through your tag stack and produce the matching configuration. ### Google Tag Manager Use the **Google bridge** with your container ID. It loads GTM with the Consent Mode default already in place. Gate each tag inside GTM using its Consent Settings; do not hard-block the container in page HTML. ### GA4 or Google Ads without GTM Use the Google bridge with your `G-…` or `AW-…` ID. The CMP loads the Google tag and forwards Consent Mode updates for you. ### Other vendors Use a built-in or [custom bridge](/integrations/custom-bridges/) when the vendor supports a consent-aware mode. Use the [script blocker](/integrations/script-blocker/) for vendors that do not. ## Google Tag Manager Set the container ID in `bridges.google.tagId`: ```js lightning("init", { bridges: { google: { tagId: "GTM-XXXXXXX" }, }, }); ``` The bridge owns the GTM loader and pushes the Consent Mode default before the container starts. Keep your individual tags in GTM and set their built-in Consent Settings there. Verify the result in [GTM Preview](/guides/verifying/) and with `LightningCMP.debug()`. > **Warning — Do not use the script blocker for GTM** > `type="text/plain"` on a GTM container throws away Google's cookieless > Consent Mode signals. Block non-Google vendors that need blocking, but let > the Google bridge and GTM manage Google tags. ## Google tags without GTM Use the same bridge with a measurement or conversion ID: ```js lightning("init", { bridges: { google: { tagId: "G-XXXXXXX" } }, }); ``` If your site already loads `gtag.js`, omit `tagId` and keep the inline Consent Mode default at the top of ``; see [Google Consent Mode v2](/configure/consent-mode/). ## Other vendors The [Integrations overview](/integrations/overview/) explains the same decision for every vendor. As a rule, bridge a vendor that can self-throttle and block a vendor that cannot. ## Continue Return to the [Quickstart](/quickstart/) for the common snippet and the install verification step, or open the [configurator](https://demo.lightning-consent.io/) again if your stack changes.