Thanks for this, here are our questions:
-
We’re seeing some instances where the
checkout_completedevent isn’t dispatched for some clients. Do we have a list of scenarios when the event is not fired when compared to the old order confirmation script injection? -
For a recent store we reviewed, we were seeing 30% missing orders. When we audited the checkout further for the site (which was running 6 web pixels), we were seeing pixels take 3-7 seconds to fire, which seems to be enough time for someone to leave the page and the pixel to miss the event. We would love to understand what is best practise for web pixels given they are each on their own sandboxed iframe (This was tested on a 60Mbps connection on a desktop running windows 11 and through chrome). I.e. if we have a strategic method of prioritising a pixel, or ensuring it runs higher up in the priority list that would be great.
Thanks,
EDIT: I should mention our pixels are not conditioned to any consent preferences - they are set to fire always.