# Essential Mode Delivered Immediately

In addition to the three discussed consent settings—**Consent Mode**, **Essential Mode**, and **No Consent Mode**—we are often asked:

> “Can Essential Mode be treated like No Consent Mode for essential data, so that the fallback configuration executes immediately?”

### The Concept

In **Essential Mode**, a tool is provided only **highly limited** and/or **fully anonymized** data (no access to PII).\
From a technical perspective, this raises a valid question:\
If the essential data does not depend on the user’s consent decision, **why wait** before activating the tag?

Executing immediately would allow you to capture all events—even from bouncing users—helping to maintain a complete analytical picture.

### The Challenge

While this idea sounds straightforward, it introduces **significant technical implications**:

* In JENTIS, tags using **Essential Mode** share the **same trigger** regardless of mode.
* Changing the **moment of activation** affects **triggers** and **reprocessing**.
* If a tag is executed immediately (e.g., `track:pageview` fired at page load before consent decision) and consent is later granted, **a second pageview will not be tracked**—to prevent duplicate tracking.
* Resolving these situations is **complex** and varies for each project.

### Current Solution Status

* **No native out-of-the-box solution** exists for this use case in JENTIS today.
* Implementing this behavior requires a **custom solution** tailored to your specific setup.
* Our team can work with you to design an approach that meets your requirements.

### Looking Ahead

We are actively working on features that will make it possible to handle this scenario more efficiently and natively in the future.\
This would allow **Essential Mode** to execute immediately for essential data while still maintaining proper reprocessing and avoiding duplicate tracking.

✅ **Recommendation:**\
If **immediate Essential Mode** execution is essential for your tracking, consult with JENTIS support to implement a **custom configuration** until native support becomes available.