How to Tell If a Website Uses Drift

Drift is a conversational-marketing and sales-chat platform built for B2B, using chat and chatbots to engage website visitors, qualify them and book sales meetings in real time. To tell whether a site uses it, the quickest answer is to type drift into the console — it defines a global object by that name — or to look for the embed from js.driftt.com. This guide covers every reliable signal, the conversational-marketing model behind them, and what a Drift install tells you about the business.

What is Drift?

Drift, founded in 2015 (and now part of Salesloft), popularised conversational marketing: the idea that B2B websites should let interested visitors start a conversation immediately — with a bot or a rep — rather than filling in a form and waiting. Its platform combines live chat, chatbots and playbooks, meeting booking, and account-based targeting, all aimed at turning website traffic into qualified sales conversations and pipeline. It is strongly associated with B2B companies with active sales teams, especially those running account-based marketing.

For detection, the key context is that Drift is a sales-and-pipeline tool, not a generic support widget. Its presence signals a B2B business that treats its website as a sales channel and invests in engaging and qualifying visitors in real time. Because Drift's widget is loaded by a consistent embed from its driftt.com domains, the install leaves a clear footprint. (Note the double-t driftt.com for assets, distinct from the drift.com marketing site.)

How Drift loads and runs

A Drift install uses an embed snippet that defines the global window.drift object (with a command queue and methods like drift.on, drift.api) and calls drift.load('<embedId>') with the account's embed ID. The snippet loads the widget script from js.driftt.com/include/<date>/<embedId>.js, where the embed ID identifies the Drift account. The widget itself is served from customer.driftt.com, and Drift sends interaction and analytics events to event.api.drift.com (and related drift.com endpoints).

Once running, Drift renders its chat launcher and can fire targeted playbooks based on the visitor, the page or account data. It sets drift-related cookies and storage to maintain the conversation and identify returning visitors. The embed ID in drift.load (and in the js.driftt.com include URL) is the public account identifier. Knowing this flow — the window.drift object, the drift.load('<embedId>') call, the js.driftt.com embed, the customer.driftt.com widget, and event.api.drift.com traffic — makes Drift straightforward to confirm.

How to tell if a website uses Drift

Confirm at least one strong signal.

1. Use the console. Type drift and press Enter. A returned object confirms Drift is loaded. You can inspect drift.api and related methods.

2. Check the Network tab. Filter for driftt or drift. You will see the embed from js.driftt.com/include/..., the widget from customer.driftt.com, and events to event.api.drift.com.

3. View the source. Search for drift. The embed snippet and the drift.load('<embedId>') call (with the embed ID) are usually visible.

4. Look for the launcher. Drift's chat launcher and playbook messages are the visible front end; the welcome message often reflects a sales-oriented playbook.

5. Read the embed ID. The embed ID in drift.load or the js.driftt.com URL identifies the Drift account.

What the Drift signals look like

"use strict"; !function() { var t = window.driftt = window.drift = window.driftt || []; ... }();
drift.SNIPPET_VERSION = "0.3.1";
drift.load("abc1def2ghi3");   // embedId
GET https://js.driftt.com/include/<timestamp>/abc1def2ghi3.js
GET https://customer.driftt.com/...   ;   POST https://event.api.drift.com/...

The combination of the window.drift object, the drift.load('<embedId>') call, and the js.driftt.com/customer.driftt.com assets is conclusive.

Drift versus other chat tools — avoiding false positives

Match the host to keep messaging tools distinct. Drift uses driftt.com/drift.com and the drift global; Intercom uses intercom.io and the Intercom global; Zendesk uses zdassets.com and zE; Qualified and other B2B chat tools have their own hosts. The double-t driftt.com asset domain is distinctive to Drift. As with all chat tools, the launcher bubble alone does not identify the vendor — confirm with the host or global. The main subtlety is that Drift playbooks can be page- or audience-targeted, so the widget might appear only on certain pages or for certain visitors; check key pages (pricing, demo) where sales chat is most likely enabled.

How reliable is each Drift signal?

