> 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/best-practices/how-to-switch-to-the-new-tracking-snippet.md).
# How to switch to the new Tracking Snippet
We've released a new version of the JENTIS Tracking Snippet. Your current snippet remains fully functional, but we recommend updating it soon to benefit from the latest improvements.
## What's new
The updated snippet now uses a compact two-line setup instead of the previous larger code block, improving compatibility with modern Content Security Policies, optimizing asynchronous loading, and reducing maintenance overhead. It is built for long-term robustness as browsers, privacy tools, and ad blockers continue to evolve, helping safeguard consistent data quality going forward.
## How to update
Open your DCP and navigate to the Containers menu
Click on the purple button "Update Tracking Snippet" on the container you would like to update the snippet on.
{% hint style="info" %}
Preview the updated snippet before publishing. Verify that your existing tracking still works as expected.
{% endhint %}
The next step is to publish a new version on the container.
After publishing, you will see your new container-specific tracking snippet
{% hint style="info" %}
You might need to refresh the page if the publishing of the previous step is not recognized automatically :wink:.
{% endhint %}
You can decide if you want to add an automatic pageview submit call to the snippet by ticking the "Add pageview to snippet" checkbox.
After implementing the new snippet, you can click the "Verify Configuration" button to make sure the snippet was implemented correctly.
---
# 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/best-practices/how-to-switch-to-the-new-tracking-snippet.md?ask=&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.
