added query parameters and hash fragments to reported url #4
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
currently only the path without any query parameters or hash fragments is reported. this leads to problems when integrating for example adwords with analytics. the missing gclid parameter which adwords attaches but which is not reported to analytics (through gtm) causes analytics to not associate the sessions with the adwords click.
I imagine there are plenty similar issues.
btw. the
this.route.path(this.params, this.params)is kind of a hack, because I did not know a better way to extract path, query and hash parameters in a more elegant way. I am open for suggestions.