Events track the individual actions your users perform while interacting with your App, website or campaigns. For example, if a user clicks on the Add to Cart button on a product page, their action triggers an added to cart event.
By tracking events, you can follow what actions your users are doing & use this to understand their goals. You can use these events to create advanced segmentation & targeting, and personalize your user experience with individualized content. You can also analyze these events to measure how a specific event trends over time, or how a certain segment of users might be performing in comparison to another.
There are 2 major types of events in Contlo:
- Standard events:
- System events: These events are recorded automatically after you integrate our SDK.
- Message events: **These events are also recorded automatically in response to the actions performed by your users when interacting with the campaigns they receive.
- Custom events:
- Transactional events: These are custom events which you send to the SDK to capture transactions.
- Non-transactional events: These are all custom events which you want to track on your app or website, or pass via integrations to Contlo
System events are events recorded automatically after you integrate our SDK.
|App Installed||When the app is installed and launched for the 1st time|
|App Launched||When the app is launched either from background state or in a fresh run|
|App Updated||When the app is updated to a newer version|
|App Backgrounded||When the app is sent to the background and is not in active use|
|App Uninstalled||When the app is removed or uninstalled from the device|
|Subscribed to Email||When the user opts in to receive email notifications|
|Subscribed to SMS||When the user opts in to receive SMS notifications|
|Subscribed to Whatsapp||When the user opts in to receive Whatsapp notifications|
|Subscribed to Push (Web)||When the user opts in to receive web-based push notifications|
|Subscribed to Mobile Push||When the user opts in to receive mobile push notifications|
|Session Started||When the user starts a new session in the app|
|Session Concluded||When the user ends a session in the app|
|User Logged In||When the user logs into their account in the app|
|User Logged Out||When the user logs out of their account in the app|
|Advertising ID||Unique ID used to personalize ads based on user's interests and behavior|
Message events are events recorded automatically in response to your users' actions after you integrate with our SDK.
|Email Subscribed||The user has subscribed to receiving marketing emails|
|Email Sent||When an email has been sent to the user|
|Email Delivered||The sent email has been successfully delivered to the user's inbox|
|Email Opened||The user has opened the received email|
|Email Clicked||The user has clicked on a link within the email|
|Email Bounced||The sent email could not be delivered to the user|
|Email Complained||The user has reported the email as spam or unwanted|
|Email Unsubscribed||The user has unsubscribed from receiving marketing emails|
|SMS Sent||An SMS message has been sent to the user|
|SMS Clicked||The user has clicked on a link within the SMS message|
|SMS Failed||The sent SMS message could not be delivered to the user|
|SMS Unsubscribed||The user has unsubscribed from receiving SMS messages|
|Whatsapp Sent||A Whatsapp message has been sent to the user|
|Whatsapp Opened||The user has opened the received Whatsapp message|
|Whatsapp Clicked||The user has clicked on a link within the Whatsapp message|
|Whatsapp Unsubscribed||The user has unsubscribed from receiving Whatsapp messages|
|Push Clicked||The user has clicked on a push notification|
|Push Closed||The user has closed the push notification without interacting with it|
|Mobile Push Notification Sent||A push notification has been sent to the user's mobile device|
|Mobile Push Notification Received||The user's mobile device has received the push notification|
|Mobile Push Notification Clicked||The user has clicked on the received mobile push notification|
|Mobile Push Notification Dismissed||The user has dismissed the mobile push notification without interacting with it|
All events have various details called event properties, which help you to understand the context of the event. For example, the above add to cart event might have product name, category and quantity as the event properties.
Contlo tracks the following system properties automatically from the Mobile SDK for all events.
|Event Type||The type of event being captured (System, Message, Charged or Custom).|
|Model Name||Model of the device through which user performed the event.|
|OS Type||Platform on which the event occurred. (Android, iOS or Web)|
|App Name||The name of the Application on which the event was performed.|
|App Version||The current version of your application installed on the user device.|
|Manufacturer||Name of the device manufacturer through which user performed the event.|
|API Level||Android defined API level of the device|
|Network Type||The network type of the device. For example WiFI|
|OS Version||The Operating system of the device. For example, 1.0.0|
|SDK Version||The Contlo SDK version. For example, 1.0.1|
|Source||The source of the event. For example, the event may originate from a Mobile device or a Web platform.|
|Package Name||Unique identifier for an app on the device or the Google Play Store|
|Device Event Time||Time at which the event occurred (in ISO format).|
|Time-zone||Time-zone of the device|
You can also capture event specific custom properties for detailed tracking of user actions as per your business requirement. For example, for a "Video watched" event, one might want to capture the properties such as "Video ID", "Watch duration", etc.
These are all the events that you pass via various 3rd-party integrations, or track user activity for on your app or website.
Let’s take the example of a mobile e-commerce app and map out the actions their users need to perform to make a purchase:
|Search for a product||Search|
|View product details||Product - Page Viewed|
|Select product quantity||Product - Quantity Selected|
|Add to cart||Product - Added to Cart|
|View Cart||Cart Viewed|
|Initiate checkout||Checkout - Started|
|Add mode of payment||Checkout - Payment|
|Select delivery option||Checkout - Delivery|
|Confirm and place the order||Checkout Complete|
All the events listed above are called custom events as they have been explicitly defined and tracked for the e-commerce app in reference.
All custom events defined and explicitly tracked for your business can be sent (to Contlo) along with a set of custom parameters to help you understand their context better. These custom parameters are passed along with the pre-defined set of system attributes.
Contlo tracks purchase and other transactional events as a special 'Charged' event. This event is captured along with additional parameters such as product details, transaction value, transaction ID, currency, and information about your users.
For more information about recording a Charged event, refer to Recording Customer Purchases under the developer documentation.
You can send events to Contlo via any of the following methods:
- Contlo's Mobile SDK
- Web event integration
- WooCommerce integration
- External platform integrations (Eg. Shopify, GoKwik, etc.)
If you send an undefined event, or event parameter via any of the client-side, server to server, or native/third party/external integrations listed above, Contlo's database will capture this data with the name and key you set. This means that you do not need to perform white-listing of your custom events or event parameters.
- Use short event and property names if possible – this will help you when analyzing events in the dashboard
- Event names should match the action a user performs on your site. Example event names – “Viewed product”, “Added To cart”, "Checkout started", “Video watched”, etc.
- Whenever possible, use the same names across your mobile apps and websites
- Group similar events with a common prefix – e.g. “Booking initiated”, “Booking date selected”, “Booking completed”
Updated 2 months ago