GA Issue: Bad Event Tracking Code

  • Resolved qph9697

    (@qph9697)


    4 years, 3 months ago

    Hi, I just received an issue in google analytics dashboard,

    Bad Event Tracking Code
    (not set) entry present in reports for property QuestionPapersHub.

    The Landing Pages report has a (not set) entry.

    A pageview hit must precede event hits in order for the event hits to include the page that they fire from. When event hits aren’t preceded by a pageview, Google Analytics doesn’t have the page for the event hits, so their page is (not set).

    Verify that tracking code for property QuestionPapersHub sends a pageview hit before sending any events.

    Google Tag Assistant Recordings can help you verify that your hits are sent in the correct order.

    This happened when I started using CAOS plugin, please help me with this.

    CAOS Settings:
    Snippet type: Async
    Position of tracking-code: Footer
    Enable Compatibility Mode: None
    Plugin Handling: Safe Mode
    Enable Stealth Mode Lite: “Check”
    Track Ad Blockers: “Check”
    Enable Enhanced Link Attribution?: “Check”

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Hi!

    Thanks for the thorough support ticket ??

    Since you’ve Snippet Type set to Async, there’s no need to set the position to Footer. Set it to Header instead.

    The notice you’re experiencing was due to a bug in the Track Ad Blockers feature. It is fixed in the latest version. So you can now safely click ‘ignore’ for this warning.

    If it returns, please let me know, but it shouldn’t, though.

    Thread Starter qph9697

    (@qph9697)

    Hi, Sorry for the late reply.

    But the issue isn’t resolved yet, I received the same error message again in my google analytics report.

    Receiving the same notice, started a few days ago.
    Also, https://irsproblemsgone.com/wp-json/caos/v1/proxy/collect is taking 1.66s to load. file is only 851b.

    Same problem for me with CAOS regularly updated till today. Solved only with Rollback to CAOS 3.6.0 (https://peppe8o.com)

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Thanks for letting me know, @peppe8o. I’ll see if I can detect any differences between 3.6.0 and the latest release.

    @thindpls, yes. Using the Stealth Mode API in the Free version is slower, because it is sent through WordPress. If you’d like to speed up Stealth Mode, you’d need to upgrade to Super Stealth.

    I have noticed that the “Bad Event Tracking Code error
    (not set)” happens only when “Track Ad Blockers” is checked.

    @daanvandenbergh
    If I go to Behavior > Site Content > Landing Pages I can see that the “not set” count is equal to the number of “tracking” events in behavior. So I suppose that when you send the “tracking” event to GA you could either assign the permalink of the current page (preferably if possible) or a fixed value so that it is just anything else other than empty.

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Awesome! Thanks for the insights, @drazon. I’ll investigate this further. Thanks a lot!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘GA Issue: Bad Event Tracking Code’ is closed to new replies.