Solutions to common problems

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

Read it first

If you experience problems with WP FP, and you use a caching solution, go to its settings and make sure that it does not:

combine JS files,
combine inline scripts
or change loading of JavaScript files by forcing deferring or asynchronous loading.

So far, we have noticed issues with:

OceanWP theme – here’s everything you need to know.
Kubio theme – the theme uses CSS styles that prevent WP FP’s Consent Banner from showing. To fix it, please add to your website this custom CSS: body#kubio{transform: none !important;}
Vertice theme – the same problem and solution as above
Some setups of caching plugins – see the orange banner above

And these are limitations that cannot be fixed (at the moment):

Multilingual websites with different language versions in subdomains – if different language versions are defined in subdomains, e.g. es.example.com, pl.example.com, etc. then visitors will be asked for consent again.

This can have many causes. The most common ones are listed below.

Make sure you entered the correct ID in the required field in the module’s settings page
Clear cache of your caching plugin / solution
Make sure your tracking tool is set to load in the right countries (see the “Loading” section of the module’s settings page)
If you have a problem with Google Analytics or Google Ads, make sure that they are not loaded from the same Google Site Tag.
If you are the only person that visits the website (e.g. its developer), please do all previous steps and also the following (in this order):
1. open the site in incognito mode
2. make sure ad blocker is disabled
3. make sure the tracking tool you are testing is set to load in the country where you are in
4. disable your VPN
5. do not log into the website
6. agree to cookies in the consent banner (if you use it)
7. wait 24 hours before the data shows in the tracking tool

To make sure that an online scanner finds a specific tracking script on your website, please enable the “Force Load” option in the settings of the tracking module for the time when your website is being scanned.

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). Please read how to set your consent banner to x2 the number of consents and how to track 50% more traffic.

We found that Google Ads and Google Analytics show warnings to website owners about incorrect implementation of the Consent Mode, even though it works correctly. Please follow this guide to check if the consent mode works correctly.

Advanced Consent Mode will not impact your reports until your website is visited by more than 1000 people who agree to cookies in one day for the period of at least 7 consecutive days. Read more on Google’s documentation page.

This is typical and expected. Some tracking tools that are set to work in privacy mode, set technical cookies which online scanners report as problems.

If you see that after installing WP FP your traffic data reported by Google’s tools drastically changed, it may mean that:

they have combined tags (read how to separate combined tags)
they are installed multiple times (remove extra installations)
or use the same dataLayer (enable “Protect dataLayer” option in the settings of your GTM’s module)

If this did not help, please read the sections about the consent banner above.

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.

Learn how to test if your WooCommerce events are tracked
Learn what technical requirements must be met to track WooCommerce in this article.

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 (if available) and _fbc cookie (if available). 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 (Pro only). 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/10. In most cases, this score is only achievable when tracking purchases.

Some users may see notification in Meta’s Event Manager that IP address sent to Meta with Meta CAPI is different from the one reported by Meta Pixel – IPv4 instead of IPv6. If you see this message, disregard it. Most internet users use IPv4. Check your IP address here.

If an IP address is in IPv4 format Meta reformats it to IPv6 by adding empty values to it. We are not doing this internally in order to leave reformatting to Meta. The mismatch does not affect your campaigns.

We found that some translation plugins that translate content “on the fly”, like Linguise, try to translate product data output by WP Full Picture. In order to fix it, please set a rule in its settings that will prevent translation of content inside HTML elements with classes “fupi_cart_data” and “fupi_cart_item_data”.