What are events?

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.

Event Categories

There are 2 major types of events in Contlo:

  1. Standard events:
    1. System events: These events are recorded automatically after you integrate our SDK.
    2. Message events: **These events are also recorded automatically in response to the actions performed by your users when interacting with the campaigns they receive.
  2. Custom events:
    1. Transactional events: These are custom events which you send to the SDK to capture transactions.
    2. 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

System events are events recorded automatically after you integrate our SDK.

Event NameDescription
App InstalledWhen the app is installed and launched for the 1st time
App LaunchedWhen the app is launched either from background state or in a fresh run
App UpdatedWhen the app is updated to a newer version
App BackgroundedWhen the app is sent to the background and is not in active use
App UninstalledWhen the app is removed or uninstalled from the device
Subscribed to EmailWhen the user opts in to receive email notifications
Subscribed to SMSWhen the user opts in to receive SMS notifications
Subscribed to WhatsappWhen 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 PushWhen the user opts in to receive mobile push notifications
Session StartedWhen the user starts a new session in the app
Session ConcludedWhen the user ends a session in the app
User Logged InWhen the user logs into their account in the app
User Logged OutWhen the user logs out of their account in the app
Advertising IDUnique ID used to personalize ads based on user's interests and behavior

Message Events

Message events are events recorded automatically in response to your users' actions after you integrate with our SDK.

Event NameDescription
Email SubscribedThe user has subscribed to receiving marketing emails
Email SentWhen an email has been sent to the user
Email DeliveredThe sent email has been successfully delivered to the user's inbox
Email OpenedThe user has opened the received email
Email ClickedThe user has clicked on a link within the email
Email BouncedThe sent email could not be delivered to the user
Email ComplainedThe user has reported the email as spam or unwanted
Email UnsubscribedThe user has unsubscribed from receiving marketing emails
SMS SentAn SMS message has been sent to the user
SMS ClickedThe user has clicked on a link within the SMS message
SMS FailedThe sent SMS message could not be delivered to the user
SMS UnsubscribedThe user has unsubscribed from receiving SMS messages
Whatsapp SentA Whatsapp message has been sent to the user
Whatsapp OpenedThe user has opened the received Whatsapp message
Whatsapp ClickedThe user has clicked on a link within the Whatsapp message
Whatsapp UnsubscribedThe user has unsubscribed from receiving Whatsapp messages
Push ClickedThe user has clicked on a push notification
Push ClosedThe user has closed the push notification without interacting with it
Mobile Push Notification SentA push notification has been sent to the user's mobile device
Mobile Push Notification ReceivedThe user's mobile device has received the push notification
Mobile Push Notification ClickedThe user has clicked on the received mobile push notification
Mobile Push Notification DismissedThe user has dismissed the mobile push notification without interacting with it

What are event properties?

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.

System Properties:

Contlo tracks the following system properties automatically from the Mobile SDK for all events.

System PropertyDescription
Event TypeThe type of event being captured (System, Message, Charged or Custom).
Model NameModel of the device through which user performed the event.
OS TypePlatform on which the event occurred. (Android, iOS or Web)
App NameThe name of the Application on which the event was performed.
App VersionThe current version of your application installed on the user device.
ManufacturerName of the device manufacturer through which user performed the event.
API LevelAndroid defined API level of the device
Network TypeThe network type of the device. For example WiFI
OS VersionThe Operating system of the device. For example, 1.0.0
SDK VersionThe Contlo SDK version. For example, 1.0.1
SourceThe source of the event. For example, the event may originate from a Mobile device or a Web platform.
Package NameUnique identifier for an app on the device or the Google Play Store
Device Event TimeTime at which the event occurred (in ISO format).
Time-zoneTime-zone of the device

Custom properties:

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.

Custom Events:

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:

ActionEvent
Search for a productSearch
View product detailsProduct - Page Viewed
Select product quantityProduct - Quantity Selected
Add to cartProduct - Added to Cart
View CartCart Viewed
Initiate checkoutCheckout - Started
Add mode of paymentCheckout - Payment
Select delivery optionCheckout - Delivery
Confirm and place the orderCheckout 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.

Charged Events

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.

Sending Events to Contlo

You can send events to Contlo via any of the following methods:

  1. Contlo's Mobile SDK
  2. Web event integration
  3. WooCommerce integration
  4. 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.

Naming events

  • 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”