Documentation

Treasure Data

Suggest Edits

📘

This integration is currently in beta. Contact your MetaRouter support team to get started.

What Is Treasure Data?

Treasure Data is a customer data platform (CDP) that helps organizations collect, unify, and analyze customer data from multiple sources to create a comprehensive view of their customers. The platform enables businesses to make data-driven decisions by integrating and analyzing data in real time, providing insights for personalized marketing, sales, and customer experience strategies. With robust data integration capabilities, Treasure Data supports various data sources, including mobile apps, websites, CRM systems, and IoT devices. Additionally, it features advanced tools for segmentation, data privacy compliance, and customer journey mapping, making it a valuable asset for enterprises looking to optimize customer engagement.

What are the benefits of integrating MetaRouter with Treasure Data?

  • Enhanced Data Privacy: Through configurable data transformations, including hashing and field-level controls, the integration helps manage sensitive information securely.
  • Data Transformation and Enrichment: Customizable field mappings and transformations ensure that incoming data aligns with Treasure Data’s schema, improving data quality and consistency.
  • High-Speed Data Processing: Enables swift data ingestion into Treasure Data, facilitating prompt access to customer insights and enhancing the responsiveness of analytics.

Capabilities and Considerations

  • Multi-Source Data Collection: MetaRouter collects data from web and mobile applications, CRMs, and other systems, routing it to specified databases and tables in Treasure Data as per the DATABASE_ID and TABLE_ID parameters in the ingestion API. With secure API key authentication and JSON-formatted payloads, it ensures compatibility with Treasure Data’s schema requirements. Data mapping includes attributes like messageId, userId, and event, and flattens nested fields (context, traits) for standardized ingestion.
  • Low-Latency Ingestion: Treasure Data’s Data Ingestion API supports quick data transfer to Treasure Data, allowing for prompt access to customer information for real-time analysis. Automated routing through the playbook further reduces latency by eliminating manual steps in the data flow.
  • Data Unification: MetaRouter consolidates data from multiple sources, aiding identity resolution in Treasure Data by unifying user data across channels. Playbook mapping aligns incoming data to consistent fields, ensuring cohesive customer profiles within the platform.
  • Attribute Enrichment: By routing detailed attributes (e.g., event, userId, enriched context properties) to Treasure Data, MetaRouter enables deeper segmentation and analysis. Field transformations, such as hashing properties.title to _titleHash, provide additional enrichment options aligned with Treasure Data's data processing capabilities.
  • Automated Data Routing: Using the playbook, MetaRouter automates data flow configurations, enabling efficient data transformations and workflows while optimizing ingestion setup for reduced manual input.

Limitations

  • Near-Real-Time Ingestion: While the Data Ingestion API supports low-latency data transfer, it does not guarantee instantaneous real-time ingestion. There may be minor delays depending on factors such as data volume and processing speed, which should be considered for time-sensitive applications
  • Batch Size Limitations: The streaming ingest API batch endpoint path records.in has the following limits:
    • 1-500 records
    • 1MB max record size
    • 5MB max batch size
      • If this limit is exceeded, the API will return a 422 error.

Getting Started - From Your Treasure Data Account

Getting Started - From Your MetaRouter Account

Adding a Treasure Data integration.

From the integration library, add a Treasure Data integration. Then, fill out the Connection Parameters:

Connection ParameterDescription
ENDPOINTEndpoint based on your region. Please see above.
API_KEYAPI key generated from your Treasure Data account.
DATABASE_IDThe name of your database.
TABLE_IDThe name of your table.

Event Mappings

MetaRouter provides all of the event mappings that Treasure integrations typically require. You may add custom events, parameters or mappings in accordance with Treasure Data’s API documentation.

Global

Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.

Output KeyDescriptionExpected Input
idString: Unique identifier for the message.messageId
user_idString: Unique identifier for the user.userId
previous_idString: Identifier for the previous session or user.previousId
anonymous_idString: An identifier for an anonymous user.anonymousId
original_timestampTimestamp: Timestamp when the original event occurred.originalTimestamp
received_atTimestamp: Time when the event was received by the system.receivedAt
sent_atTimestamp: Timestamp when the data was sent to Treasure Data.sentAt
timestampTimestamp: The primary timestamp for when the event took place.timestamp
integrationsJSON Object: Specifies enabled integrations for the event.integrations
typeString: Type of event being tracked (e.g., "track", "identify").type
eventString: Name of the event.event
nameString: Name associated with the event or action.name
categoryString: Category of the event or content.category
_titleHashString (MD5 Hash): MD5 hash of the event title.properties.title
context_Various: Fields within context are flattened with a context_ prefix.context
traits_Various: Fields within traits are flattened with a traits_ prefix.traits
properties_Various: Fields within properties are flattened with a properties_ prefix.properties

Additional Treasure Data Documentation

Data Ingestion API

Updated about 1 month ago