Skip to main content


What is the new "opt-in" feature in your plugin? Opt into what?

We started to collect telemetry from users who are willing to share some data with us, like WooCommerce, WordPress and PHP versions, or the shop language:

image (Click to expand)


This will help us to better prioritize our development roadmap for the plugin. For example, we’ve been working on translations recently and didn’t know which ones would be the most important ones (the ones with the highest user count). Unfortunately, the repository doesn’t provide us with much data about that.

Also, we will invest more time to build even more useful features and possibly add some pro features too.

If you wish to help us in this way, you can opt-in, but it is absolutely voluntary and won’t change how the plugin works in any way.

The number of conversions counted in Google Ads is less than what's actually reported in my shop. Why?

There are a number of reasons.

  1. Google Ads only counts conversions that have been triggered by an ad.
  2. The conversion window of Google Ads is typically 30 days (can be customized). That means Google Ads only counts conversions of clicks that happened during that time.
  3. If you compare Google Ads to Google Analytics, you also will not see the same numbers, as both have a different standard approach to measuring conversions:

What if a user refreshes the thank-you page multiple times, does it recount? How do you handle duplication?

We also transmit the transaction ID to Google Ads. This helps Google Ads to deduplicate all conversions that have been transmitted more than once.

This process doesn't run immediately in Google Ads but over a period of several hours after the conversion. So it might happen, that you will see a recent conversion duplicated but then fixed a few hours later.

I see issues in the back-end of my shop. Admin pages get rendered weird, and popups don't go away when I click to close them. How can I fix this?

You probably have some script or ad blocker activated. Deactivate it and the issues should go away. Usually, you can disable the blocker for just that particular site (your WooCommerce back-end).

Our plugin injects tracking pixels on the front-end of WooCommerce shops. As a consequence scripts of our plugin have been added to some privacy filter lists. The idea is to prevent the scripts from running if a shop visitor has some ad blocker enabled and wants to visit the front-end of the shop. This is totally ok for visitors of the front-end of the shop. But, it becomes an issue for admins of the shop who have a blocker activated in their browser and visit the back-end of the shop.

Unfortunately, there is no way for us to generally approve our scripts in all blockers for the WooCommerce back-end.

Therefore, we recommend admins of the shop to exclude their own shop from the blocker in their browser.

When I open the plugin settings, I see a warning flashing that goes away after half a second or so. What is this?

In rare cases scripts, that we use to render the settings page, get blocked. We use those scripts to make the interface faster and more useful. Without those scripts, the settings page would look horrible. And the reason why those scripts sometimes get blocked is ad- and script-blockers that have been installed in the browser of some users. Learn more

The warning that you see is only intended to be seen by those people who have an active script-blocker. The only way we have come up with so far, to detect if a script blocker is running, is the following:

In the first step, we output the warning into the HTML source of everyone who is accessing the page. And then, in the second step, we hide the warning with a script. This second step will only work for users who have no script blocker running. It is the safest way to be sure that the warning will be seen by users with script blockers. But this method has one downside. If the server is a bit slow, the scripts for people who don't have a script blocker running, get loaded slow, and therefore it takes half a second or so until the warning gets hidden.

If this happens to you, you can safely ignore the warning, since it means that no script blocker is running and all is rendered correctly.

In the Google Ads audience manager I see the warning ecomm_prodid never received. Why?

The plugin uses the newest version of the Google Ads dynamic data tracking code, which doesn't use the ecomm_prodid parameter anymore. This parameter was replaced with the view_item and items parameters. Google specifications

If you see the warning, this could have several causes.

  • You haven't set up the plugin correctly yet. You will need to enable dynamic remarketing within the plugin. Only then that tracking code will be injected.

  • You made the switch from the old to the new tracking code just recently. In that case, Google will need a few days before it picks up the new parameters and removes the warning.

  • Google Ads is reporting a false warning. The report shows, that a parameter is missing, but in fact, it is being transmitted and received by Google Ads. Look at the following example:

    image (Click to expand)

    Google Ads wrong audience tracking warning 1

If the warning doesn't go away, please reach out to us and ask for support.

Google Tag Assistant reports multiple installations of Global site tag (gtag.js) detected. What shall I do?


This warning is of very low severity. It can be safely ignored.

There are two main reasons, why this warning pops up.

  • You have activated more than one Google service, such as Google Ads and Google Analytics. During initialization gtag.js is configured once for each service. Google Tag Assistant detects this as a separate global site tag, but it should not. It is safe to ignore that warning.

We implemented this exactly as specified by Google.

image (Click to expand)

Google Tag Assistant multiple global site tag warning

  • Some other plugin also injects a gtag source file into the HTML output of the page. As a consequence, the gtag namespace will be declared two times. Technically this is no problem, as they both initialize exactly the same namespace. So one just overwrites the other. Therefore, it is safe to ignore that warning.

No conversions are being reported in Google Ads

