WooCommerce

We have not shipped a WooCommerce install. This is the shape we would expect, and the specific things we would confirm with you, starting with the cart-total selector on your actual theme, since WooCommerce themes vary enormously.

Not done: no WooCommerce 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 WooCommerce. 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 WooCommerce-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 wp_enqueue_script or wp_footer in a child theme, or a tag-manager plugin. Site-wide is fine
Adapter	dom against .order-total .woocommerce-Price-amount or your theme's equivalent — we would agree the exact selector with you, since themes vary enormously; datalayer if you run a GA4 plugin that emits one
Page detection	The cart page path is whatever your permalink says. */cart and */basket are in the defaults; a translated or renamed slug needs adding
Claim moment	The order-received (thank-you) page is yours, so the on-page card should work. woocommerce_thankyou also gives you a natural place to persist a gwp:selection payload if you would rather claim by email
We would confirm	The total selector on your actual theme; whether your cart updates over AJAX; whether you want the card on order-received or a block in your WooCommerce email

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 WooCommerce. We would rather scope it than have you find the gaps. (/support is the shopper help page, not developer support.)