These are the Treasure Data features and improvements being released in April 2020. Submit any product feature requests to feedback.treasuredata.com.



You can also view a video summary of our April releases.

Viewing Workflow History for Master Segments and Activations

Although master segment and activation workflows are system-defined and are not editable, in certain cases a you might want to view the workflow history for purposes of refining the master segment or troubleshooting some other issue related to the master segment population. Treasure Data now enables you to view the workflow history of master segments in the Data Workbench and activations in the Audience Studio. For more details, see Viewing Master Segment Workflow History and Viewing Activations Workflow History.

Workflow Project Level Permissions (Beta)

Project-level permissions add a granular level of permission capability that allows administrators to manage and assign permissions at the individual workflow project level while still having the flexibility to assign global workflow permissions. While all permissions can be viewed on TD Console, individual project-level permissions are only supported through APIs. To participate in this beta release, contact your Customer Success representative.

Data Connectors Released

Dropbox Export Integration (Beta)

Treasure Data supports exporting to Dropbox enabling you to send data from TD to this data storage platform. You can export your data as a CSV or TSV file to your folder on Dropbox for storage and collaboration. To participate in the Dropbox Beta, contact your Treasure Data Customer Success representative.

Facebook Page Insights Improvement

Treasure Data supports ingesting the following Facebook Page Insights data types—Page Conversation participant list, Conversation Messages, and Comments. Learn about Facebook Page Insights.

Gigya Import Integration (Alpha)

Treasure Data supports ingesting data from the SAP Data Cloud Platform (formerly Gigya). The Alpha connector allows you to ingest data from your account data store. To participate in the Gigya Alpha, contact your Treasure Data Customer Success representative.

ZenDesk Import Improvement

Treasure Data supports importing Chat data from Zendesk. Learn about Zendesk Imports.

Facebook Page Insights Improvement

Treasure Data supports ingesting the following Facebook Page Insights data types—Page Conversation participant list, Conversation Messages, and Comments. Learn about Facebook Page Insights.

Data Connectors Coming in April

Gigya Import Integration (Beta)

Treasure Data supports ingesting data from the SAP Data Cloud Platform (formerly Gigya). The Beta connector allows you to ingest data from your Account Data Store and supports Data Store and Profile endpoints for this platform. To participate in the Gigya Beta, contact your Treasure Data Customer Success representative. Learn more about Gigya.

Sailthru Import Integration (Beta)

Treasure Data supports importing data from your Sailthru account to better manage audiences for your campaigns. To participate in the Sailthru Beta, contact your Treasure Data Customer Success representative.

Bombora Import Integration

Treasure Data supports importing Bombora's Company Surge data. For more information on this release, contact your Treasure Data Customer Success representative.

Instagram Import Improvement

Treasure Data supports importing comments and tags data from Instagram. For more information on this improvement, contact your Treasure Data Customer Success representative.

MixPanel Using JQL Import Improvement

Treasure Data supports better management of your data ingestion from MixPanel by using JQL to specify the data. Learn about MixPanel Using JQL.

Updates

JavaScript SDK 2.3.0

Treasure Data Javascript SDK 2.3.0 is now available. The update includes a keepalive option for click tracking, which keeps the request alive during the loading of a document page. In addition, the updated version improves the global ID fetch behavior by returning a null value when the TD global ID doesn’t exist. Learn more on Github.


  • No labels