For Shopware 6.6 / 6.7

Google Ads

Tracking · SlGoogleAds

Every conversion counts.

Conversion tracking and remarketing across browser and server – so Google Ads counts correctly even when payments are confirmed late.

Request a consultation See features

Google Ads

conversion
view_item
view_item_list
view_search_results
add_to_cart
purchase

Features

Browser and server conversions, deduplicated automatically via the order number.

Setup

OAuth access, a conversion action and a running queue worker.

Support

Personal support with setup questions and continuous development.

Sent twice. Counted once.

Our tracking extensions report key events such as the purchase along two paths: the pixel in the browser and the platform’s server API. If one path fails – ad blockers, late payment confirmations – the conversion still arrives.

Your shop

purchase (conversion)

Browser

gtag.js

after consent

Server

Data Manager API

Purchase only once paid

Google Ads

Counted once

Deduplicated via the order number

Your shop
purchase (conversion)
ViewContent · InitiateCheckout · Purchase
ViewContent · AddToCart · Purchase
Browser
gtag.js
after consent
Server
Data Manager API
Purchase only once paid
Google AdsCounted once
Deduplicated via the order number

How long a not-yet-paid order stays attributed: 63 days (default)

One ID, two paths

Browser and server share an ID – the platform recognises duplicates and counts the event once.

Paid first, then reported

The server-side purchase is only sent once the order is paid – including invoice, prepayment or late-confirmed PayPal.

Hashed, never plain

Email, phone and name are SHA-256 hashed on your server. Raw personal data never leaves the shop.

What the extension does

Tracked events

conversion
view_item
view_item_list
view_search_results
add_to_cart
purchase

Conversion via gtag.js on the order-finish page plus dynamic remarketing.
The same conversion is also sent server-side via the Google Data Manager API – Google removes duplicates using the order number.
Click IDs (gclid, gbraid, wbraid) are captured on landing; the upload only happens once the order is paid.
Enhanced Conversions: email, phone and name are SHA-256 hashed on the server.
Consent Mode v2, tied to Shopware’s marketing consent.
Optionally server-only, next to an existing GTM setup.

Requirements & setup

Shopware 6.6 or 6.7, PHP 8.2+, configured per sales channel.
Google account approval for the Data Manager API.
OAuth client with refresh token, customer ID and conversion action.
A permanently running queue worker (Symfony Messenger). The browser tag works straight away.

Status: Compatibility declared for Shopware 6.6 and 6.7. Availability on request.

Good to know

Honest limits – so you know exactly what you can rely on.

Orders placed before setup are not uploaded retroactively.
If GTM also fires the Ads conversion, the browser side counts twice.
GDPR deletion requests are handled manually.

Works with the Consent Manager

Google Ads only loads after “Marketing” consent. Together with the Consent Manager, your shop gets an equally prominent “reject all” and blocks scripts reliably until consent is given.

See the Consent Manager

Questions about Google Ads

Question not listed? Free consultation

Do I need approval from Google?

For the server channel, yes: your Google account must be approved for the Data Manager API, which can take time. The browser tag works straight away, and no developer token is needed.

Does it work alongside Google Tag Manager?

Yes, optionally server-only next to your GTM setup. If GTM also fires the Ads conversion in the browser, it counts twice there – so enable the browser conversion in only one place.

What about PayPal or payment by invoice?

The click ID is captured on landing and only uploaded once the order is paid. Unpaid orders keep their attribution for 63 days by default (configurable).