There are several possible reasons why this can happen:

  • Cookie Management Platforms (cookie banners) might be blocking the conversion tracking
  • Off-page payment gateways need to be configured to redirect back to the purchase confirmation page. If that's not set up correctly, or if a user interrupts the redirect, no conversion is reported.
  • Google Ads only shows conversions that were triggered through an ad click. Please follow these testing procedures exactly: How to test conversion tracking
  • It can take up to 48 hours before the conversion appears in Google Ads
  • Either the conversion ID or the conversion label or both are wrong
  • If you are using caching you must make sure to exclude the purchase confirmation page
  • If you are using minification plugins, turn them off and try again. Some minification plugins break the conversion code
  • Users who disabled JavaScript or users who are blocking cookies (e.g. with ad blockers) can't be tracked

Using the pro version of the Pixel Manager for WooCommerce can alleviate some of those issues. For Google Analytics the Pixel Manager uses the Google Analytics Measurement Protocol to send purchase conversions which lifts the tracking accuracy to 100%.

Some paid ads pixels also offer server-to-server tracking (such as Facebook CAPI) which also increases tracking accuracy significantly. This is also only available in the pro version of the Pixel Manager.

You can get the pro version of the Pixel Manager from here

Not all conversions are being reported

Unfortunately, it is not always possible to track 100% of all conversions. There are several possible reasons why this can happen:

  • Some users might be using Brave browser (that blocks all trackers by default) or strict privacy settings in other browsers.
  • Some users might be using privacy-enhancing browser extensions that block Google Analytics and Google Tag Manager. Adblockers and other privacy-related browser extensions.
  • Browsers with strict privacy settings.
  • JavaScript is disabled in a browser.
  • Cookie Management Platforms (cookie banners) might be blocking the conversion tracking
  • Off-page payment gateways need to be configured to redirect back to the purchase confirmation page. If that's not set up correctly, or if a user interrupts the redirect, no conversion is reported.

The dismiss button doesn't work. Why?

You are using some kind of ad- or script-blocker in your browser. It blocks the script in our plugin that is responsible to dismiss the notification.

You have the following options:

  • Temporarily disable the ad- / script-blocker in your browser and then dismiss the notification.
  • Whitelist our scripts in the ad- / script-blocker.
  • Switch to a different ad- / script-blocker. Not all of them block our scripts.

We recommend whitelisting our scripts because they are also required on the plugin's settings page.


You might wonder why our scripts, but no others, get blocked by the ad- / script-blocker. The reason is that our plugin helps to track conversions for various ad platforms. And apart from blocking ads, many ad blocking service providers also block scripts that help track visitors and conversions. Because many of those providers are unable to distinguish if the scripts are being used for the front-end or the back-end, they simply block the scripts also on the back-end, thus triggering the issue you are facing. We've spent a considerable amount of time removing our plugin from the ad- and script-blockers. In some cases we succeeded, in others, we didn't.

Why is tracking accuracy so important?

You might ask yourself why tracking accuracy is important and why it can be low.

If for some reason only 20% of the visitors and conversions can be tracked, then paid ads platforms like Google Ads only get 20% of the data that they could get. Such a low accuracy prevents campaigns to run optimally. Actually, the difference in campaign performance can be as large as day and night. We've seen revenues and profit margins more than double in certain cases, just by fixing the visitor and conversion tracking. It doesn't mean that accurate conversion tracking makes every campaign high performing and profitable. But it will give you the best shot possible.

Here are few (of many) possible reasons why the accuracy can be low:

  • Using off-site payment gateways
  • Misconfigured cookie consent banners
  • Custom purchase confirmation pages that don't properly follow WooCommerce specifications

I am using a different Meta (Facebook) plugin and get the error "Receive the same event_id for many events". Does this also happen with this plugin?

When using Meta (Facebook) CAPI with other Meta (Facebook) plugins it can happen that you run into one of the following errors:

  • "Deduplication not set"
  • "Receive the same event_id for many events"
  • "Event Purchase not deduplicated”

This happens when the browser and server-side event IDs are not unique for each event.

Our plugin properly deals with this. It creates a unique event ID for each event which is why you should not run into that issue with our plugin.

Is it possible to use multiple Meta (Facebook) pixels with the plugin?

Short answer: No

Detailed answer: The common reason why you would want to install more than one Meta (Facebook) pixel is to be able to use more than one Meta (Facebook) ad account to drive traffic to the same WooCommerce shop. Meta (Facebook) allows you to share a pixel with other Meta (Facebook) ad accounts, which makes it unnecessary to install more than one pixel. In fact, sharing the pixel is the best practice. Therefore, the Pixel Manager for WooCommerce doesn't offer a way to add multiple Meta (Facebook) pixels.

How to enable and disable Beta releases?


This information is only valid for pro users of the plugin. If you plan to test bleeding edge beta releases go ahead and acquire the plugin from the pricing page

If you plan to test the newest beta releases you need to first unlock beta releases in your install. Open the plugin settings page > account tab. On the account tab check the box for beta releases. Done. From now on you'll be able to update your plugin to the newest beta releases through the regular WordPress update mechanism.

In some cases, it may take half an hour or so before a newly released beta version shows up in your plugin update list.

unlock beta