Understanding Semantic Events
Many of our default destination actionsThe source event and data that triggers an API call to your destination. For example, an incoming
identify event from your sources adds or updates a person in our Customer.io Journeys destination. are based on the
name of the event you send. With these semantic events, we expect a certain set of properties that we use to map to multiple destinations.
While you can send any properties and events that you want, taking advantage of our pre-defined semantic events can save you time and effort, helping you take advantage of our default actions—so it’s easier to get up and running with your destinations.
We have sets of standard semantic events for the following purposes:
Within these events, we also have semantic properties—properties that we expect to see in certain events. These properties are also mapped to our default destinations, so you can get up and running quickly.
For example, the
product_viewed event in our ecommerce specification typically contains
brand properties, so you know which product people viewed and the brand of that product.