Drift is a conversational marketing platform that uses targeted messaging and intelligent chatbots to engage with people when they’re on a business website.
This datasource slice collects data from Drift and writes it to S3 and chosen Warehouses.
Steps to add this slice to your installation
The steps to launch your slice are:
- Generate Drift App (preferably named as datacoral) and get clientID and secretID from the App
- Add the Drift slice
1. Generate Drift App
Please refer to the documentation at https://devdocs.drift.com/docs/authentication-and-scopes#section-scopes to understand and obtain the tokens/urls needed for the slice to pull data from Drift. You will need to obtain the clientId, clientSecret.
Necessary input parameters:
clientId- The Consumer Key from the connected App definition.
clientSecret- The Consumer Secret from the connected App definition.
Instructions for setting an App in drift
Step 1. create new App named
datacoral and look for clientID and secretID in App Credentials
Step 2. Add two redirectURLs in Oauth & Scopes
Step 3. Add below listed permissions in Drift Scopes
- all_contact_read `
2. Add the Drift slice
Step 1. Select the drift slice type from the available list
Step 2. Add drift slice by providing slice name and and selecting TargetWarehouse(s)
Step 3. Provide ClientID and SecretID. Select Schedule and Token refresh Schedule or use defaults.
Step 4. Drift has default 8 loadunits, please remove unused ones if any. Hover over any loadunit to edit any property related to the loadunit.
Step 5. Next screen will show data layout for each loadunit.
Step 6. Next screen will show warehouse configuration for each loadunit.
Step 7. Confirm all changes and click
Next. Tables are created in chosen warehouse(s) and you will be re-directed to the connector page
Supported load units
Output of this slice is stored in S3 and chosen warehouse(s).
Data stored in AWS S3 is partitioned by date and time in the following bucket
AWS Redshift: Schema - Schema name is same as the name of the slice. Tables produced by the slice are:
- schema.accounts - schema.contacts_attributes - schema.conversations - schema.contacts - schema.messages - schema.meetings - schema.playbooks - schema.users
Important to Note
Drift access tokens expires after every two hours hence token refresh schedule needs to be less than or equal to two hours