> 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/september-2025/25th-sep-deployment-google-tag-managerand-more.md). # 25th Sep: Deployment, Google Tag Managerand more ### :sparkles:New and noteworthy #### Reduced deployment time Our platform is continually growing, and we are developing a variety of new features for you. As a result, we are using more resources, which could potentially slow down your experience when adding channels or modifying configurations. To address this issue, we have re-evaluated our deployment process to Cloudflare. We are now implementing differential deployments, which means we deploy only what is necessary and eliminate unnecessary overhead. ### Google Tag Manager Consent is difficult to implement, and getting it right is even harder. As a result, many of our customers have approached us asking whether they can use EdgeTag to integrate with all their systems, since consent has already been implemented effectively within EdgeTag. Based on this feedback, we have added support for Google Tag Manager, which is commonly used across many shops but is often not associated with consent management. Our implementation simply loads Google Tag Manager onto the site, allowing you to manage the data layer and triggers from there. {% embed url="" %} ### :zap:Improvements \[Channel] - Pinterest events are not up to date with the docs ### :bug: Fixes \[App] - Minute view in analytics is broken \[App] - Zone check is not working correctly for self-hosting tags \[Channel] - Fire native page view event for Tatari instead of a custom event ### :book: Details Release day: 25th September 2025\ Release version: 25-35\ Edge version: 13.125.0\ SDK version: 1.31.0 --- # 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/september-2025/25th-sep-deployment-google-tag-managerand-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.