Import Data
Ingest data into Tidepool from your warehouse, CDP, or directly from actions in your App.
Ways to Integrate with Tidepool
Tidepool supports multiple approaches to data sharing. The three most common models are:
- Upload historical events using the Tidepool API
- Send data from your CDP (e.g. Segment) to Tidepool
- Submit events to Tidepool directly from your app
Check back soon for reverse-ETL and direct App integration examples.
Expected Schema for Track
Track
Reference the complete track events schema here.
Field | Live Ingest - Required | Historical Backfill - Required | Description |
---|---|---|---|
id | X | X | A globally unique ID for the event. |
user_id | X | X | An anonymized ID for the user that created the event. |
session_id | X | An anonymized session ID for the user. These will be used to link events together. | |
timestamp | X | ISO 8601 format timestamp with timezone when the event was created. | |
event_name | X | X | A descriptor for the type of event. Example values might be "user input" or "model response". |
text | The text body of the event. For LLM interactions, this is typically the text the user actually submitted (rather than the complete prompt sent to the model). These must be included to analyze LLM events. | ||
properties | An optional dictionary of metadata. |
Updated about 1 year ago