Custom Events
These are events passed through third-party integrations or tracked user activity on your app or website. They're termed "Custom Events" because they are specifically defined and monitored for the referenced app or website.
If you've integrated the Contlo SDK, you can send custom events tracked for your business to Contlo, including custom parameters.
Let’s take the example of a mobile e-commerce app and map out the actions its users need to perform to make a purchase:
| Action | Event |
|---|---|
| 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 |
These parameters are sent alongside the predefined system attributes, enhancing your understanding of the event's context.
Charged events
This is a special event that captures details of customer purchases, including items, categories, transaction amount, transaction ID, and information about the respective user. Recording a purchase against a user marks them as a customer in Contlo. This enables you to compare your funnel reports between customers and non-customers.
This event has the following advantages -
- Helps you identify your customers, and how are they using your app or website.
- Run campaigns to reward loyal customers or get lost customers back.
- Measure customer loyalty via running a cohort analysis on repeat purchases.
- Analyze paid campaign performance by total revenue earned.
- Get revenue insights like – total revenue, number of transactions, count of paying users, and more.
Properties
The charged event has the following properties:
| Parameter | Type | Description |
|---|---|---|
| event_id | string | Used to map the event. |
| transacation_value | string | The total transaction amount attributed to the revenue. |
| variant_id | string | The corresponding variant(s) ID for which the transaction is taking place. |
| event_type | string | Type of event (Charged) |
| currency | string | Currency code of variant prices. Follows ISO 4217:2015 format. |
| transaction_id | string | Unique identifier of the transaction. |
| string | Email ID of the customer | |
| phone number | string | Phone number of the customer. |
| product_id | string | The corresponding product (s) ID for which the transaction is taking place. |
| time | Long | Epoch time in milliseconds. |
Sending Events to Contlo
You can send events to Contlo via any of the following methods:
- Mobile SDK
- Web SDK
- WooCommerce integration
- External platform integrations (Eg. Shopify, GoKwik, etc.)
Sending an undefined event or parameter via client-side, server-to-server, or native/third-party integrations is captured by Contlo's database using the name and key you set. Therefore, there's no need to whitelist your custom events or parameters.
Updated 4 months ago