Drift

What Is Drift?

Drift is a conversational-marketing and sales platform built around live chat and chatbots that engage website visitors in real time and route high-intent buyers to sales teams. In one sentence: Drift puts a chat widget on a company's website whose primary goal is not support tickets but revenue, qualifying visitors, booking meetings, and starting sales conversations the moment interest is highest. Founded in 2015 by David Cancel and Elias Torres, Drift helped popularize the term "conversational marketing." It was acquired by Vista Equity Partners in 2021 and, in 2024, Drift was acquired by and folded into Salesloft, so its branding and product packaging have been evolving. Functionally, on the websites that run it, Drift still appears as a recognizable chat widget.

For technology detection, Drift behaves much like other JavaScript chat tools: because the widget runs in the browser, a Drift-powered site loads scripts from Drift's CDN, exposes a global drift (and historically driftt) object, and injects a distinctive iframe into the page. That makes Drift reliably identifiable from the front end, and usually lets you read off the workspace's embed ID.

To be precise about scope: Drift is a hosted SaaS product, not a browser extension or self-hosted library. When a website "uses Drift," it has embedded Drift's snippet and connected it to a Drift account identified by an embed ID. The conversations, playbooks, and lead data live in Drift's cloud (now under the Salesloft umbrella).

The clearest way to understand Drift is to contrast its intent with that of a support chat tool. A support widget exists to deflect tickets and resolve problems for existing customers; Drift exists to start sales conversations with prospects. That difference shapes everything: the bot's opening question is more likely to be "What brings you in today?" or "Want to talk to sales?" than "How can we help with your account?", the routing logic is tied to lead ownership and territory rather than support queues, and the headline metric is meetings booked or pipeline influenced rather than tickets closed. When you detect Drift on a website, you are almost always looking at a company running a deliberate business-to-business demand-generation motion, which is precisely what makes it a high-value technographic signal.

How Drift Works

Drift centers on a chat widget plus a backend of playbooks (its automation rules) and integrations with CRM and sales tooling.

The on-page flow works like this:

• A site embeds the Drift snippet, which loads the widget code from Drift's CDN. The snippet is configured with an embed ID that ties the widget to a specific Drift account.
• The script initializes a global object, modern installs use window.drift, while older deployments expose window.driftt (and a drift.SNIPPET_VERSION), reflecting the company's original "Driftt" spelling.
• Drift injects the chat UI into the page, typically inside an iframe associated with a drift-frame-controller (and drift-frame-chat) element, isolating the widget from the host site.
• Playbooks decide what the bot says and does: greeting visitors, asking qualifying questions, routing to the right rep, and offering to book a meeting via integrated scheduling.

On the backend, Drift focuses on conversational marketing and sales engagement: bots qualify leads using rules and (increasingly) AI, then hand off to human sellers or schedule meetings directly on a rep's calendar. Tight CRM integration (notably Salesforce, and now Salesloft's sales-engagement workflows) means qualified conversations flow into the sales pipeline. Account-based marketing features let teams personalize the chat experience for visitors from target accounts. The throughline is revenue: Drift is engineered to turn anonymous traffic into booked sales conversations.

A concrete example makes the flow tangible. A visitor lands on a pricing page; a Drift playbook configured for high-intent pages fires a greeting after a few seconds. The bot asks a qualifying question or two, company size, use case, perhaps whether the visitor is already a customer, and branches accordingly. A junior or off-target lead might be pointed at documentation or a self-serve trial. A visitor whose email domain matches a target account, recognized through Drift's account-based features and CRM enrichment, gets fast-tracked: the bot offers to connect them with sales, looks up the owning rep, and presents that rep's live calendar so the visitor can book a meeting on the spot. By the time a human joins the conversation, the lead is already qualified and routed. This "speed to lead" emphasis, responding to interest in seconds rather than hours, is Drift's core value proposition and the reason it leans so heavily on bots and scheduling.

Because Drift's purpose is pipeline, its reporting is oriented around revenue outcomes rather than support metrics: conversations started, meetings booked, and pipeline or revenue influenced by chat. That orientation, more than any single feature, is what separates Drift from the support-first chat tools it is often compared with.

How to Tell if a Website Uses Drift

Drift is straightforward to detect because, like other chat widgets, it touches scripts, globals, and the DOM at once.

Script domains (the strongest tell)

Watch the network for requests to Drift's infrastructure:

• js.driftt.com — the classic widget loader (note the original "driftt" spelling).
• js.drift.com — the newer loader domain.
• widget.drift.com and event.api.drift.com — widget assets and event/API endpoints.
• Connections to *.drift.com / *.driftt.com for real-time messaging.

The embed ID is generally visible in the inline snippet that calls Drift's load function.

JavaScript globals

In the DevTools Console, check for:

• window.drift — the modern Drift API (e.g. drift.on(...), drift.api).
• window.driftt and drift.SNIPPET_VERSION — present in older installs.

If either global is defined, Drift is active.

Widget DOM

Inspect the page for Drift's containers: an iframe/element identified by drift-frame-controller (the launcher) and drift-frame-chat (the conversation window), along with elements in the drift- class namespace.

Cookies and storage

Drift stores identifiers in cookies and local storage prefixed with drift (for example, a driftt_aid/drift_aid-style anonymous ID and session entries), which corroborate the detection.

Tools and method

