> ## 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. # Q3 2026 Release Notes > July – September 2026 **Zeotap Q3 2026 Release Notes** July – September 2026 **Released: July – September 2026** Q3 made alerting configurable instead of fixed, gave audiences an explicit timezone, let you see the exact payload a destination will receive before you activate it, and opened the platform to AI assistants. Six new integrations shipped, and Collaborate arrived as a privacy-safe clean room. ## Alerting and monitoring **Configurable alert management** **Release Date:** Q3 2026 **Alerts you cannot switch off are alerts people learn to ignore.** Every alert is now visible and configurable under **Admin → Alerts & Notifications**. Switch an alert on or off, edit its condition, change who receives it, set a delay threshold, and scope it to specific sources, audiences or folders. **What you get:** * Ten default alerts across Sources and Audiences, all editable * Recipients managed per alert, rather than one global list * Delay thresholds, so a job that is routinely slow does not page anyone * Scoping, so a noisy source does not drown out the rest [Alerts and notifications →](https://docs.zeotap.com/articles/admin-customer/alerts-and-notifications.md) ## Audience builder **Timezone-aware audiences** **Release Date:** Q3 2026 **"Everyone who purchased yesterday" means something different in Milan than it does in UTC.** Every audience now carries an explicit timezone, set on the create screen and shown at the top of the builder. It applies to every calendar-anchored condition — exact day, exact week, between dates — and any single condition can override it independently. **Two new operators** arrive with it: *Time of day is between \[start] and \[end]*, and *Time of day is \[time]* with an optional tolerance. Both make daypart and flash-sale targeting expressible without arithmetic. **Worth knowing:** * **New audiences default to your system timezone rather than UTC.** Audiences saved before this change stay on UTC and are unaffected. * Relative filters such as "within the last N hours" were never timezone-dependent and have not changed. [Using timezones in the audience builder →](https://docs.zeotap.com/articles/segment-customer/using-timezones-in-the-audience-builder) ## Destination confidence **Payload preview for destination mappings** **Release Date:** Q3 2026 **The first time you find out a mapping is wrong should not be when the destination rejects it.** A **Generate Preview** button on the mapping screen pulls a real record from your catalogue and renders the exact payload Zeotap would send — mapped identifiers, nested object lists, enrichers and destination-specific attributes included. Check the mapping before you activate it, not after. Connection testing was added to the same screen later in the quarter, so credentials and payload can be validated in one place. Works for both batch and real-time destinations. [Payload preview →](https://docs.zeotap.com/articles/integrate-customer/payload-preview-for-destination-mappings.md) **Destination metrics on more platforms** **Release Date:** Q3 2026 Platform-reported metrics — audience size, CPM, match rate and TTL — now come back from **The Trade Desk Data Monetisation, Adform DMP, Snapchat, Pinterest and LinkedIn**, surfaced in the audience and Insights views alongside the destinations already supported. [Audience insights →](https://docs.zeotap.com/articles/segment-customer/audience-insights.md) ## Consent and governance **Channel consent rules rebuilt** **Release Date:** Q3 2026 **The consent query builder could not express the rules some teams actually needed.** The channel consent rule builder has been rebuilt to match the audience builder, which unlocks the complex nested consent logic the previous builder could not represent. The consent rule listing has been redesigned at the same time. **The change most people will notice:** applied channel consent rules are now visible inside the destination settings of both audiences and journeys — so you can see which consent rules are in force at the point of activation, rather than having to go and look them up. [Consent →](https://docs.zeotap.com/articles/protect-customer/consent) **Restrict on channels, and restricted attributes in filters** **Release Date:** Q3 2026 A catalogue field can now carry a **Restrict on Channels** setting controlling which activation channels are allowed to receive it. Restricted attributes are also filtered out of the audience and journey filter pickers, so a field that cannot be activated no longer appears as though it can. Destination permissioning shipped alongside, extending the Q2 access-rules model. [Restrict on channels →](https://docs.zeotap.com/articles/unify-customer/restrict-on-channels) ## Data integrity **NCE event timestamp** **Release Date:** Q3 2026 **A delayed batch should not be able to overwrite newer data.** You can now map a standard field, `nce_event_timestamp`, to your own business event time. Ingestion compares timestamps before writing and skips any record older than what is already stored — so a late batch, a backfill, or a redelivered message cannot silently overwrite a more recent value. **Worth knowing:** * It is optional and set per source. Sources that do not map it behave exactly as before. * It uses your business event time, not the time the record arrived. ## Journeys **Delete a single node without pausing the journey** **Release Date:** Q3 2026 **Removing one step used to mean rebuilding the sequence around it.** Hover a node, click the cross, confirm — and the journey re-stitches itself. A sequence of A → B → C → D becomes A → C → D with the connections rebuilt automatically. It works on **live journeys, with no need to pause first**. Branch and True/False nodes still require Cut Branch, because removing one changes the shape of everything downstream. [Add or delete a node →](https://docs.zeotap.com/articles/orchestrate-customer/add-or-delete-a-node.md) ## Security **Two-factor authentication** **Release Date:** Q3 2026 Two-factor authentication is available at login. **Worth knowing:** 2FA is currently prompted on **every** login. There is no configurable re-prompt window yet. [Your first login →](https://docs.zeotap.com/articles/admin-customer/your-first-login-to-the-zeotap-cdp-platform.md) ## AI **Zeotap MCP** **Release Date:** Q3 2026 **Ask your CDP a question from the assistant you already use.** Zeotap MCP connects an organisation to Claude, ChatGPT, or any MCP-compatible assistant. Ask about schema, data quality, fill rate and trends; get visibility into audiences, journeys, destinations, sources and identity configuration; and use the journey and audience recommender tools to think out loud against your own data. **Worth knowing:** * It is **read-only**. Nothing can be changed through it. * Access follows each user's existing permissions. No module access in the platform means no access through MCP either. **Availability:** Beta, enabled per organisation on request. [Zeotap MCP →](https://docs.zeotap.com/articles/labs-customer/zeotap-mcp.md) ## Collaborate **Collaborate — privacy-safe data clean room** **Release Date:** Q3 2026 Collaborate is a clean room for working with a partner's data without either side handing over raw records. Create a partnership, map a join key, run an analysis behind privacy and activation controls, and save the result back as an audience. Every action is recorded in an activity log. Composable dataset primary keys can be used as join keys, the partner dropdown is filtered to organisations that have opted into discoverability, and the export destination list is filtered to the activation channels the publisher has configured. **Availability:** Limited. Provisioning is still being rolled out — contact Zeotap Support to discuss access. [Collaborate →](https://docs.zeotap.com/articles/collaborate-customer/collaborate.md) · [Quick start →](https://docs.zeotap.com/articles/collaborate-customer/quick-start.md) ## Unify **Object property mapping and editable field names** **Release Date:** Q3 2026 Primitive properties inside an object or list-of-object attribute can now be mapped individually, including property-to-property mapping — so you no longer have to take the whole object or nothing. Catalogue and source field names are also editable after creation, which removes the "recreate it to rename it" workaround. [FAQs about catalogue →](https://docs.zeotap.com/articles/unify-customer/faqs-about-catalogue.md) ## Integrations **New and enhanced integrations** **Release Date:** Q3 2026 | Integration | Type | What it enables | Docs | | - | - | - | - | | TikTok Events API | Destination | Server-to-server conversions across Web, App, Offline and CRM through one endpoint | [Setup →](https://docs.zeotap.com/articles/integrate-customer/tiktok-events.md) | | Smadex | Destination | Mobile DSP activation with raw or hashed device ID, IDFV and IP | [Setup →](https://docs.zeotap.com/articles/integrate-customer/smadex.md) | | Sportradar | Destination | Deliver an audience as a **suppression list** | [Setup →](https://docs.zeotap.com/articles/integrate-customer/sportradar.md) | | Adjust | Source | Installs, reattributions, sessions, events, reinstalls and uninstalls flow in automatically, mapped to User ID, App, Event, Consent and Device data | [Setup →](https://docs.zeotap.com/articles/integrate-customer/create-an-adjust-source.md) | | Meta Custom Audience | Destination | Custom audience activation on Meta | [Setup →](https://docs.zeotap.com/articles/integrate-customer/meta-custom-audience.md) | | Snowflake source | Source | **Key-pair authentication**, as an alternative to password auth | [Setup →](https://docs.zeotap.com/articles/integrate-customer/create-a-snowflake-source.md) | **Also enhanced:** * **Braze** — Rename External ID and Remove External ID actions * **Batch CEP** — an Update Batch Profiles action for bulk profile updates * **Salesforce CRM (journeys)** — OAuth connect and custom object support; the Connected App prerequisite has been dropped * **Databricks source** — personal access token and service principal authentication; Cluster and Warehouse ID are no longer required * **WhatsApp** — a new mapping flow, with media support * **The Trade Desk CRM** — delta support * **Pinterest CAPI** — select multiple source fields for one destination field * **Microsoft Ads Customer Match** — migrated to the REST API * **Destination mapping** — optional delta key selection, and configurable delta sync at the journey-destination level The [integrations master list](https://docs.zeotap.com/articles/integrations-master-list-publication/integrations-master-list) has been re-synced against the internal source of truth, and the remaining Beta tags removed. [Braze →](https://docs.zeotap.com/articles/integrate-customer/braze-1.md) · [Batch CEP →](https://docs.zeotap.com/articles/integrate-customer/batch-audience-management.md) · [Salesforce CRM →](https://docs.zeotap.com/articles/integrate-customer/salesforce-crm) · [WhatsApp →](https://docs.zeotap.com/articles/integrate-customer/whatsapp.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.