> For the complete documentation index, see [llms.txt](https://even-financial.gitbook.io/developer-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://even-financial.gitbook.io/developer-center/channel-partner-reporting/report-options.md).

# Report Options

Engine offers 3 primary ways to get performance and conversion data back to your systems: dashboards, real-time event pushes, and programmatic API pulls. They differ in delivery method, data freshness, and engineering effort. Most partners combine multiple methods—a dashboard for humans and a push or pull method to feed their own systems.

{% hint style="success" icon="lightbulb" %}
Add [attribution tracking tags](/developer-center/channel-partner-reporting/attribution-tracking.md) to any of these methods to tie performance data back to your own campaigns, sources, or IDs.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Looker Reporting</strong></td><td>Pre-built dashboards and exploratory reports over the Engine analytics warehouse, covering leads, offers, conversions, and revenue. Filterable and exportable, with optional scheduled email delivery.<br><br><strong>Why partners choose it:</strong><br>• No engineering required for operations, marketing, and finance teams.<br>• Visual drill-down and ad-hoc performance analysis.<br>• Scheduled or on-demand exports for recurring workflows.</td><td><a href="/developer-center/channel-partner-reporting/report-options/looker-reporting.md">Looker Reporting</a></td><td></td></tr><tr><td><strong>Postback Reporting</strong></td><td>Server-to-server event delivery. Engine fires an HTTP POST to your endpoint the moment a tracked event occurs (lead, payout, conversion), passing your identifiers back via macros so you can attribute the event in real time.<br><br><strong>Why partners choose it:</strong><br>• Real-time, event-level granularity without polling.<br>• Direct delivery to attribution and tracking systems.<br>• Click IDs and customer identifiers for seamless matching.</td><td><a href="/developer-center/channel-partner-reporting/report-options/postback-reporting.md">Postback Reporting</a></td><td></td></tr><tr><td><strong>Engine Analytics API</strong></td><td>A REST API for pulling analytics and reporting datasets on demand. Query historical ranges and recent data in structured JSON to land in your warehouse or BI tool on a schedule you control.<br><br><strong>Why partners choose it:</strong><br>• Programmatic workflows with scheduling and retries you control.<br>• Flexible querying with full historical backfill.<br>• Direct feeds for data warehouses and BI pipelines.</td><td><a href="/developer-center/channel-partner-reporting/report-options/engine-analytics-api.md">Engine Analytics API</a></td><td></td></tr></tbody></table>


---

# 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://even-financial.gitbook.io/developer-center/channel-partner-reporting/report-options.md?ask=<question>&goal=<user_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.