Worked Initially, Then Stopped — Support is okay

  • Peter

    (@secures)


    3 months, 3 weeks ago

    I’m updating my previous review to reflect the final outcome.

    The issue we experienced was partly related to configuration on our side, combined with a bug in the base plugin that has now been fixed. After resolving this together, the plugin is working properly again.

    While response times initially felt slower than expected, support was actively working on diagnosing and resolving the issue. Communication continued within the support ticket, and the underlying problem has since been addressed.

    Now that everything is functioning as intended, we’re happy with the solution and updating this to a 5-star review.

    • This topic was modified 3 months, 3 weeks ago by Peter.
    • This topic was modified 3 months, 3 weeks ago by Peter.
Viewing 1 replies (of 1 total)
  • Plugin Author Rocket Beetle

    (@rocketbeetlecom)

    3 months, 3 weeks ago

    Hi Peter,

    I’m sorry about the rough experience with the recent update – there was a bug in the base plugin that caused issues, and I understand that was frustrating.

    I do want to clarify a couple of things. We’ve been going back and forth on your support ticket over the last few days, so it’s not quite accurate that there’s been no response. We’ve been actively working through the issues together.

    On the technical side – Beetle Tracking with Cloudflare Zaraz doesn’t use a dataLayer. Everything is sent directly to Zaraz server-side, which is actually the whole point of server-side tracking. If you’re seeing data in Zaraz, the plugin is working as intended. If you’re expecting a dataLayer, that suggests there might be a mix of tools involved that we should sort out.

    I’d love to get this fully working for you – let’s continue in the support ticket and figure out what’s going on with your Google Ads setup.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this review.