Magento / Adobe Commerce

We have not shipped a Magento install. This is the shape we would expect, and the specific things we would confirm with you, starting with how your Knockout-rendered cart summary exposes a total we can read.

Not done: no Magento store has been through a real install

Nothing on this page is a report from a live install. It follows from how the tag behaves, not from anything we have watched it do on Magento. Treat every "likely" below as a question, not a promise. The two platforms we have proven end to end are Shopify and custom / headless; where we stand puts all six in one table.

What we can tell you without hedging is how the tag itself behaves. Nothing in it is Magento-specific, and only one path in it is Shopify-specific: the cart-attribute writer, which is off unless you are on Shopify with the order-email channel enabled. Page detection, the three cart adapters, the click id, the claim URL and the gwp:selection hook are all platform-neutral. That is why we can describe the shape below with some confidence, and still not claim we have walked it.

The shape we would expect

Tag placement	Likely a layout XML update or a small module adding the script to the default layout handle; a GTM container works too
Adapter	datalayer if you run GTM or a data-layer extension; otherwise dom against the summary total. A Knockout-rendered cart summary re-renders on every update, which the tag's re-evaluation already handles
Page detection	*/cart plus */cart/* cover /checkout/cart, /checkout/cart/index and locale-prefixed variants (/de/checkout/cart) with no configuration at all. Only a renamed or translated cart slug needs a pattern added (a config change on our side)
Claim moment	checkout/onepage/success is your page, rendered by your theme, so the on-page redemption card should work. This is the path we would aim for
We would confirm	How your success page exposes the order increment id (for the reporting join); whether the cart total is readable before Knockout hydrates, and if not, which event to hook

Where next

• What to bring to that conversation. Three answers get an unproven platform scoped in a single call. Bring a staging URL if you have one; the tag runs there as soon as the hostname is registered.
• Shopify: a platform we have actually installed, written up end to end. The best way to judge the size of the job.
• Install the tag, the platform-agnostic guide: snippet, page registration, adapters, verification, troubleshooting and CSP.
• Ask us something. Email support@gwpingenuity.com with [INTEGRATION] in the subject, saying you are on Magento. We would rather scope it than have you find the gaps. (/support is the shopper help page, not developer support.)