Purchase pixel firing on reload

Hi @mortenz,

Thanks so much for writing in to let us know about this! It’s actually something our developers have seen during their testing too, and they’re just putting the finishing touched on patching this bug for the next release.

While I don’t have an exact date for the release just yet, please know that the next version should get this resolved! If you’re still seeing the same issue once the update is available, could you please let me know?

Cheers!

Simon.

Hi Simon,

I can see from you last changelog that this problem should have been fixed now. However we are still experiencing the double firing of the purchase pixel on some orders.

You got any idea on how to fix this problem?

Screenshot from Facebook ads

View post on imgur.com

Kind regards
Morten

Hi Morten,

Thanks for reaching out. Indeed, the last version of the plugin (1.11.3) had a code fix to prevent duplicate purchase events when reloading the thank you page. Can you replicate this issue in the same way as before, that is, purchasing a product and reloading the thank you page?

The good news is that our developers are currently working on a brand new release with Facebook’s latest API. This gives us the possibility to switch over to server to server tracking which is super useful for tracking events such as this. We would no longer have to use the front end scripts to track a successful purchase, as we could listen for the payment_complete event from woocommerce which avoids this pain point!

I’m beginning to sound a bit like Groundhog Day I’m afraid, though I don’t have an exact release date to give you just yet, our developers are working hard to get the new release out as soon as possible!

If you’d like me to look into this further in the current version, then I surely can, in case there is anything I can suggest. As the new version is in the works, however, there aren’t going to be any new fixes for the current branch. It might make sense to wait for the new major release if at all possible.

Could you let me know how you’d like to proceed?

Cheers!

Simon.

Hi Simon,

I have investigated the case. It seems that it’s only users on IPhones paying with mobilepay, which is a payment gateway only available in Denmark.

The customer is taken over to a payment window and redirected back to completed order after payment. Could it be a problem when it redirectes?

Kind regards
Morten

Hey @mortenz,

Yes, most certainly that could affect the JavaScript tracking that the current plugin version uses. It will depend on the sequence of events and how the redirect occurs, though it seems like a high possibility.

The good news is, in the new version, we get to use Facebook’s Server to Server tracking instead. This will let us monitor for the payment_complete status change, rather than having to rely on the front end scripts which, as you’ve seen, can be a little unreliable.

The development has been complete and the testing process is underway, so hopefully we should see this fairly soon!

Would it be possible to give the new release a try when available and let me know if this issue still persists?

Cheers!

Simon.

You guys are doing an amazing job! I really appreciate what you have done for this integration. Keep up the good work.

Kind regards
Morten

Hey @mortenz,

Thanks so much for the kind words! We certainly will! ?? I look forward to hearing how the new major release works when you’ve had a chance to give it a try.

Cheers,

Simon.

Hi Simon. Is there any news about the new release?

Kind regards
Morten

Hey @mortenz,

It’s still going through testing I’m afraid! There were a few delays that caused testing to start later than expected. I still don’t have an exact release date yet but I am hopeful it will be fairly soon! The next step would be to see what the testing throws up and if there are any further changes required there.

If not, the release should come immediately after. Thanks for checking back in though.

Cheers,

Simon.