Support » Plugin: Google Tag Manager for WordPress » (not set) Event Action and Event Label

  • Resolved roboliz



    I’ve been using gtm4wp for a while now and most recently received this error in Google Analytics yesterday.

    Here’s the message:

    Bad Event Tracking Code

    First detected: Nov 12, 2019 5:04:31 PM
    Last detected: Nov 13, 2019 6:40:30 PM

    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 Website sends a pageview hit before sending any events.

    How can I fix this notification? I haven’t changed any of my GTM settings, so I’m not sure what the problem could be. I updated the gtm4wp plugin today.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Thomas Geiger



    Though this is not a GTM4WP plugin related question, let me try to answer your question.

    If you test your landing page on your own and see that the order of GA hits is correct that does not mean that it is correct for other users. There might be users on your site with slower internet connection where the order of GA hits could be wrong.

    What you could do is to open your GA pageview tag in your GTM container and set it to fire “Once per page” in the advanced settings. Then open your GA event tag and use the tag sequencing option to set your GA pageview tag to fire before your event tag. This way, either the GA event tag will first fire your GA pageview tag or it will be fired in the normal way during pageload, whichever comes first.



    Not really sure how this was resolved, but I think it was due to adding an “article loaded” event to GTM. I’ll keep an eye on this issue and follow up if this happens again.

    • This reply was modified 2 months ago by roboliz.
Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.