# February 2026 Release Note These are the Treasure Data features and improvements released in February, 2026. ## Engage Studio ### New Feature: Always-on Campaigns - Always-on Campaigns introduces a new campaign mode in Engage Studio that keeps email and mobile push campaigns in a live state so they can receive continuous, trigger-based activations from Customer Journey Orchestration (CJO) or recurring batch activation, instead of running as one-time batches. - This feature is designed for marketers who want to run ongoing, trigger-driven email or push notification programs, letting them manage Always-on and on-off campaigns separately, control lifecycle states (Live, Paused, Finished), and safely update content while maintaining delivery traceability via Campaign ID. - Learn more by visiting the [Always-on Campaigns](/products/marketing-cloud/engage-studio/always-on-campaigns) page. ### New Feature in Engage: Mobile Push - This release adds native mobile push campaign creation, personalization, preview, testing, and delivery (via Firebase Cloud Messaging) as a first-class channel within Engage Studio, alongside email and other channels. - Designed for marketers running multichannel journeys, it lets them define rich push content (including Liquid personalization, emojis, images, deep links, and UTM-tagged links) so they can drive users to specific in-app or in-web with more relevant notifications. - Talk to your Treasure Data account team to get started. - Learn more by visiting the [Mobile Push](/products/marketing-cloud/engage-studio/channels/mobile-push) page. ### Mobile Push Channel Campaign Management + Editor - This update adds full support for configuring, personalizing, previewing, and testing Firebase Cloud Messaging (FCM) mobile push campaigns directly in Engage Studio, alongside existing channels like email, SMS, and LINE. - Designed for marketers running multichannel journeys, it improves campaign orchestration by letting them choose message type (notification, data, silent), define tap behavior (open app, deep link, web URL), add images, validate payloads, and view delivery error logs, all in one UI. - To get started, contact your Treasure Data account team to enable Mobile Push (Firebase) configuration in Engage Studio and set up the required write-only API key and `deliveryfcm{project_id}` database for logging and analytics. - Learn more by visiting the [Mobile Push](/products/marketing-cloud/engage-studio/channels/mobile-push) page. ## AI ### Now Generally Available: Treasure Code - Treasure Code (formerly ‘tdx’) is an AI-native interface that lets technical teams operate the entire Treasure Data CDP as code—from queries and workflows to segments and journeys—through one unified command layer. - Designed for CDP and data operations teams, it translates natural-language instructions into production-ready SQL and configurations while applying code-grade governance like version control, peer review, and instant rollbacks to improve quality and control. - Getting started is easy: download the files, authenticate with your Treasure Data API Key, and start coding. - Learn more by visiting the [Treasure Code](/treasure-code) page. ### AI Foundry Agent Update: Run with End-User Permissions - This update changes AI Foundry agents so they execute with the permissions of the end user who runs the agent, rather than the original project creator. - This improves security and governance for AI Foundry users (such as data scientists and marketing operations teams) by ensuring agent actions and data/tool access respect each individual user’s actual Treasure Data access rights. - Learn more by visiting the [AI Agent Foundry](/products/customer-data-platform/ai-agent-foundry) page. ### Analysis Agent for Plazma DB (Internal Preview) - The Analysis Agent lets users ask natural-language questions on Plazma DB and receive structured summaries with visualizations, without writing SQL. - By automating schema discovery, proposing analysis plans, and running readable SQL within each user’s existing permissions, it shortens time-to-insight from days to minutes while enforcing aggregation-first, privacy-safe analysis. - This feature is now available to all Super Agent users. - Learn more by visiting the [Marketing Super Agent](/products/super-agent/about-marketing-super-agent) page. ## Integration Hub ### Snowflake Import Connector: Bulk Unload via S3 - This update enhances the Snowflake Import Connector to support bulk unload via Amazon S3, enabling high-volume data movement from Snowflake into Treasure Data. - Data engineers and analytics teams using Snowflake can now move larger datasets into Treasure Data more efficiently by following the new official connector documentation and guidance. - Learn more by visiting the [Snowflake Bulk Unloading Import Integration](/int/snowflake-bulk-unloading-import-integration) page. ### New Connector: LINE Official Account Insight Import - This new import connector pulls LINE Official Account Insight data (message delivery, followers, demographics, and interaction metrics) from the LINE Messaging API into Treasure Data for centralized reporting and analysis. - Marketers and data teams using LINE in Japan, Taiwan, and Thailand can now track LINE campaign performance, audience growth, and audience composition alongside other channels in Treasure Data. - Learn more by visiting the [LINE Official Account Insight Import Integration](/int/line-oa-insights-import-integration) page. ### Klaviyo Batch Consent API Export Connector - This update adds support for Klaviyo’s Subscription (Consent) API to the Klaviyo Batch Export Connector so you can send customer subscription statuses from Treasure Data to Klaviyo in bulk. - For marketing operations and CRM teams using Treasure Data as the source of truth for permissions, this enables high-volume, GDPR/CCPA-aware synchronization of true consent (not just list membership), helping ensure only customers with valid opt-in are targeted in Klaviyo campaigns. - Learn more by visiting the [Klaviyo Export Integration](/int/klaviyo-export-integration) page. ## Platform ### Deprecation of TLS 1.0/1.1 (Effective February 28, 2026) - Treasure Data will no longer support TLS 1.0 and 1.1 on any customer-facing network endpoints as of February 28, 2026, and all connections must use TLS 1.2 or higher. - This change improves security posture for customers’ security and IT teams by enforcing modern encryption standards, and may impact data collection from visitors using legacy browsers or clients that do not support TLS 1.2+. - To avoid service interruption, customers should ensure all systems connecting to Treasure Data (including Mobile SDK, JS SDK, and API integrations) are configured for at least TLS 1.2.