Thomas Geiger
Forum Replies Created
-
Hi Everyone,
Sorry for this late reply.
Purchase tracking usually fails because of several reasons, mostly I see two that usually are the root cause:
- customized order received page that does not mimic all the functionality of the original order received page => reach out to the developer and ask them whether they support the woocommerce_is_order_received_page hook and/or the woocommerce_thankyou hook
- payment gateway executes scripts during order processing in the background that marks the order as being already tracked therefore while the order received page loads, purchase event is omitted to prevent double tracking => there is an option in GTM4WP under Integration => WooCommerce where you can turn on a checkbox to prevent an order from being flagged. Turn on this option and try to place an order
Thanks, perhaps I will try to re-release the version using v1.20.1 on Monday
Can you post which payment gateway plugin you are using?
This happens usually if you are using another plugin that alters the default order received page in a way that breaks communication with 3rd party plugins like GTM4WP.
Please check if you are using any such plugin.
One other reason can be if you are using a payment gateway plugin that calls some WooCommerce functions in the background making GTM4WP to mark the order as being already tracked before the order received page is loaded. When the real thank you page is shown, the order is already marked and GTM4WP does not fire the purchase event to prevent double tracking of the same conversion. You can test this case by turning on the “Do not flag orders as being tracked” option in GTM4WP under WooCommerce settings.
Unfortunately I can not tell you which plugin of the thousands of plugins is compatible with a earlier version of GTM4WP. If you have a testing/dev version of the site, you should test all features there and if you do not see any issues, publish the site.
This happens usually if you are using another plugin that alters the default order received page in a way that breaks communication with 3rd party plugins like GTM4WP.
Please check if you are using any such plugin.
One other reason can be if you are using a payment gateway plugin that calls some WooCommerce functions in the background making GTM4WP to mark the order as being already tracked before the order received page is loaded. When the real thank you page is shown, the order is already marked and GTM4WP does not fire the purchase event to prevent double tracking of the same conversion. You can test this case by turning on the “Do not flag orders as being tracked” option in GTM4WP under WooCommerce settings.
Hi,
It is only possible if you set the container code to “OFF” in plugin settings and you put the modified container code into your theme manually.
Hi,
Please use this setup article to setup Enhanced Conversions. To be able to set this up, you will need to use the latest version of GTM4WP (min. v1.20)
Forum: Plugins
In reply to: [GTM4WP - A Google Tag Manager (GTM) plugin for WordPress] installationHi,
GTM4WP does not have any direct link to Google Analytics. Could you elaborate more on what you mean with “the link with Google Analytics”?
Hi,
v1.17 was the first version requiring PHP 7.4. The problem will be however that v1.16 or older might be not compatible anymore with other plugins’ newer versions (like WooCommerce). So to make sure everything “works”, you will also need to keep using old versions of other plugins.
@matiasquero but it has when updating in the standard way from WP.org?
Do you have a public test version of your site where you can activate v1.20 without affecting your live traffic?
Strange, a similar issue has been reported on a different thread yesterday but the error message there complains about another PHP constant.
My dev site is running on WP 6.4.3 and PHP 8.2 but does not generate such error messages.
Could you try updating the plugin from the GitHub release manually?
https://github.com/duracelltomi/gtm4wp/releases/tag/1.20
If this does not solve the issue, could you also post what PHP modules are currently active? Maybe it is possible to switch back to PHP 8.1 just to test whether the issue is around the PHP version?
@davidperez I double checked with PHP 8.2 and I do not see your error message. Could you reinstall the plugin or perhaps download the release from GitHub?
Hi,
If the log does not contain sensitive data or you can mask such data then pls lost the details. Also please let me know the version of your WordPress and PHP.
Thanks!