> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/changelog/july-2025/24th-july-plugin-sorting-meta-backup-token-id-stitching-new-ui-and-more.md).
# 24th July: Plugin sorting, Meta backup token, ID stitching, New UI, and more
### :sparkles:New and noteworthy
#### Meta backup token
Your life can be pretty dynamic when you are traveling or testing your system in different browsers and countries using a VPN. Unfortunately, a side effect of this can be that Meta will invalidate your connections as a security measure. This means you may need to log back into Meta or solve a captcha. Additionally, this will result in the revocation of your connection with EdgeTag. \
\
To address this issue, we have added a backup token. You can obtain this token from your Events Manager. It will serve as a safety net until you re-authenticate Meta within EdgeTag.
{% embed url="" %}
#### Plugin sorting
When we introduced Plugins, we knew this could be a powerful feature for you to make modifications on the fly. Now, we are providing you with even more flexibility, allowing you to rearrange plugins and define how transformations or events should be triggered sequentially.
#### Connecting offline with online activities
Connecting offline and online events is one of our key focuses when thinking about the future. Previously, you needed to carry the customer EdgeTag ID in your offline storage and send it to us when sending an offline event. This is no longer necessary, as we will now automatically link your events using the email address that you provide in the offline event payload.
#### New UI sneak peek
Our user interface (UI) has remained the same for quite a while, but rest assured, we are actively working on a new version. Currently, these changes are still behind feature flags; however, we would like to provide you with a quick preview of the first page and share our vision for its future direction.
{% embed url="" %}
### :zap:Improvements
\[Channel] - Add option to disable consent handling for Google Analytics 4 and Google Ads\
\[Channel] - Allow sending all events to Impact, not just purchase\
\[App] - Add event drop detection for NC and RC events
### :bug: Fixes
\[App] - Fix deployment for storage changes\
\[Channel] - Change revenue key for Tatari
### :book: Details
Release day: 24th July 2025\
Release version: 25-26\
Edge version: 13.116.0\
SDK version: 1.22.1
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.edgetag.io/changelog/july-2025/24th-july-plugin-sorting-meta-backup-token-id-stitching-new-ui-and-more.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.