Fat event triggers with pinned property
complete
G
Giorgio
When dealing with fat events in Avo there are currently 2 choices:
- the docs recommend to create one trigger for each occurrence of the event, but there's no way to specify if allowed property values are any different between them beyond using the trigger description
- if you want to pin a distinguishing property value for each trigger + use name mapping. This inflates the tracking plan and increases the risk that any event occurrence might have "something" different than the rest (beyond the obvious case of that property itself).
It would be better in my opinion to allow each trigger to pin property values. This way you could get the best of both worlds and triggers would have more meaning beyond being just screenshots and text
Hugi Hlynsson
complete
This has been solved with the introduction of event variants that can have pinned properties as well as screenshots attached to them. Read more in our docs: https://www.avo.app/docs/data-design/avo-tracking-plan/event-variants