Treasure Destination

This destination is maintained by Treasure Data.

Once the Segment library is integrated with your server, toggle Treasure Data on in your Segment destinations, and add your API key (which you can find in your Treasure Data console). You will also need to specify the destination database name.

The Segment Treasure Data destination is 100% handled through our servers, so you don’t need to bundle their iOS or Android SDKs.

Table Structure

All of the data from your Segment workspace is hosted on Treasure Data database. Inside that database you will see multiple tables for each of your Segment sources, one for each of the types of data.

Every table is namespaced by the source’s name. Inside each source there are a few standard tables:

source.aliases

A table with all of your alias method calls. This table will include all of the traits you identify users by as top-level columns, for example <source>.aliases.email.

source.groups

A table with all of your group method calls. This table will include all of the traits you record for groups as top-level columns, for example <source>.groups.employee_count.

source.identifies

A table with all of your identify method calls. This table will include all of the traits you identify users by as top-level columns, for example <source>.identifies.email.

source.pages

A table with all of your page method calls. This table will include all of the properties you record for pages as top-level columns, for example <source>.pages.title.

source.screens

A table with all of your screen method calls. This table will include all of the properties you record for screens as top-level columns, for example <source>.screens.title.

source.event_name

For track calls, each event like Signed Up or Order Completed also has it’s own table, with columns for each of the event’s distinct properties.

Personas

You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false.

When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Supported Sources and Connection Modes

Before you start, make sure Treasure Data supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

Segment offers an optional Device-based Connection Mode for Mobile data going to Treasure Data, so that you can use Treasure Data features that collect data directly from the mobile device. To do this, you must package the Segment-Treasure Data mobile SDK with the Segment mobile library.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

API Write Key

You can find your write key in your Treasure Data Account Settings

Database Name

The database name you want to send data to in Treasure Data.