The window.drift object and the drift.load('<embedId>') call are definitive. The js.driftt.com embed and customer.driftt.com widget are equally conclusive, as is event.api.drift.com traffic. The launcher and playbook messaging are suggestive but should be confirmed with a host or global. The weakest situation is a site that targets Drift to specific pages or accounts, so it may not appear everywhere — check sales-oriented pages. As a rule, the drift global or the js.driftt.com embed settles it, and the embed ID identifies the account.

What a Drift install reveals about a business

Finding Drift is a strong signal of a B2B company with an active sales motion that treats its website as a pipeline source. Because Drift is built for conversational marketing and meeting booking, its presence implies a sales team, likely an account-based marketing approach, and a focus on converting traffic into qualified conversations rather than just form fills. If you sell B2B sales or marketing tooling — ABM, sales engagement, lead routing, CRM, or conversational AI — a Drift install marks an ideal-fit, sales-driven account. The playbooks in evidence (a demo-booking flow, an ABM greeting) reveal how aggressively the company pursues pipeline, which is useful qualification. Drift's acquisition by Salesloft also hints at a possible broader sales-engagement footprint.

What finding Drift means for sales, agencies and competitive research

For sales and prospecting, Drift is a precise signal of a B2B, sales-led organisation — a fit for tools that support pipeline generation, lead routing, ABM and sales engagement. The presence of meeting-booking playbooks indicates a team optimising for demos and sales conversations.

For agencies and consultants, finding Drift tells you the client invests in conversational marketing, so engagements can focus on playbook strategy, ABM targeting, lead qualification, or integrating Drift with the CRM and sales stack. It signals a sales-driven, pipeline-focused client.

For competitive and market research, Drift adoption indicates how seriously a B2B company pursues website-driven pipeline. Spotting a competitor on Drift tells you they engage and qualify visitors in real time and likely run ABM, useful when benchmarking go-to-market sophistication.

Drift in the wider B2B go-to-market stack

Drift sits within a B2B sales-and-marketing stack. Expect a CRM (Salesforce or HubSpot), a marketing-automation platform (Marketo, HubSpot or Pardot), often an ABM platform (Demandbase, 6sense), and analytics — with Drift as the real-time conversation layer on top, routing qualified visitors to reps and booking meetings. Given the Salesloft acquisition, you may also find Salesloft's sales-engagement tooling in the broader organisation. For an auditor, the valuable details are the embed ID, the playbooks visible on key pages, and the surrounding CRM, marketing-automation and ABM tools; together these reveal a B2B company's pipeline strategy and how central conversational marketing is to it.

A quick Drift confirmation walkthrough

Open the site (ideally a pricing or demo page) with developer tools on the Console panel and type drift — a returned object confirms Drift. Switch to the Network tab, filter for driftt, and confirm the embed from js.driftt.com/include/... and the widget from customer.driftt.com. View the source for the drift.load('<embedId>') call to read the embed ID. Look for the chat launcher and any sales-oriented playbook message. The drift global or the js.driftt.com embed confirms Drift and the embed ID identifies the account.

A quick Drift detection checklist

• Type drift in the console; a returned object is conclusive.
• Filter the Network tab for driftt; js.driftt.com and customer.driftt.com confirm it.
• Search the source for drift.load('<embedId>') and read the embed ID.
• Look for event.api.drift.com traffic.
• Confirm the vendor via host/global, not the chat bubble's appearance.
• Check sales-oriented pages, since playbooks may be page-targeted.

Detecting Drift at scale

Checking one site is quick, but finding every Drift user across a list — to prospect B2B, sales-led companies — calls for automation. StackOptic detects Drift and thousands of other technologies from a real browser, capturing the embed and the surrounding go-to-market stack. Because Drift is such a specific signal of a B2B company that runs website-driven pipeline and likely account-based marketing, a market-wide scan for it builds a precise list of sales-led organisations, and combining it with the CRM, marketing-automation and ABM tools each runs reveals how mature their go-to-market really is. Tracking the results over time also catches companies adopting or dropping conversational marketing, which often signals a shift in sales strategy. For related reading, see our guide to detecting chat and live-chat tools on a website and the full Drift technology profile.