> 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/consent-management-platform-cmp/consent-notices/reorder-consent-notice-buttons-web.md).

# Reorder consent notice buttons (web)

By default, the "Learn more" button will be displayed *before* the "Agree" button on the sticky banner. If you use the pop-in banner format, "Learn more" will be displayed *after* "Agree".

#### ✅ Steps for changing the button order on a web notice:

* Go to **Consent notices**. 
* Go to step **2. Customization**.
* Click on **Advanced settings** then **Custom JSON**.

  <figure><img src="https://support.didomi.io/hs-fs/hubfs/New%20console%20flow/Capture%20d%E2%80%99%C3%A9cran%202023-03-09%20%C3%A0%2011.41.29.png?width=688&#x26;height=338&#x26;name=Capture%20d%E2%80%99%C3%A9cran%202023-03-09%20%C3%A0%2011.41.29.png" alt=""><figcaption></figcaption></figure>
* Add code (see below) in the Custom JSON field.&#x20;

  <figure><img src="https://support.didomi.io/hs-fs/hubfs/New%20console%20flow/Capture%20d%E2%80%99%C3%A9cran%202023-03-09%20%C3%A0%2011.42.36.png?width=688&#x26;height=341&#x26;name=Capture%20d%E2%80%99%C3%A9cran%202023-03-09%20%C3%A0%2011.42.36.png" alt=""><figcaption></figcaption></figure>

#### ✍️ Code to insert&#x20;

To change the order you need to set the value at :

* "before" for pop-in format
* "after" for sticky banner format

**Pop-in format :**&#x20;

```
{
    "notice": {
        "learnMorePosition": "before"
     }
  }


```

**Sticky banner format :**&#x20;

```
{
     "notice": {
        "learnMorePosition": "after"
      }
}
```

📰 Please refer to our [developer guide](https://developers.didomi.io/cmp/web-sdk/consent-notice/notice/look-and-feel) for more information.


---

# 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/consent-management-platform-cmp/consent-notices/reorder-consent-notice-buttons-web.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.