Event

Treasure Data Customer Data Platform (CDP) unifies data from multiple sources so that enterprises can engage customers anywhere.

Supported Features

  • Event Forwarding

Prerequisites

To set up the Treasure Data integration, you will need your Treasure Data API Key and the database name and table you want to write data to.

See Treasure Data’s documentation for help finding your API Key. Consult your Treasure Data account manager if you are unsure of your database/table name.

Supported User Identities

mParticle will forward the following IDs to Treasure Data:

  • Email
  • GAID (Google Advertising ID)
  • IDFA (Apple Advertising ID)

Data Processing Notes

Treasure Data will not accept data more than a week old.

Storage Format

Treasure Data will initially store mParticle data as a two-column table. The first column contains a timestamp, and the second contains the raw JSON data received from mParticle. Further schema can be applied to the data within Treasure Data. See the Treasure Data documentation for more information.

Supported Events

  • App Event
  • Application State Transition
  • Attribution
  • Commerce Event
  • Error
  • Opt Out
  • Push Subscription
  • Screen View
  • Session Start / End
  • User Identity Change

Configuration Settings

Setting Name Data Type Default Value Description
Treasure Data API Key string Secret key to use the API, provided by your account manager.
database name string database name of Treasure Data which the data is imported to.
table name string table name for Treasure Data which the data is imported to.