Google Analytics ID is exposed

[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.

[arpansac]

This sounds super interesting. I think it being a thing of the front end, is always exposed?
Any library you suggest would make component based analytics possible? Or should we just go about the guide given on developers google?

I'm exploring too :D

[amanintech]

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.
I have done a similar thing in React in past but don't know much about Angular approach

This might work - https://medium.com/madhash/how-to-properly-add-google-analytics-tracking-to-your-angular-web-app-bc7750713c9e

[amanintech]

give me this

[arpansac]

All yours @amanintech