-
Notifications
You must be signed in to change notification settings - Fork 53
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
Google Analytics ID is exposed #39
Comments
This sounds super interesting. I think it being a thing of the front end, is always exposed? I'm exploring too :D |
Actually I discovered another problem with this approach. We will only be able to detect the user entering URL not the other URL's when he is roaming around like its a SPA and the page doesn't reload. This is an issue with all the SPA and the fix for this is to use a route update method to send data on route change. This might work - https://medium.com/madhash/how-to-properly-add-google-analytics-tracking-to-your-angular-web-app-bc7750713c9e |
give me this |
All yours @amanintech |
Google Analytics ID is currently exposed in public view source code action. This was someone who can hinder the analytics and we may get wrong data.
Possible fix use component-based analytics also to target data while users move around.
The text was updated successfully, but these errors were encountered: