Drift: Import Activity Data
Importing user and activity data from Drift results in new users or existing user profiles supplemented with Drift conversation data. You can use this data to build and refine your existing Lytics audiences to power better, cross-channel campaigns.
Integration Details
- Implementation Type: Client-side
- Implementation Technique: REST API and/or Webhooks
- Frequency: Batch and/or Real-time
- Resulting data: User profiles and Content
This integration uses Drift's Conversation API to import conversations. Once the job is started, it will:
- Retrieve conversations from Drift
- Retrieve contacts assocatied with each conversation.
- Retrieve messages associated with each conversation.
Fields
The following fields are included in the default mapping of the drift_contacts stream:
| Source Field | Lytics User Field | Description | Type |
|---|---|---|---|
| city | city | City | string |
| contact_id | dr_contact_id unique id | Drift Contact ID | string |
| country | country | Country | string |
| email(email) | email unique id | string | |
| emaildomain(email) | emaildomain | Email Domain | string |
| employer | dr_employer | Employer | string |
| epochms(start_date) | dr_start_date | Drift Start Date | int |
| first_name | first_name | First Name | string |
| full_name | name | Full Name | string |
| last_name | last_name | Last Name | string |
| set(split(tags, ",")) | dr_tags | Contact Tags | []string |
| state | state | State | string |
| title | dr_title | Title | string |
The following fields are included in the default mapping of the drift_conversations stream:
| Source Field | Lytics User Field | Description | Type |
|---|---|---|---|
| contact_id | dr_contact_id unique id | Drift Contact ID | string |
| conversation_id | dr_conversation_id unique id | Drift Conversation ID | string |
| count(msg_author_type) | dr_contact_msg_ct | Drift Contact Message Count | int |
| count(msg_id) | dr_msg_ct | Total Drift Message Count | int |
| georegion(msg_ip) | region | State/Province | string |
| max(epochms()) | dr_last_msg_ts | Time of Last Drift Message | date |
| min(epochms()) | dr_first_msb_ts | Time of First Drift Message | date |
| msg_city | city | City | string |
| msg_country | country | Country | string |
| msg_postal_code | zip | Postal Code | string |
| valuect(hourofday()) | dr_hourly | Drift Active Hour of day | map[string]intsum |
| valuect(hourofweek()) | dr_hourofweek | Drift Active Hour of Week | map[string]intsum |
| valuect(yymm()) | dr_yymm | Drift Active Months | map[string]intsum |
Configuration
Follow these steps to set up and configure an import job for Drift in the Lytics platform. If you are new to creating jobs in Lytics, see the Jobs Dashboard documentation for more information.
- Select Drift from the list of providers.
- Select the import job type from the list.
- Select the Authorization you would like to use or create a new one.
- Enter a Label to identify this job you are creating in Lytics.
- (Optional) Enter a Description for further context on your job.
- (optional) Select the Keep Updated checkbox to import continuously.
- (optional) In the Start Date text box, enter a date to begin importing data from. Please use the format yyyy-mm-dd, e.g. 2021-11-19.
- (optional) Select the Skip Messages checkbox to skipping importing message details.
- (optional) Select the Skip Contact Details checkbox to skip importing contact details.
- Click the Start job button to start the job