At Ventrata, we track various user interactions and events on our platform to provide a comprehensive view of customer interactions with checkout. These events are sent to Segment, allowing you to analyse and understand user actions in detail.
Below, you will find information about the events we currently track, the attributes they include, what those attributes represent, and the specific steps during the checkout process when they are triggered.
The data collection can be divided into two distinct groups based on specific behaviour:
Main Event Properties
Main Event Properties are the specific pieces of data that are sent with each event based on what is being tracked at that moment.
These properties provide detailed information about the event, helping to understand the context and specifics of the user's actions.
Attributes like product name, currency, price, and others are being sent to Segment with precise timestamp of end user's action.
Segment's Identify Method
The Identify method in Segment is used to tie a user to their actions and respective events. This method is crucial for linking customer data to all events once the contact information is available.
Initially, when segment receives events (
Product Viewed,Product AddedandCheckout Started), they do not include customer information. However, after the customer fills in their contact details in that contact form, this information gets propagated to all subsequent events.In the Ventrata checkout process, data are available once the the contact form is completed and the customer presses the Pay Now button, which triggers the
Create Or Update Orderevent.
Event: Product Viewed
The Product Viewed event, also known as the "view_item" event in Google's terminology, is triggered when an end customer views a product detail page on your website
As shown in the example below, the Product Viewed event is sent immediately after Ventrata's checkout page loads.
In the embedded version, this event is triggered right after the web page containing the embedded mode is loaded.
This event helps you track and analyse which products your customers are interested in by capturing essential information each time a product page is viewed.
Main Event Properties
Main Event Properties are the specific pieces of data that are sent with each event based on what is being tracked at that moment.
Attribute | Description | Example |
| product name |
|
| unique product and option identifier |
|
| option name |
|
Segment's Identify Method
The Identify method in Segment ties a user to their actions and respective events, linking customer data to all events once contact information is available. Initially, events like Product Viewed, Product Added and Checkout Started do not include customer information. However, after the customer fills in their contact details in the contact form, press the Pay Now button, which triggers the Create Or Update Order event, this information is propagated to all mentioned events.
Attribute | Description | Example |
| indicates whether the 'Send me the latest offers' box is checked |
|
| the country selected in the contact form |
|
| the email address entered in the contact form |
|
| the name entered in the contact form |
|
| the full name entered in the contact form |
|
| the surname entered in the contact form |
|
| used locales on the contact form |
|
| optional notes provided by the end customer |
|
| the customer's phone number entered in the contact form |
|
| the postal code entered in the contact form |
|
| the street entered in the address line of the contact form |
|
Event: Product Added
The Product Added event, also known as "add_to_cart" in Google's terminology, is triggered when an end customer adds a product to their cart.
This event captures the moment a customer decides to purchase a product by adding it to their shopping cart, including details about the selected units, date, and time.
By clicking on the Continue button, as showcased in the picture below, after the end customer selects the unit, date, and time, we send this event to Segment.
By tracking the Product Added event, you can gain insights into customer purchasing behaviour, your inventory and understand potential opportunities to improve the purchasing process and increase conversion rates.
Main Event Properties
Main Event Properties are the specific pieces of data that are sent with each event based on what is being tracked at that moment.
Attribute | Description | Example |
| product name |
|
| unique product and option identifier |
|
| option name |
|
| currency of the items associated with the event |
|
| monetary value of the event - revenue (tax excluded) |
|
| total number of units in the transaction |
|
Segment's Identify Method
The Identify method in Segment ties a user to their actions and respective events, linking customer data to all events once contact information is available. Initially, events like Product Viewed, Product Added and Checkout Started do not include customer information. However, after the customer fills in their contact details in the contact form, press the Pay Now button, which triggers the Create Or Update Order event, this information is propagated to all mentioned events.
Attribute | Description | Example |
| indicates whether the 'Send me the latest offers' box is checked |
|
| the country selected in the contact form |
|
| the email address entered in the contact form |
|
| the name entered in the contact form |
|
| the full name entered in the contact form |
|
| the surname entered in the contact form |
|
| used locales on the contact form |
|
| optional notes provided by the end customer |
|
| the customer's phone number entered in the contact form |
|
| the postal code entered in the contact form |
|
| the street entered in the address line of the contact form |
|
Event: Checkout Started
The Checkout Started event, also known as "begin_checkout" in Google's terminology, is triggered when an end customer begins the checkout process by transitioning from browsing to the final steps of purchasing, indicating a strong intent to buy.
After a customer adds a product to their cart, they might be presented with an 'upgrade' or 'cross-sell' opportunity, if you set up the product this way. The customer can choose to add these options or proceed directly by clicking the Continue button.
When the customer clicks Continue, they move on to the checkout process. This action triggers the Checkout Started event as showcased on the screenshot below.
Main Event Properties
Main Event Properties are the specific pieces of data that are sent with each event based on what is being tracked at that moment.
Attribute | Description | Example |
| product name |
|
| unique product and option identifier |
|
| option name |
|
| currency of the items associated with the event |
|
| monetary value of the event - revenue (tax excluded) |
|
| tax cost associated with a transaction |
|
| unique order identifier |
|
Segment's Identify Method
The Identify method in Segment ties a user to their actions and respective events, linking customer data to all events once contact information is available. Initially, events like Product Viewed, Product Added and Checkout Started do not include customer information. However, after the customer fills in their contact details in the contact form, press the Pay Now button, which triggers the Create Or Update Order event, this information is propagated to all mentioned events.
Attribute | Description | Example |
| indicates whether the 'Send me the latest offers' box is checked |
|
| the country selected in the contact form |
|
| the email address entered in the contact form |
|
| the name entered in the contact form |
|
| the full name entered in the contact form |
|
| the surname entered in the contact form |
|
| used locales on the contact form |
|
| optional notes provided by the end customer |
|
| the customer's phone number entered in the contact form |
|
| the postal code entered in the contact form |
|
| the street entered in the address line of the contact form |
|
Event: Create Or Update Order
The Create Or Update Order event is triggered when an end customer completes a step in the checkout process.
This event is associated with filling out the contact details form and indicates that the customer is progressing toward finalising their purchase. These contact details then get propagated to other events in Segment.
By clicking on the Pay Now button, as illustrated in the screenshot below, after the end customer fills out the form and checks all of the required boxes, this event will be sent to Segment.
Main Event Properties
Main Event Properties are the specific pieces of data that are sent with each event based on what is being tracked at that moment.
Attribute | Description | Example |
| unique order identifier |
|
| product name |
|
| unique product and option identifier |
|
| currency of the items associated with the event |
|
| option name |
|
| monetary value of the event - revenue (tax excluded) |
|
| tax cost associated with a transaction |
|
Segment's Identify Method
The Identify method in Segment ties a user to their actions and respective events, linking customer data to all events once contact information is available. Initially, events like Product Viewed, Product Added and Checkout Started do not include customer information. However, after the customer fills in their contact details in the contact form, press the Pay Now button, which triggers the Create Or Update Order event, this information is propagated to all mentioned events.
Attribute | Description | Example |
| indicates whether the 'Send me the latest offers' box is checked |
|
| the country selected in the contact form |
|
| the email address entered in the contact form |
|
| the name entered in the contact form |
|
| the full name entered in the contact form |
|
| the surname entered in the contact form |
|
| used locales on the contact form |
|
| optional notes provided by the end customer |
|
| the customer's phone number entered in the contact form |
|
| the postal code entered in the contact form |
|
| the street entered in the address line of the contact form |
|
Event: Order Completed
The Order Completed event, also known as "purchase" in Google's terminology, is triggered when an end customer successfully completes their purchase.
This event marks the final step in the customer journey, indicating that the payment has been processed and the booking has been confirmed.
By tracking the Order Completed event, you can gain comprehensive insights into completed transactions.
On the example below, you can see the Success page, where we sent the Order Completed event to Segment.
Main Event Properties
Main Event Properties are the specific pieces of data that are sent with each event based on what is being tracked at that moment.
Attribute | Description | Example |
| product name |
|
| unique product and option identifier |
|
| option name |
|
| currency of the items associated with the event |
|
| monetary value of the event - revenue (tax excluded) |
|
| tax cost associated with a transaction |
|
| unique order identifier |
|
Segment's Identify Method
The Identify method in Segment ties a user to their actions and respective events, linking customer data to all events once contact information is available. Initially, events like Product Viewed, Product Added and Checkout Started do not include customer information. However, after the customer fills in their contact details in the contact form, press the Pay Now button, which triggers the Create Or Update Order event, this information is propagated to all mentioned events.
Attribute | Description | Example |
| indicates whether the 'Send me the latest offers' box is checked |
|
| the country selected in the contact form |
|
| the email address entered in the contact form |
|
| the name entered in the contact form |
|
| the full name entered in the contact form |
|
| the surname entered in the contact form |
|
| used locales on the contact form |
|
| optional notes provided by the end customer |
|
| the customer's phone number entered in the contact form |
|
| the postal code entered in the contact form |
|
| the street entered in the address line of the contact form |
|