Solutions to common problems

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

For users of WP FP version 9 and earlier

Some settings of caching plugins may cause issues with WP Full Picture. To make sure that WP Full Picture works correctly, apply these changes to the settings of your caching plugin/solution:

  1. Do not remove version numbers from files
  2. Disable combining JS files (it prevents WP FP from managing tracking scripts installed by other plugins)
  3. Disable saving inline scripts to separate files (it causes problems with tracking WooCommerce events)
  4. 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)

Solutions to common problems

So far, we have noticed issues with:

  • Bricks builder – the builder removes one of the core WooCommerce hooks that WP FP needs to track products in lists. Here’s a fix.
  • OceanWP theme – consent banner customization does not work in this theme. Read about a workaround.
  • 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

If your website shows different language versions in different subdomains, e.g. es.example.com, pl.example.com, etc. then I have bad news for you – at this moment this cannot be solved.

If your site keeps language versions in subfolders, e.g. example.com/fr/ or in query parameters, e.g. example.com?lang=fr, then you can easily fix it – simply save the ID of the privacy policy page in the consent management module.

There are two reasons this may be happening:

  1. Your WordPress may have too little memory to generate the file. Increase the memory allocated to your installation to fix it.
  2. If you are using an SMTP proxy to deliver your emails, make sure that it works correctly. Sometimes, SMTPs require periodical refresh of authentication keys.

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

  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 right countries (see the “Loading” section of the module’s settings page)
  4. If you have a problem with Google Analytics or Google Ads, make sure that they are not loaded from the same Google Site Tag.
  5. 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.

Do not worry. Everything is fine. You may see this information if you have enabled tracking of broken links.

Whenever a user tries to visit a page that does not exist, WP FP adds to it parameters which let you track this link in various tracking tools. This slightly changes the address of the page before tracking tools are loaded. As a result Google “thinks” that the page with the original address is not tagged.

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 (change dataLayer’s name in the settings of your GTM’s module)
gtm protect datalayer option

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.

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.4 to 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.

Higher scores for other events (pageviews and other non-purchase events) can only be achieved if you require your visitors to log in to browse your site. Only then will WP FP have all the extra information (email, address, phone) to send to Meta and increase the score.

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 itself 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. Why does meta point it out as an error? We are as puzzled as you are.

WP Full Picture does not add a border around the buttons. If you see a border, then probably your theme adds it. To remove it, you can either:

  1. Remove the border in your theme options
  2. Set a border in WP FP that matches the color of the buttons
  3. or paste the CSS style below in the “Additional CSS” section in the theme Customizer (WP Admin > Appearance > Customize > Additional CSS)
.fupi_cta, .fupi_button{
   border-width: 0 !important;
   outline-width: 0 !important;
}

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”.

Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments