Drift
Sync data from your warehouse to Drift. Keep your Drift contacts enriched with the latest customer attributes for conversational marketing and sales engagement.
Prerequisites
- A Drift account with API access
- A Drift OAuth access token with
contact_readandcontact_writescopes
Authentication
Drift supports two authentication methods:
Access Token
- In Drift, go to Settings > App Settings > API
- Create a new app or select an existing one
- Copy the OAuth Access Token
- Paste it into the Access Token field in Zeotap
OAuth 2.0
- Click Connect with OAuth in Zeotap
- Sign in to your Drift account
- Authorize the requested permissions
Configuration
Drift does not require any additional configuration fields beyond authentication.
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Object Type | Select | Yes | The Drift object to sync to: Contacts |
| Tag Name | Text | No | Tag to manage for audience syncs. Contacts are tagged/untagged based on the sync mode. |
Supported Operations
Sync Modes
| Mode | Supported |
|---|---|
| Upsert | Yes |
| Insert | — |
| Update | — |
| Mirror | — |
Audience Sync Modes
| Mode | Supported |
|---|---|
| Add | Yes |
| Remove | Yes |
| Mirror | Yes |
| Upsert | — |
Features
- Field Mapping: Yes
- Schema Introspection: No
Required Mapping Fields
| Object | Required Fields |
|---|---|
| Contacts |
Default Destination Fields
Contacts: email, name, phone, tags, alias, externalId
Troubleshooting
Authentication failed: invalid or expired access token
Generate a new OAuth access token in the Drift developer settings, or reconnect via OAuth.
Duplicate contact errors
Drift rejects POST /contacts when an email already exists (unless an externalId is mapped). Zeotap handles this by looking up the contact by email first and PATCHing existing records. If you see duplicate errors, verify the email field is correctly mapped.
Rate limiting
Drift enforces API rate limits (~1000 requests per 20 seconds, varies by plan). Zeotap handles rate limiting with automatic retries and backoff when HTTP 429 responses are received.
Custom attributes not syncing
Custom contact attributes must be defined in your Drift account before they can be populated via the API. Contact your Drift account representative to configure custom attributes.