For awareness, we have just been investigating an incredibly intermittent issue with sending Zaraz t
For awareness, we have just been investigating an incredibly intermittent issue with sending Zaraz track events from the client browser using zaraz.ecommerce() on one of our sites.
We identified that the issues was caused by CF Rocket Loader being enabled on the domain (This was the only site it was enabled for and the only site experiencing these issues.)
Once we disabled the Rocket Loader service the issues went away.
We have reviewed the docs and it does mention they dont work well together here:
Can I use Zaraz with Rocket Loader? We recommend disabling Rocket Loader when using Zaraz. While Zaraz can be used together with Rocket Loader, there’s usually no need to use both. Rocket Loader can sometimes delay data from reaching Zaraz, causing issues.but I would say that this isnt exactly what we encountered, we saw complete failures to call zaraz.ecommerce within the body section of the page, presumably because Rocket Loader had delayed the loading of Zaraz enough that this call happened ahead of the zaraz JS loading. Its also not obvious that these 2 services could interfere with each other, other than a small note in the FAQ section of Zaraz. It would be good if the Zaraz config section in Cloudflare would include an error/information message saying something like "You have Rocket Loader enabled, this service does not work well with Zaraz, we advise disabling it or you may face tracking issues". The other issue obviously with disabling Rocket Loader is that this prevents Rocket Loader from being used on non Zaraz loaded libraries which is a little frustrating and a somewhat undisclosed negative of using Zaraz in Cloudflare.
0 Replies