> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/regulations-manager/frameworks/iab-tcf/iab-stacks.md).

# IAB stacks

{% hint style="success" %}
**Access Type**: Regulations Manager - Editor
{% endhint %}

A stack is an IAB-defined grouping of IAB purposes that will be listed together in the first-layer of the widget for the end-user. The stack will be surfaced in lieu of each purpose being listed individually in the first-layer of the widget. In this article, we will cover:

* [Enable automatic stacks](#enable-automatic-stacks)
* [Manage stacks](#manage-stacks)

{% hint style="info" %}
In addition to utilizing IAB stacks, your organization can create categories (i.e. custom stacks) to group purposes in the first-layer of the widget. [Click here](/regulations-manager/manage-regulations/configure-regulation-by-vendor/configure-categories-for-regulation-by-vendor.md) for more information.
{% endhint %}

To start, click **Regulations Manager** in the left-hand panel.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2F8mHBFEasbCecBPmuE3Kh%2FScreenshot%202026-09-15%20at%207.21.21%E2%80%AFAM.png?alt=media&amp;token=a1e5ea20-451e-42c6-8322-459932ce64af" alt="" width="563"><figcaption></figcaption></figure>

Navigate to a regulation that has IAB TCF enabled on the list and click the **Edit** icon inline with the regulation name.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FrsuGHRuRYSesBrp6a0ZW%2FScreenshot%202026-10-07%20at%208.43.34%E2%80%AFAM.png?alt=media&amp;token=3964561d-26d7-4f1b-98f0-1c72e96bdda1" alt="" width="563"><figcaption></figcaption></figure>

Select the **Vendors & Purposes** tab and click **Manage Stacks & Categories** on the subsequent page.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FNEI19BddudoqiDAoLZY6%2FScreenshot%202026-10-07%20at%208.52.33%E2%80%AFAM.png?alt=media&amp;token=338c5d45-6bbf-448e-ad12-2ba907ad3a0a" alt="" width="563"><figcaption></figcaption></figure>

Ensure the **Stacks** tab is selected. Any configuration made for IAB stacks will be listed.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2Fc0WYntupvv84RobXr1IJ%2FScreenshot%202026-10-07%20at%209.14.35%E2%80%AFAM.png?alt=media&amp;token=196869a8-9873-4d5b-9e54-f810bea2b91e" alt="" width="563"><figcaption></figcaption></figure>

***

### Enable automatic stacks

The automatic stacks feature allows your organization to let Didomi set the IAB-defined stacks for the regulation based on the purposes and special features included in the regulation.&#x20;

{% hint style="warning" %}
**Note**: If your organization utilizes the automatic stacks feature then it will not be able to manually add any other IAB-defined stacks to the regulation.
{% endhint %}

Select the toggle for **Enable automatic stacks** to enable the feature.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2F1eVPoKCO7vfU7fjPEuOo%2FScreenshot%202026-10-07%20at%209.53.54%E2%80%AFAM.png?alt=media&amp;token=78f62bb3-684f-44f6-8684-092a1615de5f" alt="" width="563"><figcaption></figcaption></figure>

When enabled, Didomi will apply the following logic when grouping purposes into IAB-defined stacks:

<table><thead><tr><th width="245.08331298828125">Condition</th><th width="74.583251953125">Stack #</th><th>Stack text</th></tr></thead><tbody><tr><td>Regulation includes any<a href="/regulations-manager/frameworks/iab-tcf/iab-purposes.md"> IAB purpose</a> between 2-11</td><td>42</td><td>Personalised advertising and content, advertising and content measurement, audience research and services development</td></tr><tr><td>Regulation includes any <a href="/regulations-manager/frameworks/iab-tcf/iab-special-features.md">IAB special features</a></td><td>1</td><td>Precise geolocation data, and identification through device scanning</td></tr><tr><td>Regulation includes <a href="/regulations-manager/frameworks/iab-tcf/iab-purposes.md">IAB purpose 1</a></td><td>None</td><td>Purpose 1 listed separately from any IAB-defined stack. <br><br>Store and/or access information on a device</td></tr></tbody></table>

### Manage stacks

As an alternative to having Didomi automatically set the IAB-defined stacks based on what is included in the regulation, your organization can manually set which IAB defined stacks are added to the first layer of your privacy widget.

{% hint style="warning" %}
**Note**: Ensure that the Enable automatic stacks toggle is deactivated in order to manually set IAB-defined stacks.
{% endhint %}

Click **Add IAB stacks**.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FtmUyCL83bj2ZWy1NstTI%2FScreenshot%202026-10-07%20at%203.17.55%E2%80%AFPM.png?alt=media&amp;token=53d6007d-8b69-4fb0-aa4d-8f3db882db1e" alt="" width="563"><figcaption></figcaption></figure>

Use the subsequent modal to select the IAB-defined stacks that should be included in the first layer of the privacy widget.

Click **Add selected stacks** when finished.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FuPEItmpPi399DwcUNblm%2FScreenshot%202026-10-07%20at%203.40.20%E2%80%AFPM.png?alt=media&amp;token=9c3d7716-3dc5-454d-a41c-1d96437c58d5" alt="" width="375"><figcaption></figcaption></figure>

Selected stacks will be added to the stacks list and include the stack name and purposes that stack is meant to encompass.&#x20;

{% hint style="info" %}
There is currently no restriction that blocks your organization from adding multiple IAB-defined stacks that encompasses the same purpose. However, doing so may provide a less clear end-user consent experience.
{% endhint %}

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FGWB7sqRz2Ufx1w8sdLfB%2FScreenshot%202026-10-07%20at%203.49.28%E2%80%AFPM.png?alt=media&amp;token=a734ee3a-ff50-409e-bde4-d087aa3e06f0" alt="" width="563"><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didomi.io/regulations-manager/frameworks/iab-tcf/iab-stacks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.