React-ga: Multiple react GA instances with react SSR after opening new tab

[horaceleung]

Not sure if this has been flagged up before but we noticed that when a new tab is opened, within that tab it causes a new GA tag to created inside whenever user navigates to a new page or click on an action.

I believe the normal behaviour is that there should only be one instance of GA? This causes some inaccurate data within google analytics dashboard but I am not sure if this is an issue with our implementation, or with react-ga.

Appreciate if anyone has experienced this before can shed some light.

[Drapegnik]

I fixed it with:

if (!window.ga) {
    ReactGA.initialize(...)
}

[justrealmilk]

I literally came here for this reason. Turns out I'm an idiot and was calling it on render(). Thanks for your fix @Drapegnik

[amangeot]

@Drapegnik, what does it fix exactly? What kind of issue can you get from not setting up react-ga the way you do?

[Drapegnik]

@amangeot I prevent multiple ReactGA instances on the page by calling ReactGA.initialize only once

[amangeot]

Thank you for your quick reply @Drapegnik

I currently have a tracking issue. I have a widget hosted in iframes on other websites showing content from example.com/embed. When initializing my react app from these /embed urls, a specific tracking ID is used. The problem is that my main website tracks both website and widget sessions, even though it's initialized with a different tracking ID. The widget tracking ID accurately tracks only those widget sessions.

Do you know what could messup the tracking?

I was wondering if it could have anything to do with GA initialization settings as you mentioned

[amangeot]

Oh my issue came from somewhere else!

In case somebody reads this, my issue was that Google Tag Manager was loaded in our HTML template, and GTM was responsible for loading our main tracking ID for widget sessions, therefore widget sessions being tracked by both IDs.