...
- Wish list for event tracking from microfrontends:
- All events sent to Segment using (wrapped) Segment calls. Gives additional benefits of resilient JS code (e.g. trackLink and trackForm).
- Note: for Tracking Log events, both the front-end code is not resilient, and it relies on calling LMS which is not the most reliable option.
- Ideally, all events sent to reliable Destination to not lose events (e.g. AWS Bucket).
- Processing could be handled async on server.
- Could handle adding user_id given username (e.g. for Profile API).
- Need a way to indicate stability of event.
- Versioned? Other indicator? Available to GA as well?
- Can/should solution be kept out of the name (e.g. "edx.bi"), or should the version be part of the name?
- Using RAPID, who are all the I's for event design at this point, including potential for refactoring legacy events?
- Need a way to configure to where an event should be sent, including tracking logs and GA.
- Simplified defaults and decision making around this?
- Special considerations for GA? Send from backend processor back to Segment and on to GA? Different GA properties?
- Front-end consistent naming needed. Use Segment names? Tracking log names? Other? See code comment.
- Bill DeRusha (Deactivated) has additional thoughts that require a conversation.
- All events sent to Segment using (wrapped) Segment calls. Gives additional benefits of resilient JS code (e.g. trackLink and trackForm).