Custom Events

The type of event. This name is case sensitive. "Order shipped" and "Order Shipped" would be considered different event types.

The Custom Event type cannot any of the following special characters:

• double quote "
• single quote '
• parentheses ( )
• curly braces { }
• square brackets [ ]
• backslash \
• vertical bar |
• commas ,

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:

• When you’re creating journeys that use custom events data, you can only use lists and nested objects can only be used with email messages. Lists and nested objects are not currently supported for SMS.
• 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.

A unique identifier representing this specific event. A UUID is recommended.

Timestamp of when the action occurred in ISO 8601 format. If the timestamp is older than 12 hours, it will not trigger any relevant Journeys. If no timestamp is provided, it is assumed the event occurred when the endpoint is called.