# Drift

HockeyStack’s Drift integration allows you to track conversation actions and automatically send them to HockeyStack to merge with the rest of your data. This means that you can analyze in which stage prospects interact with the live chat and how marketing efforts impact the conversion rate of chat-based actions.

### Connecting to Drift <a href="#block-bc368ffcb9d549ca8a56351f5b67133f" id="block-bc368ffcb9d549ca8a56351f5b67133f"></a>

If you have Drift’s website script (with source [js.driftt.com](http://js.driftt.com/)) installed on your website, HockeyStack can automatically detect it and start listening for any chatbot actions.

If you don’t see any Drift actions tracked, then you may need to add our Drift-HockeyStack script separately to your website to allow tracking. You can ask your customer success specialist for help.

### Tracking Drift Actions <a href="#block-ec8b4efb5e6d4221b3757d28a9dd327d" id="block-ec8b4efb5e6d4221b3757d28a9dd327d"></a>

HockeyStack tracks the following actions out of the box:

* Conversation Started
* Email Captured
* Meeting Requested
* Meeting Booked

We also track the Drift user id so even if visitors don’t give their emails now, we can merge it later once they do.

### Using Drift Actions in Dashboard <a href="#block-724fc2ecec094dbca8217456b9184d3a" id="block-724fc2ecec094dbca8217456b9184d3a"></a>

After making sure that you are able to track Drift chatbot actions, you can go ahead and define the goals as such:

<figure><img src="/files/vgWInnnFHRh8LxigXc3L" alt=""><figcaption></figcaption></figure>

Now, just like any other goal, you will be able to use this throughout the platform!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hockeystack.com/integrations/other/drift.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
