Event Dictionary
Presenting the capabilities and the benefits of Event dictionary
Event Dictionary is the global event definition database for your account. It helps the marketeers define the event schema to ensure consistency across all sources.
Benefits of using Event Dictionary
Helps define the event schema including event name, properties and property data types.
Ensures consistency of events among all data sources.
Ensures that only correct data enter the system and doesn't hinder.
Helps the marketeers to add/delete/modify the properties in real-time.
Allows you to filter the events going to a specific destination.
What is an event?
An event is any action in a website/App that is performed by the customer while interacting with your business.
Think about the time you wanted to buy a product, your customer journey will be as follows - You visited the brand's website and the website homepage loaded. You went ahead and scrolled the page and clicked on the product you wanted to buy. You checked for a few offers and added the product to the cart. Later, you received an email which informed you about the ongoing offer for the product you wanted to buy, you clicked on that email and were directed to the buy now page. You completed the payment and the order was placed.
In the above scenario, the following would be considered events:
"Page load" when you visit the website
"Track" when you scroll down the page to look for the product you wanted to buy
"Click on the product" When you click on the product
"Add to cart" when the product was added to the cart
"Click on the email link" when you see the offer in the email and click it
"Page load" when you are directed to the buy page
"Order placed" when you are completed with the payment
Types of events in Lemnisk
Standard events
Events for which a standard mapping with attributes is present in Lemnisk for different destinations. These are automatically mapped events in Lemnisk.
Identify: Identifies the user and merges the cookie ID with the existing profile
Example: Login, Subscription, etc. To know more click here
Page: Identifies the pages viewed by the user. It helps create a customer funnel and identify which page the user dropped. To know more click here
Screen: Identifies the screen viewed by the user on the app. It helps create a customer funnel and identify which screen the user dropped. To know more click here
Track: Track the user behaviour on the website/app.
Example: Time spent on the app, product added to the cart, where the customer dropped in a video. To know more click here
To view standard events -
Go to > Data Pipeline > Event Dictionary > Standard Events
Custom events
Events for which a standard mapping with attributes doesn’t exist in Lemnisk. These events need to be created by businesses and map them with destinations.
Transformation
Transformations in Lemnisk is the process of transforming the user/event attributes in the destination-compatible format. Custom events are required to be created for performing a transformation on them since the transformation is set up at the destination level. It is a one-time activity for tracking a particular event for a destination. Since it can be created at an individual destination level, the same event can be tracked on different platforms.
For example: "productviewed" may be transformed as "viewedproduct" for Facebook, "viewed" in Google Ads, etc.
To create a transformation -
Go to > Data Pipeline > Destination
Select any destination and navigate to Transformation
Click Add Transformation
Select the events for transformation from the list of Events
Test any event by selecting the event in the Events field below the code snippet and clicking Run Test
Click Validate and Save to save your transformation
You can delete the transformation using the button Delete Transformation placed in the left corner of the window.
Types of Events
Event Dictionary has 2 events type
Standard Events.
Custom Events.
Standard Events
Standard events are enabled by Lemnisk by default. They are page, screen and identify methods.
Custom Events
Custom events lets you create custom track events that you want to track on the website. These track events capture the customer behaviour in the form of event and event properties.
For example, you can create a custom event to capture a product click, track purchases, capture user information etc.
Create a custom event
Click on "Create New Custom Event ".
Add a name to your event.
Add a description to your custom event.
Click on Save and the event will be created.
Add a property to the newly created custom event.
In the events properties mention the custom event's property name.
Define data type like STRING, NUMBER, etc. Know more about the available data types here.
Give a description to the property and hit the Save icon.
You can edit the property name, type and description for an existing property. You can delete the unused properties.
Map events to the destination in the Allowed Destinations section.
Channel Events:
Channel event refers to any specific, trackable action or interaction a user performs within a particular communication or marketing channel. These events are the fundamental building blocks for understanding user behaviour and campaign effectiveness across various touchpoints.
Essentially, a channel event captures "what happened, where it happened, and when it happened" within a given marketing channel. By tracking these events, marketers gain granular insights into how users engage with their brand across different platforms and communication methods.
Supported Channels and Events
Channel
Events
Sent
Delivered
Opened
Clicked
SMS
Sent
Delivered
Clicked
RCS
Sent
Delivered
Read
Clicked
Sent
Delivered
Read
Clicked
Banner Personalisation
Delivered
Clicked
NotBot
Delivered
Clicked
Onsite Notification
Delivered
Clicked
Closed
App Push Notification
Sent
Delivered
Clicked
Dismissed
Subscription
Web Push Notification
Sent
Delivered
Clicked
Dismissed
Subscription
👍🏻 Congratulations! You have successfully added a custom event to your event dictionary.
Last updated