> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/data-and-insights/marketing-integrations/returnista.md).

# Returnista

Connect Returnista to see returns and return rate per channel and campaign — and what your advertising really earned.

Connect Returnista so AdPage knows what came back. Returns are the difference between revenue and income, and a channel with a 40% return rate is not the channel your ROAS says it is.

AdPage only reads. It cannot create, approve or change a return.

### Before you start

You need two values from Returnista:

* Your **account ID**.
* A **Service User API key**.

Both come from your Returnista account. If you cannot find the Service User section, Returnista support creates these — it is a standard request, and the key is meant for exactly this kind of integration.

### Connect Returnista

{% stepper %}
{% step %}

#### Open the tile

Go to **Integrations**, select the container, and open the **Returnista** tile.
{% endstep %}

{% step %}

#### Paste the account ID and API key

Fill in both values and connect.
{% endstep %}

{% step %}

#### Wait for the first sync

AdPage verifies the credentials against Returnista before storing them, then immediately starts an initial sync of your return history. Credentials that fail are never saved.

The first sync takes a few minutes on a large history. After that, returns are kept up to date automatically.
{% endstep %}
{% endstepper %}

### What you get

The **Returns** view inside **Business & Revenue**:

* **Return rate per channel** — which traffic sources bring customers who send things back.
* **Return rate per campaign** — the same question one level down, where the differences are usually larger.
* **Net revenue** — revenue after returns, which is the figure that should drive budget decisions.

This is the integration that most often changes someone's mind. A campaign with a strong ROAS and a 45% return rate can be worth less than one that looks mediocre and keeps its sales — and nothing else in your reports will tell you that.

### Reading the numbers

{% hint style="warning" %}
**A return lands weeks after the sale.** A customer buys in week 1 and returns in week 4, so the current month's return rate always looks better than it will turn out to be. Never compare a recent period's return rate against a settled one — the recent one is incomplete by definition, not better.
{% endhint %}

**Return rate is a property of the product as much as the channel.** Clothing returns more than electronics. A channel selling mostly apparel will show a higher rate without performing worse. Compare like for like.

**Returns are attributed to the original order.** So a channel's return rate reflects the traffic that made the sale, which is exactly what you want for budget decisions — but it means a channel's history keeps changing as returns arrive.

### Troubleshooting

**The credentials are rejected.** Check the account ID and the key. A regular user API key is not a Service User key; only the latter works for integrations.

**Connected, but no returns.** Either the account genuinely has no returns in the period, or the initial sync is still running. Give it a few minutes and check the period.

**Return rate looks impossibly low.** Check the period — see the warning above. A recent period has not had time to accumulate returns.

**Returns do not line up with orders.** Returns are matched to the original order, so a return of an order from before your webshop integration was connected has nothing to attach to.

Still stuck? Contact <support@adpage.io> with the container and the account ID — never the key.


---

# 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.adpage.io/data-and-insights/marketing-integrations/returnista.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.