Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GTM Rogue Referral issue #114

Open
mraichelson opened this issue Mar 29, 2021 · 1 comment
Open

GTM Rogue Referral issue #114

mraichelson opened this issue Mar 29, 2021 · 1 comment

Comments

@mraichelson
Copy link

mraichelson commented Mar 29, 2021

There's an issue that crops up in SPAs that's dubbed the Rogue Referral issue, you can read about it in depth over here...

Right now there are two open PRs to try to address this but they've been abandoned and are no longer in-sync with the current release of gtm-module.

There's also issue #68 (August 31, 2020) which was around this as well but was closed without an actual resolution.

What is the best way to get this moving forward again?

I was starting to put together a new PR against the current base branch, but the two existing PRs worked in different files and I wasn't clear on what the actual best practice was (if any), or what the difference between the two approaches was (if any).

(This situation a blocker to me being able to use Nuxt for any work at ye olde day-job since it means paid traffic can't be accurately tracked for performance purposes.)

@mraichelson
Copy link
Author

Looks like this also snakes back to September 2019 in this issue that was filed over on nuxt/nuxt.js originally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant