When ecommerce data disappears after moving GTM installation to Complianz, check whether GTM4WP was deactivated or its store integration was disabled. Loading a container and producing WooCommerce events are different jobs. A successful page_view does not prove that product or purchase data exists.
Compare the setup before and after migration
Record the old container installer, new installer, GTM container ID, data-layer variable name and plugin versions. Check the public page rather than relying only on settings screens. If the container loads twice, resolve ownership before investigating event counts.
GTM4WP's container settings reference says that setting container placement to Off leaves its data layer active. Deactivating the plugin is not the same operation. Complianz's integration guidance describes a configuration where Complianz installs GTM while GTM4WP's container output is off.
Use that arrangement only when it matches the approved integration. Do not switch a working installation simply to reproduce a settings screenshot.
Find the first missing event
Open Tag Assistant on a staging store with synthetic product and order data. Follow one product view, one add-to-cart and one sandbox checkout. At each stage, check whether the event and ecommerce values reach the data layer before asking whether a destination tag fired.
The GTM4WP WooCommerce settings reference identifies Track e-commerce as the gate for its store hooks. Check that setting when the entire event family is missing. If only one field is absent, inspect the setting controlling that field and the event on which it becomes available.
Installer: One intended container. Producer: Store integration enabled. Timing: Read the relevant event. Purchase: Compare sandbox order values. Explanatory checklist, not a customer test result.
Match the trigger to the data's actual arrival
Do not assume all cart data exists on the initial page event. GTM4WP documents a separate gtm4wp.cartData event when its cache-safe data layer is enabled. A tag that reads cart values before that event may receive blanks even though the values appear later.
Record a short timeline: container initialization, relevant ecommerce push, tag evaluation and outgoing request. Keep the variable name consistent between the producer and container. If a custom data-layer name is used, verify both sides instead of renaming one in isolation.
| Observation |
Investigate next |
| No container |
Installer or consent-dependent loading |
| Container present, no store events |
GTM4WP activation and ecommerce setting |
| Event present, variables blank |
Event timing, variable paths and names |
| Variables correct, duplicate requests |
Multiple tags or destinations |
Verify consent and order semantics
Repeat the approved no-choice, rejection and acceptance scenarios. Missing advertising requests can be intentional; missing internal store data and denied tag execution must not be confused. Never force consent to recover a conversion counter.
Use a sandbox purchase and compare transaction ID, currency and value with the expected order. A draft checkout is not proof of payment. For installer confusion, return to the Complianz integration ownership guide. HandL WP can trace the event pipeline while keeping one deliberate container installation.
References reviewed October 12, 2026. Examples are explanatory, not customer test results.