Visit our new documentation site! This documentation page is no longer updated.

Release Note 20180401

This is a summary of new features and improvements introduced in the April 1st, 2018 release. If you have any product feature requests, submit them at feedback.treasuredata.com.

Table of Contents

Audience Suite: Marketer-Friendly Access to Customer Data

We have released the documentation for Audience Suite, which is a collection of tools to provide marketer-friendly access to customer data.


Customer List

Customer Data Modeling

Segmentation

Syndication

Audience Suite: Predictive Customer Scoring

The Audience Suite now includes Predictive Customer Scoring. Use Predictive Scoring in your customer segments to assess behaviors and predict future behavior.

Collection: Website Tracking with Google AMP and Marketo Forms

The Treasure Data AMP component makes it easy to send data from AMP components.

JavaScript SDK can be now integrated with Marketo Forms.

Collection: Automatic Event Tracking for Android SDK and iOS SDK

You can now automatically track lifecycle events using the following:

Android Mobile SDK v0.1.17

iOS Mobile SDK v0.1.25

Collection: Salesforce Marketing Cloud (SFMC) Incremental Support

You can now incrementally import data from SFMC into Treasure Data using a date column.

Collection: App Annie OAuth Support

You can now authenticate through OAuth for your App Annie connection.

Output: Result Output to Salesforce Marketing Cloud (SFMC)

Now you can export data to Data Extensions within SFMC.

Output: Result Output to Twitter, Facebook, and Instagram Hashing

Now you can send hashed emails and skip automatic hashing by Treasure Data.

Output: Result Output to SFTP Completion Confirmation

You now have the ability to confirm a successful file transfer.

Security: Basic and Premium-level Audit Logs now Available

Monitor the access and use of data in your Treasure Data account by using the audit log.

The Treasure Data basic audit log (known as standard audit log) enables you to view events that occur within the last 24 hours. Users who buy the premium license can view, filter, and query the audit log. The premium audit log captures and holds an unlimited number of events.

Workflow UI: General Availability Update – Release 1st week of April

Workflow UI Phase 2 General Availability was moved from the last week in March to the first week in April. This was to accomodate a slight delay in release of View Only & Run Only Permissions.

All accounts will have access to the new Workflow UI by the end of the 1st week of April.

Workflow UI: View Only & Run Only Permissions

Manage the permissions to edit & manage workflows within the Workflow User Interface on a user-basis.

Release will occur by April 3rd. It’s accessible as a new “Global Permissions” section each user’s profile page, under the Permissions tab accessible only to admin users.

Audience Suite: Personalization API with Marketo and Google DFP

You can integrate Treasure Data’s Personalization API with Marketo and Google DoubleClick for Publishers (DFP), and return customer data in real-time, to update your segment information.

Client: Java Client Library v0.8.2

The td-client-java library, v0.8.2, is now available. This release includes a couple of bug fixes and improvements.

Console: Result Export Job Separation from Query Job

All Treasure Data accounts now run on an updated job processing framework. The update separates the internal elements of Query Execution & Result Export and represents a major milestone towards a customer-facing separation of Query & Data export processing. Eventually, you will be able to retry data exports, without having to also retry the query processing itself.

With this system migration, you might notice the following changes in the behavior of your account:

  1. An increase in query concurrency. When a job reaches the result export phase, the query engine allows for another query to be submitted if there are resources available within your Presto or Hive resource limits.

  2. For every query with a Result Export setup, two jobs are generated. As a result, you see the following in your jobs list for queries with result export setup:



  3. Full logs are split between the two jobs.

In the Presto/Hive Query Job, the end of the log indicates that the new Result Export job being created:



In the Result Export Job, you can see the related export jobs that you used to see within the Query Job:



Both jobs will fail if the result export fails. If the query fails, the result export is generated.



Finally, the query job will not show as completed, until the result export job is also completed.


Last modified: Apr 06 2018 15:53:59 UTC

If this article is incorrect or outdated, or omits critical information, let us know. For all other issues, access our support channels.