These are the Treasure Data features and improvements released during the month of May 2024.
Submit any product feature requests to treasuredata.com/contact-us.
Activation Actions enable you to run a user-defined custom workflow to execute desired actions such as data transformation, during an activation process. By using a custom workflow within the Activation process, you can extend and customize your data-handling capabilities to meet specific operational needs. Learn more about Activation Action.
When users copy any API Key from the TD Console, a modal now appears reminding the user to keep the keys secure and confidential. 
Braze is a Customer Engagement Platform that connects consumers and brands. It allows pushing of targeted ads to the consumer-ends mobile applications and websites via their SDK. Treasure Data has partnered with Braze to support Treasure Data cohort, which can be used to build segments. Braze Cohort Export Integration allows you to add or remove profiles from or to a particular cohort. Learn more about Braze Cohort Export Integration.
Because Yahoo! Japan is deprecating the version of the Ads API that was previously used for this integration, Treasure Data is releasing a new export integration to support uploading direct targeting data to Yahoo! Japan. With this integration, you can send a user’s email address, IDFA, or AAID to a targeted audience list on Yahoo!.
Note that the Yahoo! JAPAN Ads Export Integration will no longer function after the API is deprecated by Yahoo! JP on June 30, 2024. Any jobs using this previous integration need to be migrated to the V2 export integration before that date. Learn more about Yahoo! Japan Ads V2 Export Integration.
Treasure Data enables you to write job results from Treasure Data directly to Amazon S3 in parquet format. Parquet is a column-based data format that Amazon S3 supports. Learn more about Amazon S3 Parquet Export Integration.
Treasure Data is enhancing its activation templates for behavior activations. Users can duplicate an existing behavior activation and its settings, enabling them to more easily output mapping from the original activation.
Treasure Data has reduced the retention period of job result data from 90 days to 7 days effective. Customers requiring access to older job history data can review TD's Hive and Presto instructions using INSERT queries.
Learn more about TD's Data Retention Policy.
Support Hive 4 (Hive 2023.1) will be GA in May. With this release the Hive core has been upgraded to Hive 4, which includes enhanced performance and access to new Hive capabilities. Learn more about Hive 4. Hive 4 will be rolled out gradually to all customers. Once your TD account is scheduled for migration, our support team will contact your account one month in advance.
Support for Trino 423 is now GA. With this release the Presto core has been upgraded to Trino 423, which includes performance improvements, new UDFs, new SQL support, JDBC improvements, and an updated version of tzdata. Learn more about Trino 423.
Trino 423 will be rolled out gradually to all customers. Once your TD account is scheduled for migration, our support team will contact your account one month in advance.
With its commitment to continuous improvement and providing customers with a unified and streamlined security experience, Treasure Data is announcing the migration of all accounts to the new and improved Control Panel. With this migration, the legacy Control Panel will no longer be accessible to customers as of August 1, 2024.
Treasure Data is introducing a new limitation on the maximum execution time of Hive jobs. In an effort to prevent customers from running resource-consuming jobs for too long, Treasure Data will forcefully terminate Hive jobs taking 48 hours or longer. The affect on customers is limited and Treasure Data has notified customers who have submitted Hive jobs which have taken more than 48 hours in the previous 3 months.
With Journey Versions, marketers can modify their existing live journeys by creating new versions of their journey, such as changing decision points and adding and removing steps in the journey. Using Journey Versions, you avoid the risks associated with duplicating journeys; profiles already in the journey might return to the stage's beginning and could potentially receive duplicated activations. When Journey Versions is enabled in the platform, all existing journeys will automatically be changed to journey_name v1.
The API for the Yahoo! JAPAN Ads Export Integration will be deprecated by June 30th, 2024. Because of similar authentication requirements, one of its features - the Custom segment targeting, will be supported as a kaizen of the Yahoo CAPI Export Integration.