> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/integrations/other/drift.md). # 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 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 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 After making sure that you are able to track Drift chatbot actions, you can go ahead and define the goals as such:

Now, just like any other goal, you will be able to use this throughout the platform! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hockeystack.com/integrations/other/drift.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.