Issue with Purchase Event Not Triggering in Facebook for WooCommerce v3.5.9

  • JecJac

    (@jecjac)


    1 week, 2 days ago

    I am using Facebook for WooCommerce Plugin version 3.5.9 and experiencing an issue related to the Purchase event. In the plugin code, there is the following check:

    if ( 'yes' === get_transient( $purchase_tracked_flag ) || $order->meta_exists( '_meta_purchase_tracked' ) ) {
     return;
    }

    This is intended to prevent duplicate Purchase events from being triggered. However, I have confirmed that there is no pre-existing meta or transient data for the order, yet the Purchase event does not fire.

    If I comment out this condition, the Purchase event triggers as expected.

    It seems the issue may be related to the timing of the duplicate protection logic—the transient or meta flag might be getting evaluated or set too early, preventing the Purchase event from firing even on a valid order.

    Could you please review this behavior and advise how to ensure Purchase events fire correctly while still preventing duplicates?

    Thank you for your assistance.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Marija

    (@marijastuntcoders)

    1 week, 2 days ago

    Hi @jecjac – thanks for reaching out!

    We are looking into this issue and will let you know as soon as we have an update.

    Kind regards,
    Marija

    Plugin Support Marija

    (@marijastuntcoders)

    1 week, 1 day ago

    Hi @jecjac – can you follow these steps to verify if the Purchase event is firing correctly:

    1. If you don’t have it already, install the Meta Pixel Helper Chrome extension.
    2. Navigate to Marketing → Facebook → Troubleshoot and enable Debug Mode.
    3. Place a test order and monitor events using the Meta Pixel Helper; ie. – check if the Purchase event is triggered right after clicking the ‘Place order’ button or on the Thank You page.
    4. Go to WooCommerce → Status → Logs and open the facebook-for-woocommerce.log file & confirm whether the Purchase event is being fired on the woocommerce_new_order hook.

    Note: The Purchase event may sometimes be sent only as a server event, so it can take a bit of time for it to appear in Events Manager.

    Kind regards,
    Marija

    Thread Starter JecJac

    (@jecjac)

    1 week ago

    After extensive testing and verification, I can confirm the following:

    1. Only server-side Purchase events are being sent — browser-side events are not firing at all.


    2. The following browser-side pixel events are completely missing:

    PageView

    AddToCart

    InitiateCheckout

    Purchase



    3. I have tested using every method you mentioned: Debug Mode, Meta Pixel Helper, and the facebook-for-woocommerce.log.
    Even after multiple test orders, no browser-side requests are triggered — not immediately, not after 10 hours, not ever.


    4. When I comment out the duplicate-protection block, the server-side Purchase event fires correctly — but still no browser-side event is sent.
    This clearly indicates the problem exists in the client-side layer (JavaScript/pixel injection/frontend hook timing).



    Because of this bug, my sales have dropped significantly, and I am directly attributing financial loss to this issue. I have full documented evidence (screenshots, browser network logs, plugin logs, test order IDs, etc.) and will use it if necessary.

    Here is what I expect immediately:

    ✅ Within today (no delay):

    Release an urgent hotfix/patch that restores all browser-side events (PageView, AddToCart, InitiateCheckout, Purchase).

    Do not wait for a major version — this must be addressed as a critical update.

    Provide confirmation (changelog/commit link) so I can verify the fix.

    Share what your team finds — which file/hook/timing is blocking client-side events and how it was resolved.

    Inform me about your policy regarding compensation, because this faulty update has caused measurable business damage. If you fail to address this quickly, I will be forced to proceed with legal action.


    It is extremely irresponsible to publicly release versions without proper testing, especially when core tracking features are broken. This is unacceptable.

    If no solution or action plan is provided within 24 hours, I will immediately:

    File an official complaint with documented proof

    Begin legal steps to claim compensation for the loss caused by this defective update


    I am ready to provide logs, screenshots, and order IDs — just tell me where to upload them. But do not waste more time asking basic questions. The issue is clearly reproducible: no browser-side data ever fires — not even after many hours.

    Fix this immediately and update me today.
    I expect a proper resolution — not more delays.

    Regards,
    JecJac / Md. Rifat Rana

    Thread Starter JecJac

    (@jecjac)

    6 days, 20 hours ago

    Checked Screenshot….

    https://prnt.sc/B7-tJCgjV7h4

    Thread Starter JecJac

    (@jecjac)

    6 days, 20 hours ago

    Check another screenshot.

    https://prnt.sc/qcAiyaWE70Pg

    @marijastuntcoders

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

You must be logged in to reply to this topic.