You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
@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_.
ev_
is legacy now that we have two different types of custom event. Therefore the five structured event fields (category, action etc) should start withse_
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).
The text was updated successfully, but these errors were encountered: