Treasure Destination


On this page


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 through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Supported Sources and Connection Modes

The first step is to make sure Treasure Data supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

Web Mobile Server
📱 Device-mode
☁️ Cloud-mode

To learn more about about Connection Modes and what dictates which we support, see here.

This destination requires a Device-based Connection Mode for Mobile data. Follow the steps above to ensure you have packaged the Treasure Data SDK with Segment’s.

Settings

Segment lets you change these destination settings from your Segment dashboard 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.

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account