• Resolved anthonyz747

    (@anthonyz747)


    I’ve been seeing inflated revenue and purchases inside FB Analytics since installing this plugin (free version). I looked through the event debugging in FB and found that the plugin is sending duplicate purchase events. It seems once for the actual event and again if the order-received page is reloaded by the customer. The Event Debugger only shows the 12 most recent events, but even so I found two duplicates:

    07/02/18 23:01:44
    Android
    Unknown
    Purchases
    30
    Current URL: lactiful.com/checkout/order-received/6537

    07/03/18 01:16:41
    Android
    Unknown
    Purchases
    30
    Current URL: lactiful.com/checkout/order-received/6537

    —————
    07/02/18 19:14:10
    iOS
    Unknown
    Purchases
    97
    Current URL: lactiful.com/checkout/order-received/6536

    07/03/18 10:06:27
    iOS
    Unknown
    Purchases
    97
    Current URL: lactiful.com/checkout/order-received/6536

    The duplicates are easy to spot since they have the same “Current URL” and same purchase information. This is a huge problem that results in unreliable data across both analytics and FB ads. Is there any way the plugin can be set to NOT send in duplicate transactions? Seems like a pretty big flaw. No?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author PixelYourSite

    (@pixelyoursite)

    Hi,

    This is not a common problem, so I suspect it has something to do with your configuration.

    I suggest you check the following:

    1. Do you have any Purchase events configured on our Events tab? If yes, delete them. The plugin fires the event by default when a WooCommerce order is completed.

    2. Do you have any other way of installing the pixel, like custom code, another plugin, theme settings?

    3. Do a test transaction and check the events with Pixel Helper Chrome extension. Do you see 2 events fired when a purchase is completed? If yes, do they have the same set of parameters?

    I’ve checked the URLs from your message and I can’t see any Purchase event fired on them.

    There is also something strange abut those URLs. The ones where our event is fired look a bit different, something like: order-received/2048?key=wc_order_5b3bf6b32f920

    If the configuration is fine and there’s a simple case of users reloading the confirmation page, the impact of the problem should be minor. Most users have no reason to save that exact URL and visit it again.
    However, our pro version has an option to fire the event just once, after the transaction is completed, and not on a simple page visit.

    #1: No events at all configured on Events tab.
    #2: I have a plugin that inserts code – I use it to track Bing conversions, not FB however.
    #3: Test transaction shows 1 purchase event in the chrome helper extension.
    Not ALL of the transactions are duplicated. Only some… looks like approximately 20% by the difference in FB’s numbers and actual.

    That is odd about the URLS, maybe the Event Debugger strips out the key-value pair?

    The duplication rate is close to 20%, not minor by any means. Any other suggestions or does the free version, just not work, in this case. I’m a bit leery of paying for an upgrade when the free version doesn’t do what it claims to (at least for me). Why doesn’t the free version have the option to fire the event just once, after the traction is completed? Seems like core functionality to me.

    Plugin Author PixelYourSite

    (@pixelyoursite)

    Can you please check if the duplicate events have similar parameters to the correct ones?

    Is there a time difference between the duplicate events, or they are fired in the same moment?

    Indeed it looks like the key value is removed, so the URL can be the correct one, after all.

    Thanks for the reply! Parameters seem identical between original and duplicate other than the timestamp. You can see the timestamps in my original post. There’s about a 2hr 15min gap between the first original/duplicate (on Android) posted above.

    The gap between the second original/duplicate (on iOS) is about 15 hrs.

    Plugin Author PixelYourSite

    (@pixelyoursite)

    Is there any reason for the users to return on that page, like a license code, or anything else? In my experience there is never an “organic” order-received page that can have such a large impact.

    No reason. It’s just the default WC thank you / order received page. I noticed that both of the duplicates shown above are from mobile devices. Is it possible after placing the order, these people are exiting to the home screen or shutting off the device without first closing the browser tab? Then next time they unlock the phone or go into browser, it might reload the page and send the purchased event again?

    That is my guess. To be fair, my site does get more mobile orders than typical. And if this is “normal” behavior for people on mobile, that’s why I request the option to fire the purchase event just once, after the traction is completed. It would clean up the data and I don’t think it would harm premium upgrades, since there’s so much more that the premium plugin offers.

    Plugin Author PixelYourSite

    (@pixelyoursite)

    Well, I really appreciate your advice and definitely consider it.

    For now that option is part of our pro version only. If you’re interested in an upgrade send me a message on our site and I’ll send you a discount code.

    Thanks for the suggestions and the generous offer! I don’t need and likely wouldn’t use the other pro features – we’re a single product store – I’m just looking for a reliable way of getting good purchase data back to FB to measure our ad success there. Still, I’ll consider the offer.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Duplicate Purchase Events’ is closed to new replies.