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

# Shopware

Connect Shopware 6 with an integration access key for orders, revenue and product data.

Connect Shopware 6 so AdPage reads orders and product data from your shop. Shopware uses an Admin API integration with a client ID and secret, so this is a credential connection rather than an approval flow.

AdPage only reads.

{% hint style="info" %}
This is for **Shopware 6**. Shopware 5 has a different API and is not supported.
{% endhint %}

### Before you start

You need administrator access to the Shopware admin, and a shop reachable from the internet.

You will create an **integration**, which gives you two values: an **Access key ID** and a **Secret access key**.

{% hint style="warning" %}
**The secret is shown once.** Shopware displays it when you create the integration and never again. Copy it before closing the dialog.
{% endhint %}

### Create the integration in Shopware

{% stepper %}
{% step %}

#### Open the integrations screen

In the Shopware admin, go to **Settings → System → Integrations** and select **Add integration**. Name it `AdPage`.
{% endstep %}

{% step %}

#### Give it read access

Assign a role that can read orders, products and sales channels. Shopware's built-in administrator role works; a custom read-only role is better practice if you have one.
{% endstep %}

{% step %}

#### Save and copy both values

Save, and copy the access key ID and the secret access key immediately.
{% endstep %}
{% endstepper %}

### Connect Shopware in AdPage

{% stepper %}
{% step %}

#### Open the tile

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

{% step %}

#### Fill in the shop URL and both values

The **base URL** is your shop root — `https://yourshop.nl`, **not** the `/api` path and not the admin URL. AdPage appends the API path itself.

Paste the access key ID and the secret access key.
{% endstep %}

{% step %}

#### Save

AdPage calls your shop before storing anything and reads the default sales channel to prove the credentials work. Credentials that fail are never saved.

On success the tile shows the store name read from Shopware, confirming you connected the right shop.
{% endstep %}
{% endstepper %}

### What you get

Orders, revenue and product data in **Business & Revenue** and **Product Performance**, with order revenue feeding the **Marketing Mix Model**.

Where your shop sells through several sales channels — a webshop plus a marketplace, for instance — those can be separated, which matters because marketplace orders are not driven by the advertising in your reports.

### Reading the numbers

**Order state matters.** Shopware tracks order state, delivery state and payment state separately. A revenue total that looks wrong is usually counting cancelled orders, or excluding ones not yet paid.

**Sales channels sit in one API.** All channels come back together unless scoped. Ask support to scope the container if it should cover one channel only.

**Marketplace orders arrive through the shop.** Where bol.com or a similar marketplace flows into Shopware, that revenue is in the same table as your own. It is genuine revenue, but it is not attributable to your campaigns — splitting it out is usually the right call for reporting.

### Troubleshooting

**The connection test fails immediately.** Check the base URL: shop root, `https://`, no `/api`, no `/admin`. This is the most common mistake on this integration.

**"Invalid client credentials".** The access key ID or secret is wrong, or the integration was deleted in Shopware. Create a new one — you cannot recover a lost secret.

**Connected, but no orders.** The integration's role cannot read orders. Edit the role in Shopware and grant order read access.

**It worked and then stopped.** The integration was deleted, or its role changed. Check under **Settings → System → Integrations**.

Still stuck? Contact <support@adpage.io> with the container and the shop URL — never the secret.


---

# 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/shopware.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.