Across
- 4. event types are the parents, but these children still set the final rules
- 5. this event type fires when things go wrong
- 7. the first in a sequence of events we need the message.context to populate on
- 9. this event type often fires when the screen changes but the URL does not
- 10. this can be used to tell us the state of the platform, but not a state within a feature flow
- 11. If you want to know how long a user viewed an asset on a platform, use these bookend event types
- 13. it's either triggered by a user exit, a user success, or an application error
Down
- 1. if the application sends the user to a different spectrum platform, fire this event type on the new platform
- 2. this abbreviation lets us know the render has just begun
- 3. this is where experiment variants are assigned
- 6. query for specific event types in Quantum using this field
- 8. this event type fires when a user returns to the original application for which they had been linked out from
- 12. app version persists across an entire visit, but is first recorded here