> 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/marketing-intelligence/journeys/journeys-use-cases.md).
# Journeys Use Cases
### Example Use Case
* Inbound leads, last 7 days
* Analyze their full journeys and understand how we brought them
* SDR Hit list engagements, today
* Set up alerts for sales team to enable quick response
* List of Closed Won Deals
* Pull deal retros for board meetings
* Buying Unit Penetration
* Understand who we need to convert
### Example Configurations
| View | Configuration | Filters |
| ---------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Account List Intent Tracking | Group by Companies | Target Account list (company property), Who have entered site today Target Account list (company property) Who have done \[Enter high intent goal] within the last 7 days |
| ABM Activity | Group by Companies | Whose target account (company property) is true, who have entered site last 90 days |
| Buying Unit Penetration | Group by Users | Whose Company domain (company property) Contains \[Enter Company Name] |
| New ICP Leads | Group by Companies | Who have done \[Enter sign up goal] within the last 3 days |
| Rep Account List Activity | Group by Companies | Account list owner property (company properties) is \[Enter owner name] All Time |
| Gong Mentions | Group by Companies | Who have done \[Gong mention tracking goal] in the last 7 days |
---
# 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/marketing-intelligence/journeys/journeys-use-cases.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.