1. View Source. Search the HTML for drift, driftt, js.driftt.com, or js.drift.com; the loader snippet and embed ID are often inline.
2. DevTools Network tab. Reload and filter for drift; look for js.driftt.com / js.drift.com and read the embed ID.
3. DevTools Console. Enter typeof window.drift (or window.driftt) to confirm the API; check Application > Cookies/Local Storage for drift entries.
4. Wappalyzer and similar tools will typically label the site "Drift" automatically.

For a guided approach to spotting chat tools, see how to detect chat and live chat tools on a website, and for the broader method, how to find out what technology a website uses.

Key Features

• Conversational chatbots and playbooks. Rule-based and AI-assisted bots that greet, qualify, and route visitors automatically.
• Live chat. Real-time conversations that hand off seamlessly from bot to human seller.
• Meeting booking. Integrated scheduling so qualified visitors can book time on a rep's calendar inside the chat.
• Account-based marketing. Personalized chat experiences and routing for visitors from target accounts.
• CRM and sales-engagement integrations. Deep ties to Salesforce and, post-acquisition, Salesloft workflows.
• Conversation analytics. Reporting on engagement, pipeline influenced, and meetings booked.
• Drift Intel and visitor identification. Drift can enrich anonymous traffic with firmographic data, surfacing which companies are visiting even before a form is filled, so reps can prioritize accounts that match the ideal customer profile.
• Email and follow-up. Conversations that start in chat can continue over email, and drip-style follow-ups re-engage visitors who left without booking, keeping the conversation thread tied to the same lead record.

Pros and Cons

Pros

• Purpose-built for revenue: strong at qualifying and routing high-intent B2B traffic.
• Fast lead response via bots that engage visitors instantly, day or night.
• Solid CRM/sales-engagement integration for getting conversations into the pipeline.
• Account-based features suit B2B and ABM strategies.

Cons

• Historically priced toward mid-market and enterprise; can be costly for small teams.
• Product branding and packaging are in flux following the Salesloft acquisition, which can create uncertainty.
• More sales-oriented than support-oriented; teams wanting a help desk may find it a poor fit.
• The widget adds front-end JavaScript with some page-load cost.

Drift vs Alternatives

Drift competes most directly with other chat tools, differentiated by its sales-and-marketing focus. The table compares common alternatives.

Platform	Primary focus	Detection tell	Best for
Drift	Conversational marketing/sales	js.driftt.com / js.drift.com, window.drift, drift-frame-controller	B2B revenue teams, ABM
Intercom	Support + product engagement + AI	widget.intercom.io, window.Intercom	SaaS/product-led teams
Qualified	Pipeline chat for Salesforce	qualified.com assets	Salesforce-centric sales
HubSpot Chat	Chat tied to HubSpot CRM	hs-scripts.com, hs-banner	HubSpot users
LiveChat	Focused live chat	cdn.livechatinc.com	SMB live chat

If your interest leans toward support and product onboarding rather than sales chat, compare Drift with our profile of Intercom.

Use Cases

• Conversational marketing. Engaging website visitors with targeted chat to capture and qualify demand.
• Sales acceleration. Routing qualified, high-intent visitors to reps and booking meetings instantly.
• Account-based marketing. Personalizing the on-site chat experience for visitors from target accounts.
• Competitive and lead research. Detecting Drift on a site signals a B2B company with an active conversational-marketing/sales motion, useful technographic input for prospecting and competitive analysis. Sellers can use that signal to tailor outreach, knowing the target already values fast, conversation-led buying experiences.
• Event and campaign landing pages. Marketing teams drop Drift onto webinar or campaign pages so that interest generated by an ad or email can convert into a live conversation immediately, rather than dying in a static form.

Frequently Asked Questions

Why do I see both "drift" and "driftt" on a site?

Drift was originally spelled "Driftt," and that legacy survives in code: the classic loader lives at js.driftt.com and older installs expose window.driftt, while newer deployments use js.drift.com and window.drift. Seeing either spelling indicates Drift is present; which one depends on how recently the snippet was installed. The double-t artifacts are harmless quirks of the company's history rather than a different product.

What is the fastest way to confirm a site uses Drift?

In DevTools, type typeof window.drift (or window.driftt) in the Console; if it returns "object", Drift is active. You can also filter the Network tab for drift and look for js.driftt.com / js.drift.com, or spot the drift-frame-controller element in the DOM.

Is Drift a support tool or a sales tool?

Primarily a sales-and-marketing tool. Unlike support-first chat platforms, Drift's playbooks, lead routing, and meeting-booking features are built to generate and qualify pipeline. It can field questions, but its design goal is revenue, not ticketing. Its reporting reflects this, centering on conversations started, meetings booked, and pipeline influenced rather than tickets resolved or response times.

Did Drift get acquired, and does it still exist?

Yes. Drift was acquired by Vista Equity Partners in 2021 and then by Salesloft in 2024, after which it was folded into Salesloft's platform. The product and branding have been evolving as a result, but the recognizable Drift chat widget still appears on many websites.

What does a typical Drift conversation flow look like?

A playbook fires a greeting on a high-intent page, the bot asks a qualifying question or two, and it branches: low-fit visitors are pointed to docs or a trial, while visitors from target accounts are fast-tracked, the bot identifies the owning rep and offers that rep's live calendar so the visitor can book a meeting immediately. The goal is "speed to lead": engaging and qualifying interest in seconds rather than hours.

Can a website hide that it uses Drift?

Not easily if it runs the standard widget. Drift must load its scripts in the browser, define a global object, and inject its chat iframe, all visible to anyone inspecting the page. Server-side analysis confirms it even more reliably by examining scripts, globals, and behavior together. Analyze any URL with StackOptic.