Understanding semantic events
Many of the actions The 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.name of the event you send. With these semantic events, we expect a certain set of properties that we use to map to multiple integration 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 set up data-out integrations.
We have sets of standard semantic events for the following purposes:
Semantic Properties
Within these events, we also have semantic properties—properties that we expect to see in certain events. These properties are also mapped to our data-out integrations, so you can get up and running quickly.
For example, the product_viewed event in our ecommerce specification typically contains product_id and brand properties, so you know which product profiles viewed and the brand of that product.