> 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/analytics-dashboard/captured.md).
# Captured
Measure CTA performance with capture metrics and captures by partner and platform.
The **Captured** section focuses on conversion: how often users click your CTA, where it happens, and which partners and platforms drive it. Impressions measure reach and Engaged measures interaction. Captured shows what ultimately drives value.
### Capture Metrics
* **Impressions Captured** – The number of impressions where users clicked a CTA at least once.
* **Capture Rate** – Impressions Captured as a percentage of all impressions. It measures how well the playable turns views into action.
* **Total Captures** – Every CTA click recorded. This can be higher than Impressions Captured when users click a CTA more than once.
* **Top Capturing Scene** – The scene with the most captures. In most well-built playables, this is the end card.
### Captures by Partner
A line chart of captures over time, with a line for each partner. Use the dropdown to switch between:
* **Total Captures** – How many captures each partner delivered.
* **Capture Rate** – Captures relative to each partner's impressions.
This helps answer questions like:
* Which partners deliver the highest-quality traffic?
* Are spikes in impressions turning into captures?
* Which partners may need creative or targeting changes?
### Captures by Platform
The same chart broken down by device type, like Mobile, Tablet, and Desktop, with the same **Total Captures** and **Capture Rate** options. Use it to refine CTA size, placement, and interaction design for each device.
{% hint style="info" %}
If no CTA clicks were recorded in the selected range, the section shows **No Capture Events Detected**. Check that your playable has a CTA layer with a Launch URL action, and use the [Analytics Event Monitor](/play/preview-and-share/analytics-event-monitor.md) to confirm it fires.
{% endhint %}
---
# 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/analytics-dashboard/captured.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.
