RFC/PROPOSAL: add session_id to event.schema #17
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What/Why
What are you proposing?
We propose that the event schema contain a dedicated session ID field so that consumers of UBI data can track what users (authenticated and anonymous) are doing on dedicated visits.
client_id
does not uniquely identify a user (since two users with the same browser version would point to the sameclient_id
) and theuser_id
proposed in this PR will not always be available.What users have asked for this feature?
We have spoken to data analysts who work on analyzing user behavior.
What problems are you trying to solve?
The analysts we spoke to mentioned that a
session_id
is an important field in addition toclient_id
anduser_id
to understand shifts in the user behavior over time. They also mentioned how they often need to correlate search-interactions tied to a session against the other interactions that would also be tied to a session.Are there any security considerations?
No additional security impact as the existing recommendation was to already track the user ID under the
client_id
field. This is of a similar impact.Are there any breaking changes to the API
Yes, the
session_id
is proposed as a required field.What is the user experience going to be?
Customer can configure and analyze the user-behaviors along an additional axis that is well-separated from
client_id
anduser_id
.Are there breaking changes to the User Experience?
No
Why should it be built? Any reason not to?
This will allow the separate customer personas (front-end developer and behavior analyst) to be able to perform their tasks better with less coordination required as it reduces ambiguity around what attributes are tracked in which fields.
What will it take to execute?
Any remaining open questions?
No.