# 18th Sep: Package loading, Secrets, Email Batching and more ### :sparkles:New and noteworthy ### Browser package loading When designing the loading mechanism for our browser SDK, we ensured that channels would only load after a user was created and JavaScript was fully loaded. However, as our number of partners increased, we encountered situations where multiple EdgeTag instances were created on the same site, each with its own browser packages. This led to issues where one package would load correctly, while others would not, causing some browser events to fail to fire.\ \ We're pleased to announce that with this release, we have addressed this problem. Now, you can have multiple EdgeTag systems on your site, and everything will work seamlessly. ### Secret handling in Cloudflare Our power users may have noticed in the past that they were unable to add more than five instances of the same channel. However, there are use cases where users want to track different flows with different pixels on their site, requiring up to ten instances of Facebook. Previously, this was not possible due to a hidden limitation on Cloudflare. We have redesigned the system so that each instance has its own secret, allowing you to create as many instances of the same channel as needed. ### Email batching We want to let our users know as soon as we detect some problems with their data stream. This means that when an event has issues, like AddToCart, or when the channel is no longer contributing, we send you an email asking you to double-check the report. As we are adding more customers, we also need to scale up our infrastructure. For this reason, we built our own queuing and batching mechanism to scale and reliably send you emails with reports. ### :zap:Improvements \[Channel] - Hide Meta Halo channel, Meta channel handles everything now \[Channel] - Added support for OneScreen.ai \[App] - Upgrade Stripe SDK to the latest version ### :book: Details Release day: 18th September 2025\ Release version: 25-34\ Edge version: 13.124.0\ SDK version: 1.30.0 --- # Agent Instructions: 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: ``` GET https://docs.edgetag.io/changelog/september-2025/18th-sep-package-loading-secrets-email-batching-and-more.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.