PMW pixels not fired (conversion pixels)

  • Resolved Herbert van-Vliet

    (@remarkno)


    1 year, 6 months ago

    Version: 1.45.0; tier: free; distro: fms
    WP 6.6.2, Woo 9.3.3, PHP 8.2.24

    Payment gateways:
    kco, Klarna Checkout, KCO_Gateway
    vipps, Vipps MobilePay, WC_Gateway_Vipps

    https://…/checkout/order-received/
    Theme: Kava

    Purchase confirmation page reached per gateway (active and inactive):
    37 of 43 = 86% for kco
    12 of 14 = 86% for vipps

    A few questions.
    I couldn’t find documentation on how this is implemented. Are conversion pixels talking directly to Google, Bing, FB etc, or is this a conversion pixel that talks to the website where the plugin is deployed?

    I am thinking that the 14% of the orders where the conversion pixel isn’t fired could be caused by an AdBlock plugin, Brave shields, or because the visitor did not want the cookies.
    Is that likely?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Leeberty

    (@aaronvincentlee)

    1 year, 6 months ago

    Hi @remarkno,

    I understand that you’re experiencing some issues. Let’s get this sorted out.

    “Are conversion pixels talking directly to Google, Bing, FB etc, or is this a conversion pixel that talks to the website where the plugin is deployed?”

    Conversion pixels primarily communicate with the advertising platforms (like Google, Bing, Facebook, etc.) to track user interactions and conversions related to ads. When a conversion pixel is installed on a website, it collects data about specific actions taken by users (such as purchases or signups) and sends that data back to the respective advertising platform for tracking and analytics purposes.

    In the context of a plugin like Pixel Manager for WooCommerce, the conversion pixel would be set up to send data to these platforms while also providing insights and tracking capabilities directly on the website where the plugin is deployed.

    This means that the pixel operates both as a tracking tool for the website owner and as a communication tool with the advertising platforms.

    “I am thinking that the 14% of the orders where the conversion pixel isn’t fired could be caused by an AdBlock plugin, Brave shields, or because the visitor did not want the cookies.”

    It’s possible, however, after checking your Purchase confirmation page reached per gateway alaysis, it is most likely because of your offsite payment gateway.

    It means that not all your customers are getting redirected to the purchase confirmation page. The conversion tracking happens on the purchase confirmation page.

    With this, please read the following support articles. They explain what’s causing this and what your options are going forward.

    I hope this helps. Feel free to reach out if you have further questions.

    Thread Starter Herbert van-Vliet

    (@remarkno)

    1 year, 6 months ago

    Ok, thanks, that clarifies things.

    So I understand that the pixels are loaded from remote domains and they are reporting back to those sites directly. Let’s for example use Facebook.
    That means that if Facebook is blocked (through e.g. AdBlock, Brave Shields, or when the site applies the visitor’s cookie consent properly), the pixel would not be loaded and no information can be sent to Facebook.

    I’m not sure what the word “primarily” in your response means, but your plugin must send its own code to the website in order for data to be sent directly back to the website. The Facebook pixel is not going to do that for you.
    Right?

    Assuming your plugin does send its own code on the thank-you page, the WooCommerce view “PMW pixels not fired” will contain those orders where the user never went back to the “thank-you” page: this can be decided because the plugin code reports directly to the website (and cannot be blocked by AdBlock, Brave Shields and so). No cookies required for that either: all is good.
    Unless of course the end user doesn’t bother going back to the thank you page because of the off-site payment settings or UX.
    That’s why you can say to fix it “if it gets below 90%” (ref. https://sweetcode.com/blog/are-all-payment-gateways-created-equal#what-can-you-do-to-fix-the-tracking-accuracy).

    Does this describe what’s going on?

    Plugin Author alekv

    (@alekv)

    1 year, 6 months ago

    Yes. The PMW runs its own code on the thankyou page. And most, if not all, blockers don’t block it. But, blocker can block the tracking pixels that the PMW runs in its code.

    So essentially the tracking accuracy is for the most part a measurement if the buyers reached the purchase confirmation page or not.

    If 100% reach the purchase confirmation page, then at least the PMW can run the tracking pixels, which still can be blocked by Consent Management Platforms, ad blockers etc.

    For the first part we can do something about it. Make sure that all buyers reach the purchase confirmation page. And that’s what this is all about.

    Does this describe what’s going on?

    So I would say yes. That’s what’s going on.

    Thread Starter Herbert van-Vliet

    (@remarkno)

    1 year, 6 months ago

    Thanks.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘PMW pixels not fired (conversion pixels)’ is closed to new replies.