You can create a regular, scheduled data export from Ometria to an AWS S3 bucket, Databricks, Google Cloud, Microsoft Azure, or an SFTP you host.
See also: Customised data export
Segment membership records track which contacts are members of a given dynamic segment, and when they enter or exit it.
The first time the export runs, you can request a snapshot of every contact currently in the segment. From the second run onwards, you receive only the changes since the last export: the contacts who have entered the segment and the contacts who have exited it.
See also: Create a dynamic segment
null - this means Ometria has no data for that field.The following fields are passed for your segment membership records:
| Field | Type | Description |
| list_id | String |
The ID of the segment this record relates to.
|
| their_id | String |
The contact's Customer ID.
|
| String |
The contact's email address.
|
|
| profile_hash | String |
A unique, encoded identifier for the contact's profile, sometimes called a profile ID.
|
| event_type | String |
The membership change type. Only present in subsequent (delta) exports. One of
|
| dt_event | Time |
The date and time the contact entered or exited the segment. Only present in subsequent (delta) exports.
|
For the full set of contact fields you can contact record export, see Data dictionary: Contact records.
Comments
0 comments
Article is closed for comments.