Lightning CMP connects your third-party tools to consent in two ways. Pick by
whether the vendor has a **consent-aware mode**.

Before installing, use the [Lightning configurator](https://demo.lightning-consent.io/)
or the [setup decision guide](/install/choose-setup/). If you use Google Tag
Manager, start with the [Google bridge](/integrations/bridges/#google-gtag--gtm)
and manage individual tag consent inside GTM.

## Bridge it (preferred)

If the vendor can throttle itself on a consent signal — Google, HubSpot, Adobe,
Pardot, or [your own vendor](/integrations/custom-bridges/) — **bridge** it. The
CMP loads the tag and forwards the decision, so under denial it keeps sending
cookieless, privacy-safe signals instead of going dark. See
[Built-in bridges](/integrations/bridges/).

## Block it (fallback)

If the vendor has **no** consent-aware mode — Meta Pixel, TikTok, LinkedIn,
Hotjar… — **block** it. The CMP refuses to execute the tag's `<script>` until its
category is granted. See the [Script blocker](/integrations/script-blocker/).

## Decision table

| The vendor…                                                                      | Do this                                        |
| -------------------------------------------------------------------------------- | ---------------------------------------------- |
| …has a Consent Mode / consent API (Google, HubSpot, Adobe, Pardot)               | [Bridge](/integrations/bridges/) it            |
| …is anything else the CMP ships no adapter for, but _does_ expose a consent hook | [Custom bridge](/integrations/custom-bridges/) |
| …just fires a pixel with no cookieless mode                                      | [Block](/integrations/script-blocker/) it      |

:::tip
Reaching for a bridge over a block is what keeps your measurement alive. Only
fall back to blocking when a bridge genuinely isn't possible.
:::