Learn business growth with Google Analytics 4 Forums Google Analytics 4 Identifying the origin of unexpected events in Google Analytics 4

  • Identifying the origin of unexpected events in Google Analytics 4

    Posted by Jacob on 7 June 2022 at 2:22 pm

    Man, over the last month I’ve seen about 50 new event types rocking and rolling! Oddly enough, I didn’t add these in GTM or as custom dimensions or audiences. Some of them are buck wild, recording hundreds of event occurrences every day. We’re talking curious monikers like “Create Report Viz”, “Resize pancake”, or “Add New Component”. Does any one have an idea of where to look to shut these cheeky party crashers down?

    Quinn replied 11 months, 2 weeks ago 3 Members · 2 Replies
  • 2 Replies
  • Gabriel

    Member
    16 June 2022 at 2:31 am

    It sounds like somewhere within your system, new event types are being introduced without your knowledge, which is causing confusion. This could be due to different applications or plugins installed on your website or system that are automatically sending these events. To find out where these events are coming from, you should locate your tracking code on your site, as this is likely where these events originate. By reviewing the place where the tracking code is implemented, you may be able to pinpoint the source of these unexpected events and adjust the code or settings to stop them happening in the future. You might also want to check with other people who may have access to make changes in order to uncover any recent activity that could explain these new events. If that doesn’t help, you might have to consult with a professional who understands code and systems integration.

  • Quinn

    Member
    21 October 2022 at 5:49 am

    It sounds like someone else might have access and is adding these events. Check who has permissions to your GTM and analytics. Once you’ve done that, you can simply remove or modify these events in your GTM – just look for triggers related to these events and remove or disable them.

Log in to reply.