> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/marketing/adjust/faq.md).

# FAQ

<details>

<summary>Which entities does Adjust support in Coupler.io?</summary>

Adjust currently supports one entity: **Report**. It's a flexible report builder — you define the metrics and dimensions, and the API returns the matching data. This single entity covers installs, revenue, cost, ad revenue, cohort metrics, engagement data, and more.

</details>

<details>

<summary>Can I pull cohort metrics from Adjust?</summary>

Yes. Metrics like `cohort_revenue`, `cohort_ad_revenue`, `cohort_gross_profit`, and `cohort_all_revenue` are available in the metrics picker. Keep in mind that cohort metrics measure user groups from their install date, so you'll need a date range long enough for cohorts to show meaningful activity.

</details>

<details>

<summary>What's the difference between network metrics and standard metrics?</summary>

Metrics prefixed with `network_` (like `network_installs`, `network_cost`) come directly from the ad network's own reporting API. Standard metrics (like `installs`, `cost`) reflect what Adjust has attributed based on its own attribution logic. Discrepancies between the two are normal — use `network_installs_diff` and `network_cost_diff` to track the gap.

</details>

<details>

<summary>How do I add custom event metrics that aren't in the default list?</summary>

Use the **Additional metrics** field in the data flow settings. Enter each custom metric name on a new line. These are typically app-specific events you've defined in Adjust (e.g., a purchase event or tutorial completion event). Check your Adjust dashboard for the exact metric slugs.

</details>

<details>

<summary>Can I combine Adjust data with spend data from other ad platforms?</summary>

Yes. Set up separate data flows for Adjust and your other ad platform (e.g., Facebook Ads, Google Ads), then use Coupler.io's **Join** transformation to combine them on shared keys like `campaign` or `country_code`. This is useful for reconciling attribution data with raw spend.

</details>

<details>

<summary>Why does adding more dimensions increase my row count so much?</summary>

Each unique combination of dimension values creates its own row. If you add `network`, `campaign`, `country`, and `creative`, you'll get one row for every unique combination of those four values — which can multiply quickly across a large account. Start with fewer dimensions and drill down only where needed.

</details>

<details>

<summary>Can I send Adjust data to AI tools for analysis?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your Adjust report data directly to these tools for natural-language querying, anomaly detection, or campaign commentary.

</details>

<details>

<summary>How far back can I pull historical data from Adjust?</summary>

Adjust's reporting API supports historical data going back to when your app was first tracked. Use the date picker in the data flow settings to set your start date. For very long date ranges, consider using narrower windows and Coupler.io's Append transformation to build up your history incrementally.

</details>

{% hint style="info" %}
For a full list of available metrics and dimensions, see the [Data Overview](/sources/category/marketing/adjust/data-overview.md) article. If you're running into API errors or missing data, check [Common Issues](/sources/category/marketing/adjust/common-issues.md). For tips on structuring your reports, visit [Best Practices](/sources/category/marketing/adjust/best-practices.md).
{% 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 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://docs.coupler.io/sources/category/marketing/adjust/faq.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.