# Integrations and cookie consent Your published site can carry Google Analytics, a Google Tag Manager container and three support widgets, each added by pasting an ID. If your visitors need to agree to cookies first, the built-in cookie banner asks them, category by category, and every integration waits for the answer. All of this lives in the site's **Settings** under **Integrations**. Admins and collaborators can change it, and changes publish with your next Update and Promote. --- ## The integrations | **Integration** | **Consent category** | **What it stores** | | ---------------------------------- | -------------------- | -------------------------------------------------------------------------- | | **Google Analytics ID** | Analytics | \_ga and \_ga\_ cookies | | **Capable analytics integration** | Analytics | The same Google Analytics cookies. Needs a Google Analytics ID. | | **Google Tag Manager ID** | All three, see below | Whatever the tags in your container store | | **Jira Service Management widget** | Functional | An ajs\_anonymous\_id cookie and widget session details in browser storage | | **Released changelog** | Functional | Nothing on your site. The widget shows content from Released | | **Statuspage** | Always loads | No cookies. It only remembers which notices a visitor dismissed | With the cookie banner off, every integration loads on every page view, as before. --- ## The cookie banner Turn on **Cookie consent popup** and every page shows a banner in the bottom right corner until the visitor chooses. It says **This site uses cookies for analytics and to improve your experience. You can accept them, reject them, or choose which to allow.** | **Button** | **What happens** | | -------------- | ---------------------------------------------------------------------------------- | | **Accept all** | Allows every category the banner offers, and nothing else. | | **Reject all** | Allows only Essential storage, such as remembering this choice. | | **Customize** | Shows a checkbox for each category, then **Save choices**. Essential is always on. | The banner only offers the categories your site uses: * **Analytics** when Google Analytics or the Capable analytics integration is set up. * **Functional** when the Jira Service Management or Released widget is set up. * **Analytics**, **Marketing** and **Functional** when a Tag Manager container is connected, because a container can hold any kind of tag. A **Cookie settings** link is added to the footer of every page, so visitors can change their mind. Withdrawing a category reloads the page and removes the cookies the built-in integrations set for it. A choice is kept in the visitor's browser for 12 months, then the banner asks again. It also asks again when you add an integration that needs a category the visitor was never offered. --- ## Google consent mode and Tag Manager With the banner on, the site sets Google consent mode v2 to denied for everything before any tag loads, then applies the visitor's choice: | **Category** | **Google consent types it grants** | | ------------ | --------------------------------------------------- | | Analytics | analytics\_storage | | Marketing | ad\_storage, ad\_user\_data and ad\_personalization | | Functional | functionality\_storage and personalization\_storage | It also pushes Tag Manager events you can use as Custom Event triggers: `capable_consent_essential`, `capable_consent_analytics`, `capable_consent_marketing` and `capable_consent_functional` for each category allowed, plus `capable_consent_update` carrying the whole choice in `capable_consent`. An event fires again on later page views, but not twice on the same page. What your container does depends on one switch, **Tag Manager handles consent**. It appears once the banner is on and a Tag Manager ID is set. | **Tag Manager handles consent** | **What happens** | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | Off (the default) | The container loads only after a visitor selects **Accept all**. Anyone who rejects or customises never loads it. | | On | The container loads on every page view, and its own consent settings decide which tags fire, using the consent types and events above. | --- ## A few things that catch people out * Videos and maps embedded in your pages, such as YouTube, Vimeo or Google Maps, load straight away and may set their own cookies. The banner does not control them. * Withdrawing consent removes cookies set by Capable's built-in integrations. Cookies set by your own Tag Manager tags stay until they expire, unless the tags clear them. * For your site's security, Tag Manager tags can only load scripts from Google. Tags from other providers do not run. * Visitors with JavaScript turned off see no banner, and no tags run for them. * A visitor who accepted the old two-button banner is asked again, because it never offered Marketing as a separate choice. --- ## Related ### [Add a cookie consent banner to a Confluence site](https://help.gocapable.com/sites/add-a-cookie-consent-banner-to-a-confluence-site.html) Turn the banner on, step by step. ### [Use Google Tag Manager with a published Confluence site](https://help.gocapable.com/sites/use-google-tag-manager-with-a-published-confluence-site.html) Consent triggers in your container. ### [Add Google Analytics to a published Confluence site](https://help.gocapable.com/sites/add-google-analytics-to-a-published-confluence-site.html) Measure traffic with GA4. ### [Chat widget / marketing tag / third-party script does not run on the published site](https://help.gocapable.com/sites/chat-widget-marketing-tag-third-party-script-does-not-run-on-the-published-site.html) When a widget or tag stays silent. ### [Site settings](https://help.gocapable.com/sites/site-settings.html) Every setting in one place. --- _Paste an ID. Ask first if you need to._