> 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/faq/debugging-monitoring/purchase-events-not-firing-from-woocommerce.md).
# Purchase events not firing from WooCommerce
Troubleshoot a missing trytagging\_purchase event from a WooCommerce checkout, including multilingual (WPML) setups.
If the `trytagging_purchase` event does not fire from your WooCommerce checkout, use this page to find the cause and fix it.
***
### Common causes
The `trytagging_purchase` event usually fails to fire for one of these reasons:
* The AdPage Tagging plugin was customized after installation.
* A WooCommerce feature or another plugin conflicts with the AdPage Tagging plugin.
***
### Solutions
WooCommerce order data can be picked up in more than one way. If the standard flow does not produce a `trytagging_purchase` event, enable **Use old purchase flow** in the plugin settings. This sends the event through a different data flow.
***
### Required settings
Whichever flow you use, make sure these fields are always filled in:
* **URL**
* **GTM ID**
* **Loader ID**
Save your changes, then place a test order to confirm everything works correctly.
***
### Multilingual environments (WPML)
If your WooCommerce store runs in multiple languages through WPML, treat every language as its own environment. These settings are not shared automatically between languages, so the plugin needs to be configured separately for each language (and for each domain, if your WPML setup uses a separate domain per language).
To check that every language is configured correctly, open the language switcher in your WordPress backend, switch to each language, and confirm the plugin's fields are filled in for that language too.
See [Multilingual environments (WPML)](https://docs.adpage.io/documentation/integrations-websites/woocommerce#multilingual-environments-wpml) on the WooCommerce integration page for the full walkthrough and a step-by-step check.
***
### Still not working?
If the `trytagging_purchase` event still doesn't fire after checking the above, reach out to our support team. You can find the Loader ID in your AdPage container's Tagging Pixel instructions.
---
# 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/faq/debugging-monitoring/purchase-events-not-firing-from-woocommerce.md?ask=&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.
