WP Full Picture loads tracking files at specific places and with specific dependencies. Unfortunately, this causes issues with some settings of caching solutions, which change the placement and order of loading these files.
To make sure that everything works correctly, check the settings of your caching plugin / solution and make these changes:
Do not remove version numbers from files
Some caching tools remove version numbers from files loaded by the browser. This stops them from downloading new versions of these files when they are available, and breaks tracking.
Do not combine JavaScript files
If you combine JS files, WP Full Picture will not be able to block specific tracking scripts installed by other plugins (see the settings in the Consent Banner module).
Do not save inline scripts in a separate file
WP Full Picture adds some JavaScript data to the HTML of the page to make sure that it is available when needed. When this data is saved in a separate file, it can load after the scripts that need them, breaking tracking as a result.
Do not change the order of loading JavaScript files
WordPress developers can choose when a JavaScript file loads (in the head of the document or in the footer) and what other files need to load before it (as a dependency).
However, caching solutions can change this order by deferring, asynchronous loading and delaying execution of these files, which breaks tracking.
Turn off Deferring, Asynchronous loading and Delaying Execution of JavaScript files or set exceptions for:
- fupi-helpers.js
- fupi-consb.js
- /wpfp/js/head.js
- fupi-woo.js (if you use WooCommerce)
- jquery.js (if you use WooCommerce)
- hooks.js (if you use WooCommerce)