> 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/common-issues.md).
# Common Issues
## Connection issues
My API token is not accepted
Double-check that you're using the correct API token from Adjust. Go to **Account Settings → Your profile → API token** in Adjust — this is different from your app token. Make sure there are no leading or trailing spaces when you paste it into Coupler.io.
The data flow fails immediately after setup
This usually means no metrics were selected. Adjust requires at least one metric to generate a report. Go back to the **Metrics and dimensions** step in your data flow settings and confirm at least one metric is selected.
## Missing data
My report returns no rows
Check the following:
* At least one metric must be selected — the API won't return data without it
* Your start date may be set too recently or in the future — use the date picker to set a date that falls within a period with known activity
* If you're filtering by specific dimensions, make sure those dimensions have associated data for the date range you've selected
Some campaigns or networks are missing from my report
Adjust only returns data for sources active in the selected date range. If a campaign ran before your start date, it won't appear. Also confirm that the relevant networks are connected and properly tracked in your Adjust account.
Cohort metrics are empty or lower than expected
Cohort metrics require sufficient time to accumulate. If you're pulling `cohort_revenue` for installs that happened recently, there may not be enough post-install activity recorded yet. Try extending the date range to give cohorts more time to mature.
## Permission errors
I get a 401 or "unauthorized" error
Your API token may have been regenerated or expired. Log into Adjust, navigate to your profile settings, and check if the token shown matches what you have in Coupler.io. If it differs, update the token in your data flow's source settings.
I can connect but can't see data for certain apps
The API token is tied to your Adjust user account. If your account doesn't have access to specific apps in Adjust, those apps won't appear in your report. Contact your Adjust account admin to request the necessary permissions.
## Data discrepancies
Adjust numbers don't match what I see in ad network dashboards
This is expected. Adjust attributes installs based on its own attribution logic (last-click, probabilistic, etc.), while networks report all clicks and installs they claim credit for. Use `network_installs_diff` and `network_cost_diff` metrics to see the delta explicitly.
Revenue figures differ from my internal records
Adjust revenue tracks what's reported through its SDK events. If some purchases aren't firing the revenue event correctly, or if refunds aren't being reported, totals will differ. Also check if you're comparing `revenue` (IAP only) vs. `all_revenue` (IAP + ad revenue) — using the wrong metric is a common source of confusion.
## Rate limits
My data flow errors out with a rate limit message
Adjust's reporting API has rate limits that vary by plan. If you're running large reports with many dimensions and a long date range, try narrowing the date window or reducing the number of dimensions. Avoid running multiple data flows against Adjust simultaneously.
---
# 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/common-issues.md?ask=&goal=
```
`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.