Fix rogue referral issue for GTM, GA and AdWords tracking #86
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Would really love to see this get merged in. |
|
For reference: This and #74 are both an attempt to address the same issue, but both are out of date with the base branch at this point. What's the best path forward with trying to get one of these PRs merged to help address this issue? |
|
any update about this pr? |
|
@jeffski Any chance you could update this PR so it's in sync with the base branch? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempt to fix this issue affecting GTM and Google Analytics CPC/AdWords tracking.
See issue details here: https://www.simoahava.com/gtm-tips/fix-rogue-referral-problem-single-page-sites/
See also fix from https://github.com/fengsi-io/gtm-module/pull/1