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

# Itsperfect

Connect Itsperfect to bring the POS receipts of your own stores into AdPage: revenue per store per week, next to your webshop. Available on request.

Itsperfect is the ERP with a POS for fashion brands. Connect it, and AdPage reads the receipts from the tills in your own stores, so store revenue can sit next to your webshop revenue: per store, per week.

AdPage only reads: it cannot create, change or delete anything in Itsperfect, and nothing is written back.

{% hint style="info" %}
**Itsperfect is available on request.** The tile only appears for accounts it has been switched on for. Ask your contact at AdPage, or <support@adpage.io>, to turn it on for your container.
{% endhint %}

### Before you start

You need three things:

* An **AdPage login with access to the container** of your webshop. The connection is stored per container.
* Someone who can **create an API token in Itsperfect**, usually an Itsperfect admin.
* The **address of your Itsperfect environment**: the web address you use to log in to Itsperfect. Not sure? Itsperfect support (<support@itsperfect.io>) can tell you.

### Step 1: create an API token in Itsperfect

{% stepper %}
{% step %}

#### Add a token

In Itsperfect, go to **Settings › API** and choose **Add**. Give the token a name you will recognise later, such as *AdPage*.
{% endstep %}

{% step %}

#### Give it read rights only

On the permissions tab, allow **reading (GET)** on these four, and nothing else:

| Permission  | What AdPage does with it                                            |
| ----------- | ------------------------------------------------------------------- |
| `orders`    | Reads the receipts from your tills (POS orders)                     |
| `stores`    | Reads your own stores, so you can choose which ones count           |
| `customers` | Checks, for a sample of receipts, whether a customer was registered |
| `payments`  | Checks, for a sample of receipts, whether the amounts include VAT   |

AdPage never needs write rights (PUT, POST or DELETE).
{% endstep %}

{% step %}

#### Copy the token

Save and copy the token. You paste it into AdPage in the next step.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Use a general API token, not the token of a webshop.** Itsperfect also gives every webshop its own token (under **Settings › Webshops**), but that one only sees webshop orders, not the receipts from your stores.

**Do not send the token by email.** Paste it into AdPage yourself. Afterwards AdPage only shows its last four characters.
{% endhint %}

Some Itsperfect environments also ask for a **username and password** for the API, an extra layer of security that is set in Itsperfect. If yours does, have those at hand too.

### Step 2: connect in AdPage

{% stepper %}
{% step %}

#### Open the tile

Go to **Integrations** and select your container at the top of the page. Open the **Itsperfect** tile in the E-commerce group. Searching for "pos" or "store" finds it too.
{% endstep %}

{% step %}

#### Fill in the address and the token

* **Itsperfect address**: the address where you log in to Itsperfect. If it ends in `/api/v2`, that is fine too.
* **API token**: the token from step 1.
* Does your Itsperfect environment ask for a username and password? Tick **Itsperfect also asks for a username and password** and fill them in.
  {% endstep %}

{% step %}

#### Test and connect

Select **Test & connect**. AdPage first tests the connection: it fetches your stores and counts the POS receipts of the last 7 days. Only when that works is anything saved. Want to check first? **Test only** does the same, without saving.
{% endstep %}
{% endstepper %}

### Step 3: choose the stores that count

Under **Stores** you see your stores from Itsperfect, each with its type (store or shop-in-shop) and country. Active stores and shop-in-shops are switched on; a store that is not active in Itsperfect is off.

Switch off any store that should not count, and select **Save choice**. Opened a new store? Select **Refresh list**: new stores are added, and the stores you already set keep their choice.

### Step 4: run the test

The test run reads one week of POS receipts and shows what AdPage makes of them. This is how we check together that the numbers are right before they are used anywhere.

1. Under **Test run**, pick **A day in the week** you want to check, or leave it empty for the last full week.
2. Select **Run test**.
3. Compare the revenue per store with the weekly report in Itsperfect for the same week. AdPage shows revenue **excluding VAT**.

Next to the totals, the test run answers the questions we cannot see from the outside:

* whether the amounts in Itsperfect include VAT or not;
* how returns and exchanges are recorded, and that sold gift cards are not counted as revenue;
* what share of the receipts has a registered customer;
* how many other orders (wholesale and webshop) there were that week, which AdPage leaves out of store revenue.

{% hint style="info" %}
**Pick a week with a return in it**, so the test also shows how returns are recorded. Then let us know at <support@adpage.io> whether the totals match your report. A difference of a few euros per store is worth mentioning too.
{% endhint %}

### What AdPage reads and keeps

AdPage reads your POS receipts and your stores, and for a sample of receipts the customer and the payment. Of the wholesale and webshop orders it only counts how many there are, to leave them out. It does not read stock, prices or purchase data.

It keeps:

* the connection: the address, and the token and password, which stay on the server and are never shown again (only the last four characters of the token);
* your stores, each switched on or off;
* the latest test run: **counts and totals only**. No names, email addresses, phone numbers or postcodes of your customers are stored.

### Your Itsperfect API limit

Itsperfect allows **750 API requests per hour** for your whole brand, shared by all your connections (webshop, logistics, AdPage). AdPage stops by itself when fewer than 150 are left, so your other connections keep running. A test run uses at most 45 requests, connecting only a few.

### What comes next

After the test run, these are the next steps. We switch them on with you once they are ready:

* **Store revenue in the Marketing Mix Model**, per store per week, next to your webshop revenue.
* **Regional measurement on the customer's postcode**, so a regional test measures webshop and stores together.
* **POS purchases of known customers as offline conversions** to Google Ads and Meta.

### Troubleshooting

**The Itsperfect tile is missing.** It is switched on per customer; see the note at the top of this page.

**Itsperfect rejects the key.** The token is wrong or misses a permission. Check the four read permissions from step 1. If your environment uses a username and password for the API, check those too. To enter a new token, select **Change address or key** in the tile.

**The stores can be read, the orders cannot.** The token misses the read permission on `orders`.

**No stores appear.** The token misses the read permission on `stores`.

**The address is rejected.** Use the address where you log in to Itsperfect, starting with `https://`.

**The limit for this hour is reached.** Wait until the time AdPage mentions and try again.

**The previous test just ran.** A test run can be done once every two minutes.

**Disconnecting.** Select **Disconnect** in the tile. AdPage deletes its copy of the key. The token keeps working in Itsperfect until you delete it there, under **Settings › API**.

{% hint style="warning" %}
**Itsperfect is not covered by the daily connection check**, so a broken connection does not email you. If you change the token in Itsperfect, check the tile afterwards.
{% endhint %}

Still stuck? Contact <support@adpage.io> and include the container and what the tile showed.


---

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