Skip to main content

​
Event properties vs. Customer properties

Event properties and Customer properties are not automatically linked. Customer properties describe who the customer is, and event properties log what the customer does. Customer properties = who they are. Describe the customer, their name, email address, language, location or other details that you may want to update over time. vero.customerproperties Event properties = what they do. Event properties are tracked along with events. Events are actions such as “registered” or “completed-checkout”. These events also have their own properties about them, and are often used to scope details about that event. For example, you might trigger “completed-checkout” and track “total_cost” and “product_details” as associated event properties. vero.eventdata The way that these details are tracked via the API is also separate. If a customer triggers an event with properties and you would like to update them as customer properties, your technical team would want to configure tracking to also tell Vero to update these details via an “identify” call. More details on this can be found in the API reference. We have more details about Customer properties here and Events here.