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

Upgrade to gtag.js #8

Open
ZiggyMo opened this issue Oct 24, 2017 · 2 comments
Open

Upgrade to gtag.js #8

ZiggyMo opened this issue Oct 24, 2017 · 2 comments

Comments

@ZiggyMo
Copy link

ZiggyMo commented Oct 24, 2017

The new recommended way to track is to use gtag.js rather than analytics.js. For more details see:
https://support.google.com/analytics/answer/7538414#analyticsjs

@zhhz
Copy link
Owner

zhhz commented Oct 24, 2017

Hi ZiggyMo,

Thanks for the information. I haven't checked out gtag.js myself yet, not totally sure the requirements or pre-configuration/settings with google. So my concern here is how to not break the already existing gulp-ga users. Maybe we should add an option for switching between analyics and gtag...

Any PR will be more than welcome.

Thanks.

--Z

@xied75
Copy link

xied75 commented May 18, 2018

Would second this. There is no reason to worry about the breaking change, if it breaks, it might be the time for the end-user to move on, eventually they need to move with what Google supports.

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

3 participants