Learn business growth with Google Analytics 4 Forums Google Analytics 4 Resolving Duplicate Events in Google Analytics 4 with GTM Setup

  • Resolving Duplicate Events in Google Analytics 4 with GTM Setup

    Posted by Ava on 9 October 2022 at 1:10 pm

    “Hey guys, I’m working on setting up GA4 tracking for a new website using GTM. But I’m facing some issues. Double events are being logged in GA4. For instance, I’ve noticed a purchase event that’s logged twice as you can see in these links. I am also noting double counts for add_to_cart and view_cart events. I believe there’s a common source triggering these duplicates. Any advice or suggestions on sorting this out would be super helpful!”

    Lily replied 10 months, 4 weeks ago 3 Members · 2 Replies
  • 2 Replies
  • Alexander

    Member
    24 March 2023 at 10:42 pm

    You might have added event code on your site and in GTM causing duplicates. Go through your GTM settings and website code to find and remove the duplicate. You could also trace your events using GA’s debug mode or browser extensions like Tag Assistant. Keep digging, you’ll find it!

  • Lily

    Member
    10 June 2023 at 3:04 pm

    It sounds like you’re experiencing a common issue where events are being logged twice in Google Analytics 4 (GA4) through Google Tag Manager (GTM). This could be due to a number of reasons. Firstly, check if the same tracking code has been inserted twice. This can occur if the code has been manually put into the website and also implemented via GTM. Another reason could be that you have the same tags firing twice in GTM, so you should check your tag firing order and rules. Also, check any third-party plugins you’re using, as these can interfere with GA4. It could potentially be that an event listener is triggering GA4 events twice. In any case, the way you can investigate this is by using Tag Assistant by Google, using DebugView in GA4, and investigating the website’s source code. Remember to ensure only one implementation method (either hardcoding or GTM) is being used to avoid duplication of events.

Log in to reply.