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.

Sign up for GitHub

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

Jump to bottom

Update from ga.js to analytics.js #19

Closed
iteles opened this issue Jun 24, 2015 · 13 comments
Closed

Update from ga.js to analytics.js #19

iteles opened this issue Jun 24, 2015 · 13 comments
Assignees
@iteles
Labels
enhancement New feature or enhancement of existing functionality

Comments

@iteles
Copy link
Member

iteles commented Jun 24, 2015

When the site moves out of alpha! https://developers.google.com/analytics/devguides/collection/gajs/
@iteles iteles self-assigned this Jun 24, 2015
@iteles iteles mentioned this issue Oct 18, 2015
Open
@iteles
Copy link
Member Author

iteles commented Oct 21, 2015

Currently investigation whether to just use analytics.js or go for the Google Tag Manager container

To update: https://developers.google.com/analytics/devguides/collection/upgrade/reference/gajs-analyticsjs

@nelsonic
Copy link
Member

So glad you #_finally_ learning this... Brings back many memories of #2010 😜

@nelsonic nelsonic added the enhancement New feature or enhancement of existing functionality label Oct 21, 2015
@iteles
Copy link
Member Author

iteles commented Oct 21, 2015

Nice.

@iteles iteles changed the title Add async Goggle Analytics call Update from ga.js to analytics.js Oct 21, 2015
@iteles
Copy link
Member Author

iteles commented Oct 21, 2015

Decided against going full-blown Google Tag Manager for now (don't see the need) and ensured script is analytics.js (which uses Google Universal Analytics as opposed to ga.js which does not) and loading asynchronously for modern browsers (actually understanding how it works).

@nelsonic
Copy link
Member

You made the right decision... 😉
Cannot stand Google Tag Manager. Its one of those "necessary evils" that developers put up with, but is slow and clunky.

@iteles
Copy link
Member Author

iteles commented Oct 21, 2015

You could have been this helpful an hour ago 😆

@nelsonic
Copy link
Member

You didn't ask me...

@iteles
Copy link
Member Author

iteles commented Oct 21, 2015

If I'm investigating something you already know the answer to... I'll make sure it's a direct question next time!

@nelsonic
Copy link
Member

Direct questions are betterer.
I'm used to people at FAC ignoring anything I've written/said so I just keep quiet...

@nelsonic
Copy link
Member

If you ask me what I would recommend you focus on... the answer is: https://mixpanel.com

@iteles
Copy link
Member Author

iteles commented Oct 21, 2015

Ooooooooh...!

@iteles iteles mentioned this issue Oct 21, 2015
Closed
@nelsonic
Copy link
Member

If you read what I write you would know we are using _Kibana_ for our app because we are already storing our data in ElasticSearch which means it is not being sent to a third party where we have zero control over it.
The plan is to build a simplified application-specific usage tracker that will give the person _using_ the app the insights into their own usage, not ship them off to some "data warehouse" in a different country...
Setting up analytics properly on MixPanel takes just as much work as writing our own event handler and pushing the data into ES. if you ask me I will tell you exactly what to do.

@iteles
Copy link
Member Author

iteles commented Oct 22, 2015

👍 #transferableconcepts

@iteles iteles closed this as completed in d2ea552 Oct 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iteles iteles

Labels
enhancement New feature or enhancement of existing functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nelsonic @iteles