Any metadata associated with the event.
Object keys are expected to be strings, and cannot contain any of the following special characters:
- double quote "
- curly braces { }
- square brackets [ ]
- backslash \
- vertical bar |
Object values can be any type. Note that both object keys and object values are case sensitive. For example, "deliverydate" and
"DeliveryDate" would be considered different event properties.
Notes:
- Lists and nested objects can only be used with email messages. Lists and nested objects are not currently supported for SMS.
- When attempting to access double or deeper nested lists in a Custom Events journey message, nested lists are not available for easy selection in the "Insert Variable" dropdown modal. You can manually write out the path to access the nested list as a variable, which can then be resolved in a message using Liquid loops. If the Liquid is written correctly, the nested Liquid list will validate correctly in both the Real Subscriber Preview and in sent messages. Note: nested objects are accessible via the "Insert Variable" modal today, but nested lists are not.
- For URLs that are provided as a value, Attentive will automatically shorten the link with your brand's link shortener. For example, https://mysite.com/. Note that Attentive can only shorten URLs that are 1,024 characters or fewer.
- Custom events must be triggered using the same custom app that originally created them.
- There is a maximum of 200 object keys per custom event type. While payloads larger than this will be saved, not all keys will be available for use in Journeys and macros.
