Double page tracking via gatsby-ssr.js and gatsby-browser .js about gatsby-plugin-segment-js HOT 5 CLOSED

We're seeing this too. I'm just not using trackPage configuration option and instead I'm using this in gatsby-browser.js:

exports.onRouteUpdate = () => {
  //Fire off the Segment tracking call
  window.analytics && window.analytics.page();
};

This way it doesn't fire the extra analytics.page calls from gatsby-ssr.js, and we just fire them manually.

from gatsby-plugin-segment-js.

Sounds like this is real. I'll have a look. Is it just straightforward to repro?

from gatsby-plugin-segment-js.

This is hitting me as well. I can reproduce it quite easily, but I don't have it in a public project. If it would be useful, I could put together a public repo that illustrates it. I think it's just a matter of adding the plugin with trackPage = true, though.

from gatsby-plugin-segment-js.

Would a good fix be to set a flag in the config as to whether you are actually making use of server side rendering, and to not fire the call in gatsby-ssr.js if not?

I think a lot of people using Styled Components (myself included) have a gatsby-ssr.js despite not using server side rendering intentionally for some reason that I only vaguely remember— but builds fail if i remove it.

from gatsby-plugin-segment-js.

This is fixed in 4.0.0, and there is now a includeTitleInPageCall option where you can choose if you want to send the page title with the call. That's the only thing close to a "breaking change" in 4.0, despite it being a "major" version bump.

from gatsby-plugin-segment-js.