> 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-integrations/zap-post-integrations/klaviyo/roas-reporting.md).

# ROAS Reporting

ROAS Reporting measures return on ad spend by matching campaigns with attributed sales.\
With Klaviyo, ZAP\~POST ingests sales data and assesses each sale against various attribution methods. Qualifying sales are linked to the relevant submission and campaign.\
Use the ROAS Reports screens to review the resulting performance data.

<figure><img src="https://1277613767-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyQKiT3JcaHMDXjtrjvBz%2Fuploads%2Fd0WN2RnqjwN8hZWtQ6HY%2Fimage.png?alt=media&amp;token=5446acdc-8824-455f-9904-5e78301ce4cc" alt=""><figcaption></figcaption></figure>

You can find more information on ROAS Reporting [here](/zap-post-web-app/zap-post-user-guide/zap-app/using-the-zapp/insights.md#roas-reporting)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://userguide.zappost.com/zap-integrations/zap-post-integrations/klaviyo/roas-reporting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.