# September 2026 Release Note These are the Treasure AI features and improvements released in September, 2026. ## AI Studio ### New Feature: Treasure AI Voice Connector for AI Studio *Posted on: Sep 02, 2026* - AI Studio now connects to Treasure AI Voice through the same Connector/Connection model as Databricks, Snowflake, GitHub, and Treasure Data CDP, so an agent can read your meeting recordings, AI summaries, action items, and speaker-separated transcripts directly in a chat. - Designed for sales teams and anyone who runs meetings, it turns conversations Treasure AI Voice has already captured into working material — drafting a follow-up from this morning's client call, or pulling every commitment made across a week of conversations — without exporting a file. - The connection is read-only and inherits your Treasure AI Voice role: a Regular User's agent reads only that user's own recordings and an Enterprise Admin's reads the whole organization, and no agent can delete a recording, edit its tags, or start an export. - Learn more by visiting the [Connect Treasure AI Voice](/products/ai-studio/connections/ai-voice) and [Connections](/products/ai-studio/connections) pages. ### New Feature: Slack Connector for AI Studio *Posted on: Sep 03, 2026* - AI Studio agents can now search, read, and post Slack messages on your behalf, across the channels, direct messages, threads, and files your own Slack account can see. - Designed for teams whose decisions and context live in Slack, it lets an agent recover an answer from months of conversation, summarize a thread alongside your CDP data, and post the result back to the channel that needs it. - The agent acts as the member who connected, reading only what that person can read and posting, editing, and deleting under their name, so enabling the connector grants write access that cannot be narrowed per member or per channel. - Learn more by visiting the [Connect Slack](/products/ai-studio/connections/slack) and [Connections](/products/ai-studio/connections) pages. ## Engage Studio ### New Feature: Link Shortening and Click Tracking for SMS Campaigns *Posted on: Sep 08, 2026* - Engage Studio now supports link shortening and click tracking for SMS One-off and Always-On Campaigns, helping marketers reduce message length and measure engagement with links in their SMS messages. - Enable **Use TD shortened URL** at the campaign level to replace eligible HTTPS URLs with shorter Treasure AI links. Shortened links use the `t6e.ai` domain, are generated uniquely for each recipient when the campaign is sent, and remain active for 90 days. - Enable **Link Click Tracking** in workspace settings to record click events asynchronously in your Treasure Data account. Where detection is available, automated requests are identified with the `suspected_bot` field. - Click tracking requires link shortening; UTM parameters alone do not create native Engage click events. Link shortening, click tracking, and UTM tracking can be used together, with UTM parameters continuing to support attribution in analytics platforms such as Google Analytics and Adobe Analytics. - Learn more by visiting the [Shorten links in SMS campaigns](/products/marketing-cloud/engage-studio/channels/sms/shorten-links-in-sms-campaigns) and [Track clicks in SMS campaigns](/products/marketing-cloud/engage-studio/channels/sms/track-clicks-in-sms-campaigns) pages. ### Enhancement to Subscription Events: AlwaysOn Campaign Attribution *Posted on: Sep 14, 2026* - The `subscription_events` table now records campaign attribution for unsubscribes from AlwaysOn email campaigns, so downstream analysis can connect each unsubscribe to the campaign that sent the message. - A new `campaign_model` field identifies whether the campaign is a one-off `Campaign` or an `AlwaysOnCampaign`, allowing consumers to distinguish IDs from the two campaign types. - Existing records remain compatible: records written before this enhancement do not have the new field, and template or test sends have no campaign attribution. - Learn more by visiting the [Subscription Events Table](/products/marketing-cloud/engage-studio/channels/email/subscription-events-table) page. ### Enhancement to Test Email Subjects: Automatic [TEST] Prefix *Posted on: Sep 15, 2026* - Engage Studio now automatically adds a `[TEST]` prefix to the subject line of email messages sent with **Send Test**, making test messages immediately recognizable in recipients' inboxes. - Designed for marketers and reviewers who validate email content, the prefix makes it easier to distinguish test messages from live campaign emails and reduces confusion during review. - The prefix is applied only to test email sends; live campaign subject lines remain unchanged. - Learn more by visiting the [Engage Content Creation](/products/marketing-cloud/engage-studio/channels/email/engage-content-creation) page. ## Treasure AI Voice ### Enhancement to Treasure AI Voice CDP Export *Posted on: Sep 03, 2026* - Treasure AI Voice CDP exports now support recurring schedules and include an `updated_at` timestamp, enabling incremental processing and downstream deduplication. - Learn more by visiting the [Treasure Data CDP Integration](/products/ai-voice/cdp-integration) and [Administrator Guide](/products/ai-voice/administrator-guide) pages. ## Data Workbench ### New Feature: DROP TABLE Support for Hive *Posted on: Sep 01, 2026* - The Hive query engine now supports the `DROP TABLE` statement, so data engineers can delete tables directly using HiveQL — completing the basic table lifecycle alongside the `CREATE TABLE` support added in July — without switching to Trino. - Learn more by visiting the [DROP TABLE Statement Syntax](/products/customer-data-platform/data-workbench/queries/sql-reference/drop_table) page. ### New Feature: Table and Column Comments in Trino *Posted on: Sep 09, 2026* - Data Workbench's Trino query engine now supports table and column comments in SQL, including comments in `CREATE TABLE` and `ALTER TABLE ... ADD COLUMN` statements and updates through `COMMENT ON TABLE` and `COMMENT ON COLUMN`. - Designed for data engineers and analysts, this capability lets you keep business context with your schemas so teammates and AI tools can interpret datasets more accurately. - The system-managed `time` column cannot be assigned a custom comment. ## Integration Hub ### Enhancement to Salesforce Marketing Cloud V2 Export Connector *Posted on: Sep 02, 2026* - The Salesforce Marketing Cloud V2 Export connector now supports the Add operation, which inserts only records whose primary key does not already exist in a Data Extension. - Designed for marketers and integration engineers who add new audience members to Salesforce Marketing Cloud, Add preserves existing Data Extension records by skipping matching primary keys rather than updating them. - Add uses Salesforce Marketing Cloud's Asynchronous API and requires the target Data Extension to have a primary key; Treasure AI automatically enables the asynchronous API when you select Add in the Console. - Learn more by visiting the [Salesforce Marketing Cloud V2 Export Integration](/int/salesforce-marketing-cloud-v2-export-integration) page. Data Operation menu in the Salesforce Marketing Cloud V2 Export connector showing Add, Upsert, and Replace options ### New Feature: Asynchronous Delivery for LINE OA Streaming Import *Posted on: Sep 08, 2026* - LINE OA Streaming Import can now return a `200 OK` response as soon as it accepts and validates a webhook, then write its raw and event data in the background to help avoid LINE Messaging API timeouts when data delivery is delayed. - Designed for teams that use a webhook relay to connect LINE Official Account events to Treasure AI and experience delivery timeouts, the per-source **Return response immediately (asynchronous delivery)** setting is off by default and lets you choose faster webhook responses where avoiding timeouts outweighs the risk of a lost event. - When asynchronous delivery is enabled, `200 OK` confirms that the connector accepted the webhook rather than that its data was written; a later background delivery failure or connector restart can result in an unrecoverable lost event. - Learn more by visiting the [LINE OA Streaming Import Integration](/int/line-oa-streaming-import-integration) page. ### New Feature: Airship Channels Import *Posted on: Sep 08, 2026* - The Airship Import Integration now supports Channels as a data source, so you can import every channel in a project or retrieve one channel by its Channel ID. - Designed for teams that need device-level audience data, channel imports bring Airship channel information such as opt-in state, tags, and attributes into Treasure AI for analysis. - Select **Channels** as the data source in the Console and optionally enter a Channel ID to import a single channel; existing Reports, Named Users, and Static Lists imports continue to work unchanged. - Learn more by visiting the [Airship Import Integration](/int/airship-import-integration) page. ## Real-Time ### New Feature: Real-Time Identity Log Tables *Posted on: Sep 14, 2026* - Real-Time now records its identity decisions to two queryable tables: `validation_failures`, listing key/value pairs on an incoming event that failed validation and were excluded from stitching, and `id_changes`, which now also records the IDs evicted when an event stitches to a profile holding 200 associations. - Merge rows in `id_changes` now report the incoming IDs that triggered the merge in `current_id_attributes`, separately from the profile's full association set in `key_values`, so you can tell which ID caused a profile to merge rather than only that it did. - Identity logging is on for every instance with no opt-in required, and live traffic is never blocked: an event carrying an invalid key is still processed, so the log table is the only place a tracking misconfiguration surfaces. - Both tables are ingested rows that persist indefinitely by default, so set an expiration period on them to match your investigation window. - Learn more by visiting the [Real Time Identity Log Tables](/products/customer-data-platform/real-time/real-time-identity-log-tables) page. ### Enhancement to Real-Time Observability Event Tracking *Posted on: Sep 14, 2026* - The reserved `td_rt_tracking_id` column now reaches the `id_changes` and `validation_failures` tables in addition to `activations`, so one tracking ID follows a single event across its activation, identity, and validation outcomes. - Attaching the column stays optional, and events without it behave exactly as before. - Learn more by visiting the [Real Time Observability Event Tracking](/products/customer-data-platform/real-time/real-time-observability-event-tracking) page. ## Composable CDP ### New Feature: Snowflake Query Tags in Composable Audience Studio *Posted on: Sep 02, 2026* - Composable Audience Studio now sets a structured, JSON-formatted Snowflake `QUERY_TAG` on the segmentation, activation, profile lookup, validation, metadata, and metering queries it runs on your Snowflake account, recording which application ran the query, which parent segment, segment, or activation it belongs to, and what kind of operation it was. - Designed for data teams that monitor Snowflake usage, query tags let you separate Composable Audience Studio workloads from the rest of your Snowflake activity, attribute warehouse compute costs to individual audiences, segments, and activations, and set up monitoring or chargeback directly in Snowflake's query history. - Query tagging requires no configuration — tags appear automatically in `SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY`, where you can parse them with Snowflake's JSON functions and filter on the fixed application identifier `TreasureAudienceStudio`. - Learn more by visiting the [Snowflake Query Tags](/products/customer-data-platform/composable-cdp/audience-studio/snowflake/query-tags) page. ## Treasure Workflow ### Enhancement to Workflow Templates with the ${json:...} Placeholder *Posted on: Sep 09, 2026* - Treasure Workflow templates now support the `${json:...}` placeholder, which evaluates a JavaScript expression and stores the result in the task configuration with its JSON type (string, number, object, array, boolean, or null), while the `${...}` placeholder always stores the result as a string. - For example, a task that sends a number or an array in the JSON body of an `http>` request no longer needs to write the whole body as one manually quoted string. - Write the placeholder as the whole value, such as `count: ${json:count}`. - Learn more by visiting the [Calculating Variables](/products/customer-data-platform/data-workbench/workflows/calculating-variables) page. ### Enhancement to Parallel Task Execution with the Eager Option *Posted on: Sep 09, 2026* - The `_parallel` option of Treasure Workflow now supports an `eager` option, which starts the next task as soon as a running task finishes instead of running tasks in fixed groups of the `limit` size. - Designed for workflows whose parallel tasks have uneven run times, `eager: true` keeps the number of running tasks at the configured `limit`, so a single slow task does not delay the start of the remaining tasks. - A failed task does not block the other tasks in an eager group, so the remaining tasks run to completion and only the failed tasks run when the attempt is resumed. - Set `eager: true` together with `limit` in the `_parallel` configuration, and workflows that do not set `eager` keep the same behavior as before. - Learn more by visiting the [Parallel Task Examples for Treasure Workflow](/products/customer-data-platform/data-workbench/workflows/parallel-task-examples-for-td-workflow) page.