> For the complete documentation index, see [llms.txt](https://userguide.zappost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.zappost.com/zap-post-web-app/zap-post-user-guide/zap-app/using-the-zapp/insights.md).
# Insights
Track the performance your Zap campaigns and gain valuable insights.
## Accessing Insights
Once your first submission has been created, the next step track how well it performs. \
To access the Insights area of the Zap App, select the ‘insights’ icon in the ZAP-POST header and then Return on Advertising Spend.
## ROAS Reporting
ZAP\~POST ROAS Reporting ensure every campaign is automatically matched against attributed conversions, giving you a clear, real-time return on ad spend figure you can act on.
Reporting is available at the account, campaign and submission level. All reports can be filtered by date and Match back attribution.
Match back options
| Match back Method | Description |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| All | This will match any orders that pass any of the match back methods. |
| Customer | This will only attribute an order if a customer specifically targeted in a send made a purchase within 42 days of the campaign land date (This is a default value and can be changed) |
| Address | This will attribute an order that is placed from a postcode that was targeted as part of your send. |
{% hint style="info" %}
If you want to change your ROAS attribute window, you can speak with your account manager and they can handle this for you.
{% endhint %}
All reports can also be exported to PDF for use outside of the ZAP APP.
---
# 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://userguide.zappost.com/zap-post-web-app/zap-post-user-guide/zap-app/using-the-zapp/insights.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.
