GTM4WP 2.0.0 Release Candidate is available for download
Release candidate of GTM4WP 2.0 is out. You can download it from GitHub.
Download from here:
https://github.com/duracelltomi/gtm4wp/releases/tag/2.0.0-rc1
What changed since beta 3
- The experimental “Reliable purchase tracking” option can no longer produce a second purchase event on the same thank-you page. A page view that already carries the purchase event never arms the fallback, so the two cannot both fire even when the “Do not flag orders as being tracked” testing option has switched the usual de-duplication guards off.
- A product data payload that cannot be written as JSON no longer breaks the tracking scripts on a product page. This happens when another plugin’s filter puts a value into the product array that PHP cannot convert to JSON, or replaces the array with nothing at all. The add-to-cart click and variation-selection handlers used to raise a script error, or push an add_to_cart event with no product and no value. Both paths now skip the event for that one product, the way the product list and cart trackers already did.
How to install it
Download the file named duracelltomi-google-tag-manager-for-wordpress-2.0.0-rc1.zip from the release page. Do not use the source code archives that GitHub generates on the same page, because the compiled scripts are not stored in the repository and those archives will not work as a plugin.
In your WordPress admin, go to Plugins, Add New Plugin, Upload Plugin, and upload the file. WordPress will ask whether to replace the version you have. If you are already running beta 3, install rc1 over it the same way.
Please test this on a staging copy of your site first. This is a pre-release and I do not recommend it for a production site yet.
The stable release stays 1.22.5
The version served by wordpress.org is still 1.22.5, so nobody receives 2.0 as an automatic update. If you want to go back after testing, install 1.22.5 again, either by uploading it or with a rollback plugin. Your settings are migrated when 2.0 activates and the old option format is kept in sync, so a downgrade keeps your configuration, but please take a backup before you start.
Feedback
If something does not work, or a data layer value is not what you expect, please open an issue so that it can be fixed before the final release:
