> ## Documentation Index > Fetch the complete documentation index at: https://docs.zeotap.com/llms.txt > Use this file to discover all available pages before exploring further. # Q2 2026 Release Notes > April – June 2026 **Zeotap Q2 2026 Release Notes** April – June 2026 **Released: April – June 2026** Q2 turned folders into properly governed workspaces, gave audience refreshes a real schedule, made Audience Boost measurable instead of assumed, and opened up Calculated Attributes to SQL. Thirteen new or enhanced integrations shipped alongside. ## Governance and access control **Access rules** **Release Date:** Q2 2026 **Folder permissions decided who could open a folder. They did nothing about what data could flow through it.** Access Rules add the third governance layer. Source Access Rules blocklist an entire source — or individual attributes within it — from selected folders. Destination Access Rules blocklist destinations from folders. Both propagate to subfolders automatically. **What you get:** * Attribute-level control, not just source-level: block a single sensitive field without blocking the source that carries it * Rules inherit down the folder tree, so you configure once at the parent * A zero-disruption rollout: audiences and journeys that are already running keep running, but are flagged, and cannot be republished until the restricted field is removed Combined with folder access control and mandatory templates, a folder now behaves as a self-contained, governed workspace rather than a filing label. [Access rules →](https://docs.zeotap.com/articles/admin-customer/access-rules.md) · [Source access rules →](https://docs.zeotap.com/articles/integrate-customer/source-access-rules.md) · [Destination access rules →](https://docs.zeotap.com/articles/integrate-customer/destination-access-rules.md) **Audience templates** **Release Date:** Q2 2026 **A condition everyone must apply is a condition someone will eventually forget.** Audience Templates let an administrator define a condition once and apply it automatically to every audience in a folder, or across the whole account. The template renders inside the audience canvas as a locked block — visible, so builders understand what is being applied, but not editable away. **What you get:** * Define once in the Templates module, apply at folder or account level * Mandatory templates cannot be removed inside the audience builder * Templates are referenced rather than copied, so an edit reaches every audience using it * The previous audience consent rule is migrated into this model [Audience templates →](https://docs.zeotap.com/articles/segment-customer/audience-templates.md) **Deeper folder nesting** **Release Date:** Q2 2026 The subfolder depth limit has been raised, so larger teams can mirror their real structure instead of flattening it to fit. ## Audience activation **Audience scheduler** **Release Date:** Q2 2026 **"Refresh daily" was a setting you had to trust. Now it is a schedule you can read.** Audiences get explicit refresh schedules, with recurring cadences, one-time pushes, and a "push now, then follow the schedule" option for when you need data moving immediately but want it maintained afterwards. **What you get:** * Recurring cadences, plus a one-time push for ad-hoc activation * A **Next Fire Time** column, so you can see when an audience will refresh rather than inferring it * Warnings on destinations that are expiring or have expired **Availability:** Generally available. The **hourly** cadence must be enabled for your account — contact Zeotap Support if you need it. [Audience scheduling →](https://docs.zeotap.com/articles/segment-customer/audience-scheduling.md) **Audience Boost — measure the uplift, don't assume it** **Release Date:** Q2 2026 **Enrichment that you cannot measure is enrichment you cannot justify.** Audience Boost now creates two audiences in the destination platform: the boosted audience, and a seed audience built from your first-party data alone. Running both means the uplift is measurable in the platform's own reporting, with no manual A/B setup. **What you get:** * A benchmark seed audience created automatically alongside the boosted one * A boosted-only mode, if you do not want the seed audience created * Boost now sends multiple identifiers per user, and works with the multi-attribute action [Audience Boost →](https://docs.zeotap.com/articles/segment-customer/audience-boost.md) **Activation metrics and destination cards** **Release Date:** Q2 2026 **The destination knows your match rate. Until now you had to go and ask it.** Platform-reported metrics are surfaced inside Zeotap. The new Activation Metrics tab carries an identifier-increment uplift badge, and each destination card opens a detail panel showing the audience name and ID, the mapping used, and a per-identifier breakdown. [Audience insights →](https://docs.zeotap.com/articles/segment-customer/audience-insights.md) ## Journeys **Concurrent entry** **Release Date:** Q2 2026 **One user, one journey, one time — until that was the thing standing in your way.** Concurrent entry lets the same user be active in a journey more than once at the same time, which matters for order-level or transaction-level journeys where a second event should not wait for the first to finish. **Worth knowing:** with concurrent entry switched **off**, a re-trigger while the user is still in the journey is dropped, not queued. [Add concurrent entry →](https://docs.zeotap.com/articles/orchestrate-customer/add-concurrent-entry.md) **Wait for Condition node** **Release Date:** Q2 2026 **A delay waits for the clock. Sometimes you need to wait for the customer.** The Wait for Condition node holds a user at a point in the journey until a profile attribute updates or an event fires, within a maximum wait window you set. Users who qualify continue; users who do not are dropped when the window expires, and remain visible in analytics. The common case it solves: suppress the follow-up send to anyone who has already converted, without building a parallel journey to catch them. [Wait for Condition →](https://docs.zeotap.com/articles/orchestrate-customer/wait-for-condition.md) **Journey templates** **Release Date:** Q2 2026 Journey Templates arrive in the Templates module, applying the same define-once model to journeys that Audience Templates apply to audiences. [Journey templates →](https://docs.zeotap.com/articles/orchestrate-customer/journey-templates.md) ## Calculated attributes **SQL calculated attribute editor** **Release Date:** Q2 2026 **Some attributes cannot be expressed in a form builder, no matter how many dropdowns it has.** The SQL editor lets you write the attribute directly, with a **Test Query** preview so you can check the result before saving, and an in-editor help guide for the available functions. It unblocks aggregations the form builder was never able to express. Calculated attributes can also now be saved as drafts, and paused and resumed. **Availability:** Beta, enabled on request. Contact Zeotap Support to have it switched on for your account. [Add a calculated attribute →](https://docs.zeotap.com/articles/unify-customer/add-a-calculated-attribute.md) ## Data modelling **Complex and nested NCE joins** **Release Date:** Q2 2026 Non-customer entity data with nested relationships can now be used directly in audiences, journeys and destination mappings, rather than being flattened first. The JavaScript enricher was extended at the same time, so it can transform any catalogue attribute rather than a restricted set. [Objects, list of objects and NCE support →](https://docs.zeotap.com/articles/segment-customer/object-list-of-objects-and-nce-support-in-destination-upload.md) ## Labs **Labs — AI Playground and Audience Recommender** **Release Date:** Q2 2026 Labs is a new module for capabilities that are ready to use but still evolving. It launches with **AI Playground** and **Audience Recommender**. **Availability:** Permissioned — access is granted per organisation. [Labs →](https://docs.zeotap.com/articles/labs-customer/labs.md) · [AI Playground →](https://docs.zeotap.com/articles/labs-customer/ai-playground) · [Audience Recommender →](https://docs.zeotap.com/articles/labs-customer/audience-recommender.md) **Observability Hub** **Release Date:** Q2 2026 **When an audience lands late, the first question is always whether it is late or stuck.** The Observability Hub reports audience and destination run health in one place: SLA and refresh-delay flags, a run history side panel, and a per-destination duration breakdown that shows where the time actually went. **Availability:** Enabled per organisation. [Observability Hub →](https://docs.zeotap.com/articles/labs-customer/observability-hub.md) ## Integrations **New and enhanced integrations** **Release Date:** Q2 2026 | Integration | Type | What it enables | Docs | | - | - | - | - | | Amazon Conversions API | Destination | Server-to-server conversion events, with OAuth onboarding | [Setup →](https://docs.zeotap.com/articles/integrate-customer/amazon-conversions-api.md) | | Microsoft Conversions API | Destination | Server-to-server conversion events to Microsoft Advertising | [Setup →](https://docs.zeotap.com/articles/integrate-customer/microsoft-capi.md) | | Batch CEP | Destination | Send audience identifiers and custom attributes to Batch | [Setup →](https://docs.zeotap.com/articles/integrate-customer/batch-audience-management.md) | | Braze Object Sync | Journey action | Sync object data to Braze from inside a journey | [Setup →](https://docs.zeotap.com/articles/integrate-customer/braze-journey-action.md) | | Hello Charles | Destination | Contacts, tags and custom properties for WhatsApp activation — **Beta** | [Setup →](https://docs.zeotap.com/articles/integrate-customer/hello-charles.md) | | The Trade Desk Data Monetisation | Destination | Monetise segments through The Trade Desk, with CPM values on an audience — **Beta** | [Setup →](https://docs.zeotap.com/articles/integrate-customer/ttd-data-monetisation.md) | | Active Agent (Virtual Minds) | Destination | Activate segments, and create segments via a shared attribute, with CPM support | [Setup →](https://docs.zeotap.com/articles/integrate-customer/active-agent-virtual-minds.md) | | Decentriq | Destination | Send segments into a data clean room for privacy-safe collaboration | [Setup →](https://docs.zeotap.com/articles/integrate-customer/decentriq.md) | | Talon.One Audience | Destination | Sync audiences into Talon.One for promotions and loyalty | [Setup →](https://docs.zeotap.com/articles/integrate-customer/talon-one-audience.md) | | Dynamic Yield (real-time) | Destination | Real-time personalisation alongside the existing CSV upload | [Setup →](https://docs.zeotap.com/articles/integrate-customer/dynamic-yield-realtime.md) | | Eloqua | Journey destination | Activate journeys into Oracle Eloqua | [Setup →](https://docs.zeotap.com/articles/integrate-customer/eloqua.md) | | Appademic S3 | Destination | Deliver audience files to Appademic | [Setup →](https://docs.zeotap.com/articles/integrate-customer/appademic-s3.md) | | Inxmail Audience | Destination | New **Upload Recipients to a list** action | [Setup →](https://docs.zeotap.com/articles/integrate-customer/inxmail-audience.md) | **Also enhanced:** * **Snowflake source** — column-based delta, so only changed rows are pulled * **Databricks source** — setup documented end to end * **PubMatic Publisher** — delta uploads and a disassociate action * **Snapchat** and **Yahoo Ads** — moved to OAuth authentication * **Google Cloud Storage** — a `_success` file is now written once all data has been pushed, so downstream jobs have a reliable completion signal [Set up a Snowflake source →](https://docs.zeotap.com/articles/integrate-customer/create-a-snowflake-source.md) · [Set up a Databricks source →](https://docs.zeotap.com/articles/integrate-customer/set-up-a-databricks-source.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.