Solutions to common problems

This page lists the most common problems you can encounter in WP Full Picture and ways of solving them.

Before everything else

Some caching plugins heavily modify JavaScript files used by WP Full Picture, which causes issues.

If you experience problems with WP FP, but none of the solutions below fix it, please deactivate your caching plugin/solution to see if it fixes the problem. If it does, then activate your caching solution, go to its settings and turn off combining JS files and processing inline scripts.

I installed a tracking tool with one of the modules, but it does not work

  1. Make sure you entered the correct ID in the required field in the module’s settings page
  2. Clear cache of your caching plugin / solution
  3. Make sure your tracking tool is set to load in the country you are in (see the “Loading” section of the module’s settings page)
  4. Check if your tracking works in incognito mode of your browser with AdBlock disabled
  5. If you have a problem with Google Analytics or Google Ads, make sure that they are not loaded from the same Google Site Tag.
  6. If a tracking tool is installed, but you see no traffic data in the tracking tool, wait 24 hours for the data to show up in its dashboard (unless it lets you view real-time traffic)

Tracking script cannot be found on my website

Some tracking tools check if their tracking script is correctly installed on a website.

If they inform you that a tool is not installed, in most cases it means that the script did not load for the robot which was checking the installation. It can happen when:

  • you are logged as an administrator or an excluded user (these users are not tracked)
  • you disabled tracking in a consent banner
  • when you are in a country which was excluded from tracking (with geolocation)
  • and several other cases

To avoid this:

  1. please enable the ¨Force Load¨ option in the settings of the tracking module
  2. or exactly follow the installation instructions provided in WP Full Picture’s sidebar.

Do not worry, your traffic is fine. It did not drop, but it is no longer reported. Simply a portion of your visitors decline tracking in the consent banner (when it is set to work in opt-in mode).

To maximize the accuracy of your traffic measurements, please use a tracking tool that does not require consent banner (does not use cookies and does not collect personal information about your users).

Advanced Consent Mode will not impact your reports until your website is visited by more than 1000 people who consent to cookies. Before that, all the data tracked by Google Analytics running in consent mode will be unavailable to you. Read more on Google’s documentation page.

We found that Google shows warnings to website owners about incorrect implementation of the Consent Mode even though it works correctly. These notifications may show at the top of Google Ads and Google Analytics panels. Please follow this guide to check if the consent mode works correctly in Google Ads and Google Analytics.

This is typical and expected. Scanners like CookieChecker, Termly or Piwik Scanner use lists of known cookies that should be blocked. If they encounter any that they don’t know (for example, set by WP Full Picture) they report a problem.

Some (like Piwik Scanner) also report as problematic if your website is hosted outside the EU or downloads any files from non-European servers.

And finally, if you load a tool like Google Analytics or HotJar in privacy mode, then they can still set some functional cookies (with the same name as before) which online scanners will also report as problems.

I see doubled or tripled ecommerce events in the Google Tag Assistant

Doubled or tripled events in your Tag Assistant dataLayer preview can show up because GTM, Google Analytics and Google Ads use the same datalayer.

If you only use Google Analytics and Google Ads on your website then there is nothing to worry about. WP Full Picture marks events from Google Analytics and Google Ads with a special “send_to” parameter, so that the data is sent only to the right receivers.

If you also use a GTM module on your site, you need to enable the “Protect dataLayer” option in the GTM module’s settings.

gtm protect datalayer option

This will rename the dataLayer that GTM uses to “fupi_dataLayer” which will prevent Google Analytics and Google Ads from pushing to it their own events.

An event or data is not tracked

If you enabled tracking of a specific data type or a user action, but you are not seeing it in your reports, please check these things in this order:

Make sure that your tracking tool is set up to receive this piece of information (some tools require you to register the type of data that you will send them). WP Full Picture can track and send something to the tracking tool, but if this tool is not set up to receive it, then you will not see this data in your metrics.

Some events are not tracked in my WooCommerce store

WP Full Picture is set up to track stores that use standard WooCommerce hooks and HTML. Some plugins and themes may, however, either not use them or highly modify them. In such case, tracking will not work.

Facebook CAPI’s “events match quality score” is very low

Events match quality score shows how well Facebook is able to match events that happen on your website to Facebook’s users. To do this, Facebook needs as much data as possible.

By default, WP Full Picture sends to Facebook the IP address of the user’s device, ad-click identifier (if available) and the contents of _fbp cookie. However, this data will result in events match quality scores around 4-5/10.

To increase this score, you can enable the advanced matching option. When you do this, WP Full Picture will send to Facebook the hashed email address and physical address of the visitor (if it is known to WP Full Picture). This will increase the quality score to around 8-9/10. In most cases this score is only reached when tracking purchases.

How can I save visitor’s consents?

Saving visitor’s consents will soon be available in the Pro version of the plugin. Consents will be saved in the WP Full Picture’s cloud servers in France.

Why only in Pro, and why in the cloud and not in the WP’s database?

  1. Consents saved in the WordPress database can be easily manipulated simply by changing values in the database, hence they will not be treated by courts as valid proofs of consent.
  2. Saving many consents in the database can drastically increase its size, which can be a problem on weaker hosts.
  3. To increase the likelihood that the consent will be treated as a proof, WP Full Picture will not only save the consents and user’s IP, but also:
    • copy of all the texts of the consent banner, that were visible at the moment when the consent was made
    • copy of the privacy policy current at the time of consent
    • copy of plugin’s settings at the time of consent
    • user’s user agent information and screen resolution
  4. Hosting big amounts of data, maintenance, security audits and administration of cloud solution is not free, thus it will be available only for paying users.

Why is the plugin loading clever_ads.js file?

This file is used for testing if the visitor uses ad blockers. The file is 100% safe and this is its content:

adblock test script

How does it work?

The script creates an empty, invisible <div> on site. If WP Full Picture cannot find it, then it is assumed that an ad blocker blocked the script. The information whether the visitor uses an ad blocker is available in the fpdata javascript object and can be tracked by some tracking tools.