> 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/appsflyer/faq.md).

# FAQ

<details>

<summary>Can I pull data for multiple apps in one data flow?</summary>

No — each AppsFlyer data flow is tied to a single App ID. If you want data for multiple apps, create a separate data flow for each one. You can then use Coupler.io's Append transformation to combine results from multiple data flows into one destination sheet or table.

</details>

<details>

<summary>What's the difference between In-app events, Organic in-app events, and Retargeting in-app events?</summary>

These three entities cover the same type of data (user actions inside your app) but split by attribution type. **In-app events** covers users acquired through paid channels. **Organic in-app events** covers users who found your app without paid advertising. **Retargeting in-app events** covers users who re-engaged through a retargeting campaign. If you want a complete picture, use Coupler.io's Append transformation to combine all three.

</details>

<details>

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

For raw reports — installs, in-app events, and uninstall events — AppsFlyer limits history to the last **90 days**. Aggregated reports (daily, partners, geo) may support longer ranges depending on your AppsFlyer subscription plan. Set your start date using the date picker and stay within the 90-day window for raw entities.

</details>

<details>

<summary>Why are IDFA and GAID fields empty in my install data?</summary>

Device identifiers are increasingly restricted due to privacy regulations and platform policies. On iOS, users must opt in via App Tracking Transparency (ATT) for IDFA to be shared — most decline. On Android, GAID availability is affected by Google's privacy changes. This is a data availability issue at the platform level, not something Coupler.io can resolve.

</details>

<details>

<summary>Can I use AppsFlyer data with AI tools like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can send AppsFlyer campaign or event data directly to these tools for automated analysis, summaries, or anomaly detection.

</details>

<details>

<summary>Why does my data flow show different numbers than the AppsFlyer dashboard?</summary>

The most common cause is a timezone mismatch. Make sure the timezone you set in Coupler.io matches your app's timezone in AppsFlyer App Settings exactly. Also check that the date range you're pulling aligns with what the dashboard is showing. For more detail, see the Data discrepancies section in Common Issues.

</details>

<details>

<summary>How do I combine paid and organic install data in one report?</summary>

Add both the **Installs** and **Organic installs** entities as sources in your data flow, then apply the **Append** transformation. This stacks both datasets into a single output. You can add a column or filter in your destination to distinguish the two. If you also have retargeting installs, add that entity as a third source in the same Append.

</details>

{% hint style="info" %}
For details on available fields and report types, see the [Data Overview](/sources/category/marketing/appsflyer/data-overview.md) article. For timezone and API key troubleshooting, see [Common Issues](/sources/category/marketing/appsflyer/common-issues.md). For tips on combining organic and paid data, see [Best Practices](/sources/category/marketing/appsflyer/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/appsflyer/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.