> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/developer-guide/consent-javascript-sdk/reprocessing-in-the-consent-javascript-sdk/step-by-step-use-case.md).

# Step-by-Step Use Case

In this example, we will walk through common loops and sequences when working with different vendor consent settings in the **Consent JavaScript SDK**.

***

### Vendor Settings in This Scenario

* **myAnalyticsService**\
  Consent setting: **No Consent Mode**
* **myMarketingService**\
  Consent setting: **Essential Mode**

***

### Sequence of Events

| Step – Description                                                                         | Commands                                                                   | Consent Status                                                                                                               | Result                                                                                                                                                                                                                                                                       |
| ------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Page load initiated** – A pageview is requested to be tracked.                           | `js\n_jts.push({ track: "pageview" });\n_jts.push({ track: "submit" });\n` | <p><code>myAnalyticsService: true</code><br><code>myMarketingService: undefined</code> <em>(default consent status)</em></p> | <p><strong>Analytics Pageview-Tags:</strong> Executed without restrictions (justification does not require consent).<br><strong>Marketing Tags:</strong> Not executed (no explicit consent or denial provided yet).</p>                                                      |
| **Alternative A:** User interacts with the CMP banner and **consents to all tools**.       | –                                                                          | <p><code>myAnalyticsService: true</code><br><code>myMarketingService: true</code></p>                                        | <p><strong>Analytics Pageview-Tags:</strong> Not re-executed (consent setting unchanged).<br><strong>Marketing Pageview-Tags:</strong> Executed without restrictions <em>(reprocessed commands, consent changed from “undefined” → “true”)</em>.</p>                         |
| **Alternative B:** User interacts with the CMP banner and **denies consent to all tools**. | –                                                                          | <p><code>myAnalyticsService: true</code><br><code>myMarketingService: ncm</code></p>                                         | <p><strong>Analytics Pageview-Tags:</strong> Not re-executed (consent setting unchanged).<br><strong>Marketing Pageview-Tags:</strong> Executed with restrictions <em>(Privacy Mode Configuration; reprocessed commands, consent changed from “undefined” → “ncm”)</em>.</p> |

***

### Key Takeaways

* **No Consent Mode** (`myAnalyticsService`) runs without waiting for user consent.
* **Essential Mode** (`myMarketingService`) adapts behavior based on consent status:
  * `true` → Full tracking
  * `ncm` → Restricted tracking (privacy mode)
* Reprocessing ensures that events held in memory can be executed with the updated consent context.


---

# 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.jentis.com/developer-guide/consent-javascript-sdk/reprocessing-in-the-consent-javascript-sdk/step-by-step-use-case.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.