Two Purchase events on order-received page with cd_est parameter

  • Resolved Konstatninos

    (@skredlemon)


    6 months, 4 weeks ago

    Hi,

    I have the free version of the plugin. I have tested both in the FB Events Manager > Test Events and with the Pixel Helper plugin, and when I place an order I get two Purchase events in both cases.

    Under the custom parameters for the first event I can see explicitly that the plugin is PYS.

    Under the custom parameters for the second event I can see only cd_est and currency. However under the Event Info details I can see that the Pixel Code lists a noscript tag which mentions towards the end that the plugin is PYS also.
    ( […] &cd%5Bplugin%5D=PixelYourSite&cd% […])

    Can you please verify PYS does actually fire two Purchase events?

    If that is the case, does the second one (the one with just the cd_est and currency) stand as a backup for some reason?

    I came to PYS from Facebook for Woocommerce, where I would fail to include the value of the purchase to the payload. As a result my conversions would not give an accurate number. When I had 3 orders with a total revenue of 250€ I would see a revenue of 5000€ in my reports from 3 orders with an average order amount of 33€.

    Of course the above details aren’t a concern in this question, since they are related to a different plugin, however I am puzzled with the cd_est parameter that I still see in my second event. This is the exact parameter that I would see in my events with the other plugin, until it was too late to react. I am trying to understand if this is normal behavior and my data reading will be fixed moving forward, or if this is something that needs further attention on my behalf.

    Kindly note that I have currently only PYS doing all the weight lifting with regards to the pixel and CAPI. I have removed Facebook for Woocommerce completely from my site, and I am confident I have cleaned all the leftovers the other plugin had left behind. Cleaned all the transients, scheduled tasks, and what not related to the old plugin.

    Thank you in advance.

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

    (@pixelyoursitesupport)

    6 months, 4 weeks ago

    Hello @skredlemon — based on your description, the second Purchase event may have been configured in the Event Setup Tool inside Facebook Events Manager.

    Please check there, go to All Events, and remove any events listed. After that, make sure the option “Track events automatically without code” is disabled on the same page.

    For reference: https://prnt.sc/_0KL0lT8fkXc

    One of these settings is likely firing the duplicate Purchase event, since our plugin does not send a backup Purchase event.

    Thread Starter Konstatninos

    (@skredlemon)

    6 months, 4 weeks ago

    Hi,

    Thank you for the insight. It was not what I was hoping to read, but that made me try things I would have otherwise skipped. The “what not” part that I posted yesterday included the cleaning up of the Events created with Facebook’s Events without code (I just did not mention it explicitly).

    Anyway, I have now managed to make sure no more than one Purchase events fire on my order-received page.

    What worked in my case – and I really hope this is the correct approach, because I don’t know what else to try at this point – was removing the noscript tags with the following two actions. After that and only then would I place an order and not get a second Purchase event. All other attempts have failed. 

    add_action( 'wp_head', function() {
        remove_action( 'wp_head', 'pys_fb_noscript', 10 );
    }, 999 );

    add_action( 'wp_footer', function() {
        remove_action( 'wp_footer', 'pys_fb_noscript', 10 );
    }, 999 );

    Please review and comment.

    Thank you,
    Konstantinos.

    Plugin Support pixelyoursitesupport

    (@pixelyoursitesupport)

    6 months, 4 weeks ago

    This looks like a site‑specific issue that I can’t reproduce on my test setups. That being said, could you please open a support ticket using this link and include a reference to our conversation here so we can investigate in detail?

    Thread Starter Konstatninos

    (@skredlemon)

    6 months, 3 weeks ago

    Hi,

    I have created a ticket using the link that you shared, as instructed.

    Thank you again,
    Konstantinos.

    Thread Starter Konstatninos

    (@skredlemon)

    6 months, 3 weeks ago

    I am leaving this note here for possible future discoverers of the post that the issue appears to have been resolved.

    As it turned out, although Facebook’s Codeless Events were configured to not fire, they had been created prior to installing and using PYS, and somehow they were finding their way into the source code. I explicitly deleted all duplicate events from Fb’s configuration, allowed some time, and re-tested. This time no duplicate events were present.

    The code I had pasted above was also disabled during all of the testing. It may have played its role while the issue remained, but it seems to be of no use as of this time.

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

The topic ‘Two Purchase events on order-received page with cd_est parameter’ is closed to new replies.