Skip to content
This repository has been archived by the owner on Aug 10, 2020. It is now read-only.

GA Event category should not be hardcoded to "Event" #80

Open
hraynaud opened this issue Apr 17, 2014 · 1 comment
Open

GA Event category should not be hardcoded to "Event" #80

hraynaud opened this issue Apr 17, 2014 · 1 comment

Comments

@hraynaud
Copy link

HI first thanks for this great gem. I noticed that the google_universal support is only available on the master branch and not in any of the release branches. Is there an ETA when it will be officially released. Also, the event tracking api as implemented doesn't fully match google's spec.
https://developers.google.com/analytics/devguides/collection/analyticsjs/events

The current implementation hard codes the category as "Event", and doesn't support the last number parameter. I'm happy to provide a pull request with the desired enhancements but just wanted to check to make sure I didn't miss anything.

@sfsekaran
Copy link
Collaborator

Since we do support google_universal (yet), and the events are the true issue here, I'm editing the issue title.

Yes, the hardcoded category is a problem. What's your proposed solution? Also--how would your change affect the other tracking systems analytical supports?

@sfsekaran sfsekaran changed the title Full support for google_universal GA Event category should not be hardcoded to "Event" Jun 3, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants