> 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/extensions/plugins/shopware-webhook-plugin.md).

# Shopware Webhook Plugin

Install and validate AdPage purchase webhooks for your Shopware store.

Use the AdPage Shopware plugin to forward purchase data from your store backend.

<a href="https://github.com/AdPageGroup/Shopware" class="button primary" data-icon="github">View the Shopware plugin</a>

### Before you start

Have access to your Shopware server, sales-channel configuration, and AdPage server container. Remove duplicate purchase webhooks before testing the plugin.

Back up your store and test the installation on a staging environment first.

### Install the plugin

{% stepper %}
{% step %}

#### Install AdPage Webhook Plugin

Open the plugin repository and install the plugin through Composer. Follow the repository installation instructions for your Shopware version.
{% endstep %}

{% step %}

#### Configure each sales channel

Open the AdPage plugin settings in Shopware. Select every sales channel whose orders you want to forward.

Enter the tagging URL for each selected channel. It must match the tagging URL configured in your AdPage server container.
{% endstep %}

{% step %}

#### Publish your changes

Save the plugin configuration and clear Shopware caches. Publish your Google Tag Manager server container after validating the integration in preview mode.
{% endstep %}
{% endstepper %}

### Validate the installation

Place a test order through each configured sales channel. Then confirm that the purchase webhook reaches your AdPage server container.

Check that the order includes the expected transaction ID, value, currency, and items. Use Google Tag Manager server preview to verify your downstream tags fire once.

### Available Shopware webhook event

The plugin sends the completed order as a purchase webhook. It is sent from the Shopware backend.

This protects purchase tracking when browser-side scripts do not run. Use it with your storefront ecommerce data layer for complete tracking.

See [Shopware](https://docs.adpage.io/integrations-websites/shopware.md) for data layer and GTM setup.

{% hint style="warning" %}
Do not test purchases with a live payment method. Use a test payment method or a staging store.
{% endhint %}

### Troubleshooting

If the webhook does not arrive, confirm that the plugin is active. Check the tagging URL for the affected sales channel and clear Shopware caches.

If purchases duplicate, disable overlapping Shopware or third-party order webhooks. Retest with one test order per sales channel.

#### Settings

Will set the webhooks per sale channel. You need to set the webhook up per sale channel.&#x20;


---

# 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/extensions/plugins/shopware-webhook-plugin.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.
