> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/consent-management/user-guides/privacy-banners/banner-templates.md). # Banner Templates Commanders Act offers multiple banner templates for different kind of privacy workflows. | Template | Description | | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Header (with Privacy Center)** |

Floating overlay banner (is layered on top of the website), positioned at the top of the page. This banner includes a text message and customizables buttons. You can add a link to another page (e.g. privacy policy).

This template exists with and without an optional privacy center.

| | **Popin (with Privacy Center)** |

A floating modal dialogue (pop-up), positioned in the center of the page. This banner includes a text message and customizable buttons. It supports links to another page (e.g. privacy policy).

This template exists with and without an optional privacy center.

| | **Footer (with Privacy Center)** |

Floating overlay banner, positioned at the bottom of the page. This banner includes a text message and customizable buttons. It supports links to another page (e.g. privacy policy).

A variation of this template exists with extended accessibility support.

| | **Popin with categories** | This template directly opens the privacy center that allows visitors to select Commanders Act Consent categories and sub-categories they want to activate/deactivate. | | **Footer / Popin / Header** | Floating information banner, no buttons to refuse or accept. Not compliant for GDPR & CCPA | | **Footer without button** | Floating overlay banner, positioned at the bottom of the page. This banner includes a text message and cross icon to close the banner. It supports links to another page (e.g. privacy policy). Not compliant for GDPR & CCPA | | **IAB TCF 2.2 Popin** |

Template available if IAB TCF compliancy option is activated in the Data Governance > Consent Management > Settings section.

A floating modal dialogue (pop-up), positioned in the centre of the page. This template offers consent controls following the IAB TCF 2.2 standard.

| | **IAB TCF 2.2 Footer** |

Template available if IAB TCF compliancy option is activated in the Data Governance > Consent Management > Settings section.

Floating overlay banner, positioned at the bottom of the page. This template offers consent controls following the IABTCF 2.2 standard.

| | **IAB TCF 2.0 Popin (deprecated)** |

Template available if IAB TCF 2.0 option is activated in the Data Governance > Consent Management > Settings section.

A floating modal dialogue (pop-up), positioned in the centre of the page. This template offers consent controls following the IAB TCF 2.0 standard.

| | **IAB TCF 2.0 Footer (deprecated)** |

Template available if IAB TCF compliancy option is activated in the Data Governance > Consent Management > Settings section.

Floating overlay banner, positioned at the bottom of the page. This template offers consent controls following the IABTCF 2.0 standard.

| | **Footer with privacy center (accessibility)** |

Floating overlay banner, positioned at the bottom of the page. This banner includes a text message and customizable buttons. It supports links to another page (e.g. privacy policy).
Includes standards for WCAG 2.0
for more details, look at this page of our documentation

| | **Popin with privacy center (accessibility)** |

A floating modal dialogue (pop-up), positioned in the center of the page.This banner includes a text message and customizable buttons. It supports links to another page (e.g. privacy policy).
Includes standards for WCAG 2.0
for more details, look at this page of our documentation

| --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://doc.commandersact.com/features/consent-management/user-guides/privacy-banners/banner-templates.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.