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

Change ev_ to se_ in Tracker Protocol #197

Closed
alexanderdean opened this issue Mar 26, 2013 · 4 comments
Closed

Change ev_ to se_ in Tracker Protocol #197

alexanderdean opened this issue Mar 26, 2013 · 4 comments
Assignees
Milestone

Comments

@alexanderdean
Copy link
Member

ev_ is legacy now that we have two different types of custom event. Therefore the five structured event fields (category, action etc) should start with se_ for structured event. So e.g. ev_ac -> se_ac.

Note that the Scalding ETL already supports both options, so once more people have moved onto the Scalding ETL, we can make the change.

This will require updating the JavaScript and Arduino trackers (not the No-JS Tracker).

@ghost ghost assigned alexanderdean Mar 26, 2013
@rgabo
Copy link
Contributor

rgabo commented Mar 26, 2013

@alexanderdean, does this mean that you would standardise unstructured event fields with the usc_ prefix? IMHO ue_ might be a better choice as it is shorter and follows the same naming as se_.

Let's discuss and decide here and we can contribute the documentation change to https://github.com/snowplow/snowplow/wiki/snowplow-tracker-protocol#310-custom-unstructured-event-tracking.

@alexanderdean
Copy link
Member Author

Agree - ue_ should be the prefix for unstructured events, short and to-the-point.

@alexanderdean
Copy link
Member Author

Ah - just realised the Tracker Protocol says usc, hence your confusion! I have updated the Tracker Protocol to say ue now.

@alexanderdean
Copy link
Member Author

Implemented as part of 0.8.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants