Teavaro provides profile and event level data activation.
Profile and event data can be sent as individual extracts or combined.
Profile data is usually a full extract, whereas event data would consist of the events for a selected period, for example 24h.
For data extracts we support CSV and JSONL format.
Other forms of activation include:
-
Fetching data via GraphQL API.
-
Receiving a selected events data stream.
-
Sending selected fields to API, for example identifiers, consents, and attributes.
For more information, please contact helpdesk@teavaro.com.
Profile Data
Consists of the following:
|
Data source |
Field description |
Example |
|---|---|---|
|
profiles (core data) |
owner
|
JSON
|
|
identifiers |
Identifiers include:
Each identifier is described with: name
|
JSON
|
|
device_identifiers |
Device identifiers include:
Each device identifier is described with: name
|
JSON
|
|
consents |
Consents captured from consent management providers like for example OneTrust, using the consent string and mapping it to a more descriptive list of purposes with name and value. |
JSON
|
|
attributes |
Attributes consist of aggregated events collections, for example page and product views, campaign engagements, ecommerce events; audience segments created through the audience builder, and onboarded attributes, for example socio-demographic, and next best action recommendations.
Each device identifier is described with: field_name
|
JSON
|
Event Data
Consists of the following:
|
Field name |
Description |
Example |
|---|---|---|
|
timestamp |
ISO 8601 / RFC 3339 timestamp in UTC |
|
|
transaction_id |
A unique id (UUID) per request. |
|
|
umid |
Unified marketing id (UUID) |
|
|
device |
User-agent derived information |
JSON
|
|
location |
IP address derived information |
JSON
|
|
isp |
IP address derived information |
JSON
|
|
pipeline_name |
The pipeline name |
|
|
domain |
The domain of the request. |
|
|
cv |
Custom variable data incoming with request payload. This is analytics, campaign and other tracking data for example obtained from data layer(s), query string parameters and any other local storage. |
JSON
|
|
destination |
For ClickIdentTrack calls, the destination or landing page URL. |
|