• Hi Analytify Support,

    We’re using Analytify Pro 9.1.1 with GA4 in gtag tracking mode

    While troubleshooting a separate tracking issue, we noticed that all GA4 g/collect requests include ep.debug_mode=true.

    However:

    • The Analytify diagnostics page reports “Debug Mode: No”.
    • We can’t find any setting in Analytify to enable or disable GA4 debug mode.
    • The issue occurs on our production site.

    Could you please clarify:

    1. Is it expected that frontend GA4 events are sent with debug_mode=true?
    2. Is there a setting to disable this for production sites?
    3. If not, what is the recommended way to disable GA4 debug mode while continuing to use Analytify for tracking?

    Thank you.

    • This topic was modified 4 days, 7 hours ago by Syazman.
Viewing 1 replies (of 1 total)
  • Plugin Support ruqyya

    (@ruqaiyya)

    Hey, @dinsyazman!

    Thank you for reaching out and for laying out the details so clearly, it really helped us track this down quickly.

    Good news: this is already fixed on our end. The next release will have debug mode off by default, so your site’s data will be tracked normally without any extra steps from you.

    If you’d like early access before the official release, feel free to reach out to us on our support forum and we’ll be happy to get you a beta version to try right away.

    To answer your questions directly:

    1. No, it was a leftover setting from testing. It’s fixed now.
    2. With the update, it’s disabled by default. For anyone who needs DebugView for testing, it can be enabled temporarily by adding this to you theme’s function’s.php: add_filter( 'analytify_debug_mode', '__return_true' );
    3. Just update to the latest version once released (or grab the beta version for early acess) and your tracking will work normally right away. Your GA4 data collection was not affected, events were still being recorded as usual.

      Please don’t hesitate to reach out if you need any more clarification!
Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.