Telemetry implementation best practices for web app analytics

[coolbung]

Wanted to understand the best practices for using start event for sessions in the context of web applications.

A little background first of all - we're trying to implement telemetry in an angular web app. The goal is to measure statistics similar to Google analytics viz

• Total visitors
• Unique visitors
• Which browsers / platforms are being used
• What are the locations
• How many pageviews
• Top pages
• Avg pages per session
• Avg time spent in each session
• What % of visitors viewing course details are enrolling
• What are the top searches
• What are the busiest times of the day

A few specific questions / observations

1. When a (guest) user visits the site a session start is sent with a session id (context.sid) but in this case what should be the actor.id The telemetry SDK uses the device fingerprint id as actor.id in case of guest
2. When the above user logs in another session start event is sent this time with the same context.sid as previously but with the actor.id set to the users id from the auth system
3. IMPRESSION event is generated on each navigation event in angular. Here edata.uri will have the route (eg: /course/details/javascript-basics) and edata.pageid has a unique name for the page eg: CourseDetails
4. Send INTERACT events for tracking actions eg: enrolling to a course
5. Send a search event with query and filters when user searches

Can you confirm all the above are in aligned with how telemetry should be used for web activity tracking?

@pramodkvarma @anandp504 @SanthoshVasabhaktula

cc @snehal0904