> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/analytics/readme.md).
# Welcome
CRAFTSMAN ANALYTICS provides a powerful, end-to-end view of how users interact with your playables. It gives creators, marketers, and performance teams the ability to understand engagement, track funnel progression, and optimize creative effectiveness using clear, actionable data.
With Analytics, you can:
* **Track the full user journey** from first load to final conversion
* **Visualize engagement patterns** at both high-level and scene-level depth
* **Monitor funnel performance** across Impressions → Engaged → Captured
* **Identify drop-off points** and moments of peak interaction
* **Compare high-level performance across playables** using the multi-project [Listing View](/analytics/analytics-tab/listing-view.md)
* **Understand which elements in your project are being interacted with,** including hotspots, swipe areas, and CTA elements. (e.g. See which options users are selecting in a quiz)
* **Understand how each layer of your playable performs**, including hotspots, swipe areas, and CTA elements
CRAFTSMAN ANALYTICS is designed to empower teams to *play smarter*: making data-driven decisions that improve user flow, creative clarity, and conversion outcomes.
---
# 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://help.craftsmanplus.com/analytics/readme.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.
