> 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/may-2026/28th-may-new-audiencesense-dashboard-blotout-consent-banner-and-more.md). # 28th May: New AudienceSense Dashboard, Blotout Consent Banner and more ### :zap:Improvements * \[Channel] - When re-importing historical events into `Klaviyo`, each event now carries its original timestamp. Previously, `backfilled` events all landed with today's date, making your historical data unreliable. Your email timelines will now accurately reflect when things actually happened. * \[Channel] - The `Tatari` browser pixel now correctly identifies and fires events for New Customers (NC) and Returning Customers (RC), enabling smarter segmentation and more accurate campaign attribution for TV ad measurement. * \[Channel] - You can now instantly see whether Enhanced Conversions for Leads is active on your `GoogleAds` account, right inside the EdgeTag settings panel. No more second-guessing whether a prerequisite is met — the status shows up live as enabled or disabled the moment you toggle the flag. ### :bug: Fixes * \[Channel / Shopify] - On `Shopify` stores, `GoogleAds` click events were sending the internal iframe URL instead of your actual storefront URL. This meant Google was attributing conversions to a sandbox URL nobody ever visits. Fixed — Google now receives the correct page URL every time. * \[Channel] **-** For New Customer and Returning Customer purchase events, `GoogleAds` was incorrectly also firing `page_view` and `view_content` events alongside the purchase. This inflated engagement metrics and muddied attribution. Those extra events are no longer sent for NC/RC purchases. * \[Channel] - Permission errors from `GoogleAds` were silently falling into an "unknown error" bucket with no alerts going out to the team. These errors are now correctly classified and routed to the event drop notification channel, so the right people are notified automatically. ### :book: Details Release day: 28th May 2026\ Release version: 26-18\ Edge version: 13.156.0\ SDK version: 1.54.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/may-2026/28th-may-new-audiencesense-dashboard-blotout-consent-banner-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.