Event types
The tree groups the 30 event types into nine families. Ticking a family row selects every type under it; expand the row to pick individual types. The header checkbox selects all of them, and the counter above the tree tracks how many of the 30 are selected. At least one type is required — the dialog will not create or save a subscription without one.What each type means, and what its payload carries, is listed in the Events API reference.
Conditions
Add condition adds aproperty eq value row. The property list holds only the properties the selected event types actually carry:
Select several families and the list offers the union of their properties.
Every property except
apiVersion picks its value from a list of what exists in the environment — sources, card definitions, segments, destinations, endpoints, API versions or users — and sends the underlying id rather than the name you chose. apiVersion is the version number itself, so you type it.
Narrowing the event types can strand a condition on a property the remaining types do not carry. Studio then re-points that row at the first property that is still allowed — check the conditions again after you change the selection.
The compiled expression
Filter expression shows exactly what Studio sends, in a grammar limited toeq, and and or:
or and bracketed as a group once a condition is present; conditions are appended with and. A condition left without a value is omitted from the expression preview, but it blocks creation and saving. Fill in the value or remove the condition before submitting.