Drift powers conversational marketing and sales — chat conversations on your site, the contacts behind them, and the accounts they belong to. Connecting it as a data source through the Connectors library syncs those tables into your Alta workspace, where they become training data for Alta and a foundation for your metrics, dashboards, and Luna analysis. Once it's flowing, you can measure chat volume, engagement, and which accounts are talking to you — and ask Luna questions in plain English. Drift connects with credentials.
Who this is for: Marketing and sales teams running Drift who want chat engagement measured alongside pipeline in Alta.
Before you start
Have your Drift API credentials (OAuth token) ready, with access to conversations and contacts.
Connect a source only once per workspace. If Drift already shows Connected, edit the existing connection.
Connect Drift
Open Connectors from the sidebar.
Find Drift via the category tabs or the Search data sources box.
Click the Drift card to open the Create connector screen.
Fill in the connection fields shown, then click Create.
Alta runs a connect test. If it fails you'll see The connect test has failed with Drift's error — fix the field and retry.
The card then shows Connected and Data is syncing until the first sync finishes.
Choose which tables sync
Open the connection. Drift brings in tables like conversations, messages, contacts, and accounts.
Use the Synced toggle in the Drift tables section to control what's pulled in.
Turn off Show only synced tables to see everything available.
Key tables and fields synced
conversations —
id,status,createdAt,updatedAt,contactId,inboxIdmessages —
id,conversationId,type,author,createdAtcontacts —
id,email,name, attributesaccounts —
id,name,domain, owners
What you can ask this data
Once it's syncing, build it into metrics and dashboards or just ask Luna / Ask AI. For example:
"How many chat conversations did we have last week?" — counts
conversationsbycreatedAt."Which accounts engaged in chat?" — joins
conversationstoaccounts."What's the average number of messages per conversation?" — counts
messagesperconversationId."How is chat volume trending over time?" — trends
conversationsby date.
Build your first metric (worked example)
Confirm
conversationsshows Last sync — Succeeded.In Metrics, create a metric on
conversationswith measure count of rows and date fieldcreatedAt.Set the period to weekly and group by
inboxId(or account) to see where chats land.Save, add to a dashboard, then ask Luna "how many chat conversations did we have last week?" to confirm.
Example use cases
Conversational-marketing dashboard. Chat volume, engaged accounts, and response patterns over time.
Account engagement. Join chats to target accounts to see which are actively reaching out — a buying signal.
Chat-to-pipeline. Combine with CRM data to connect Drift conversations to created opportunities.
Keep it in sync
Sync status shows Last sync (Succeeded/Failed) and the Sync frequency.
Click Sync now to refresh immediately; it's disabled while a sync runs.
Use the overflow menu (⋯) to Disable, Enable, or Delete.
Tips and common pitfalls
Sync messages for depth. Conversations give volume;
messageslet you measure engagement per chat.A failed connect test is usually credentials or scopes. Re-check the field flagged by the inline error.
Deleting is permanent. Disable instead to pause.
Related
