Version 3.5.5 No Purchase Event fire from Facebook Pixel Browser

[gsimeonov2012]

🔎 Isolate the bug

Install 3.5.5 complete a purchase and check with Facebook helper that purchase event is not triggered. At the moment purchase events are only reported from the API

• I have confirmed this occurs in the most recent version of WordPress, WooCommerce, and Facebook for WooCommerce.
• I have confirmed this occurs when only WooCommerce and Facebook for WooCommerce are active and when using a default WordPress or WooCommerce theme.

✍️ Describe the bug

Install 3.5.5 complete a purchase and check with Facebook helper that purchase event is not triggered. At the moment purchase events are only reported from the AP

🚶‍♀️ Steps to reproduce

Install 3.5.5 complete a purchase and check with Facebook helper that purchase event is not triggered. At the moment purchase events are only reported from the AP

✔️ Expected behavior

Orders should trigger Purchase events from Pixel Browser

This bug is continus from older version, I`m just reporting that the latest fix from #3512 implemented in 3.5.5 did not fix this issue and it is still ongoing.

Orders do not trigger purchase events from the Facebook Pixel Browser , only from API

[gsimeonov2012]

Can this be fast forwarded and fixed as soon as possible as it is a know issue for months

"in facebook-commerce-events-tracker.php a check exists:

// use a session flag to ensure this Purchase event is not tracked multiple times
$purchase_tracked_flag = 'wc' . facebook_for_woocommerce()->get_id() . 'purchase_tracked' . $order_id;

// Return if this Purchase event has already been tracked.
if ( 'yes' === get_transient( $purchase_tracked_flag ) || $order->meta_exists( '_meta_purchase_tracked' ) ) {
return;
}

basically when the order is created it will add the meta and prevent the code being executed"

Credit to: Stefan Vasiljevic (@stefanue) pinpointing the issue in the thread - https://wordpress.org/support/topic/events-not-tracking-after-update/

[hardik18882]

Yes same issue since last version and continues on this update as well. We were hoping that this new update will fix the Browser pixel issue for purchase events but it doesnt.

Can this be fast forwarded to fix as soon as possible please?

[WouterBossen]

Yes, i've been in contact with Meta too and pointed out to them the issue in their code. Trying use a single function to both trigger the pixel and the CAPI, which will then prevent the pixel from firing. They just refuse to fix it.

[gsimeonov2012]

They finally fixed it I believe - https://github.com/facebook/facebook-for-woocommerce/actions/runs/16670703857

But we will have to wait for the next release

[hardik18882]

Please Can this fixed be pushed quickly for next release?

[hardik18882]

No Updates yet? This is serious issue and not sure why you guys are not fixing it.

[gsimeonov2012]

3.5.6 update came, but sadly the issue persist

[vncnt-mb]

+1 on this issue's importance.

Just to confirm, patching our plugin with the inject_purchase_event() function from the feature/separate-purchase-event-tracking branch is a successful workaround for us.

Hoping for a merge soon.

[hardik18882]

I don't understand WHY they don't take this issue seriously. Browser Pixel events are important for Campaign optimization and if this is Not solved then it's no use.

[iodic]

Hey everyone, the team is working on this update and the branch from which @vncnt-mb got the update is one of the solutions being tested. We will follow up as soon as there is an update.

@vncnt-mb, can you email your Pixel ID to woosupport@meta.com? We would like to review the events before and after the change. Can you also provide information whether the number of events matches the number of orders in the store?

Thanks!

[hardik18882]

Hello @iodic

Is this issue planned to get solved in next update? Can you please provide any estimated time?

As currently there are NO Browser events been fired for Purchase event in last update version 3.5.7 as well.

Thanks,

[hardik18882]

Hello @vncnt-mb

Have you got any updates from Meta about your submissions to them?

Hello @iodic

Can you please provide update about when this issue will be solved?