Events setup
Entities setup is usually done by the CDP technical consultant.
In the Administration/Entities/Events tab, it is possible to create, edit, show/ hide events that will be used through Meiro Business Explorer (the basis for identity stitching and attribute calculation, displayed for each customer in the Customer Profile Detail tab/ Timeline). In this tab, you can also find system events that are automatically generated after configuring the channels. These system events are distinguished by a specific system tag, and they cannot be hidden.
A full list of events will be visible to users in the Data Library/ Events tab.
Learn from this article: |
1. Create event
To create an event, please click on the Create Event button and fill out the form that will be displayed.
General |
|
|
|
|
Event Name |
Name your event that will be displayed across Meiro Business Explorer. It is possible to edit the name later on. |
|
|
|
Source (not editable later) |
Pick the data source from which this event comes from. |
|
|
|
Event Type (not editable later) |
Insert an event type (for example, web_pageview, web_transactions, etc.). |
|
|
|
Event Version (not editable later) |
Assign the version of this event that you can refer to later. |
|
|
|
Event Retention (optional) Select after how many days events will be deleted (max 5000). It is recommended to avoid storing events for too long as it may influence the costs of data storage. There is no general recommendation about how long events should be stored, it depends on the nature of the event. Usually, more information is collected, and it is advised to store it for a longer time. By default, Event Retention is 0 (infinite). To learn more, contact the Meiro team. |
|
|
|
|
PriorityIf the toggle is activated, the event will receive priority in processing. |
|
|
|
|
SchemaThe schema describes the way how event payload should be displayed in the user interface. It is possible to set multiple items that will be displayed. |
|
|
|
|
Title |
Set the title of the payload. The event title is the further specification of the event. For example, event type "Order Status Updated" may have the title "The customer's order changed the status to Awaiting bank payment" to specify the event further. The title will be visible under this name across Meiro Business Explorer. It is possible to edit it later on. |
|
|
|
Add items to display in the payload |
Name: Name your schema item. It will be visible under this name across Meiro Business Explorer. It is possible to edit it later on. Type: Set the item type (string, datetime, number). It is possible to edit it later on. Format: Pick one of the available formats (text, link, list). It is possible to edit it later on. Path: JSON path that points to value in payload corresponding to this payload item. It is possible to edit it later on. |
|
|
|
Warning: It will not be possible to edit Source, Event Type and Event Version later. In this case, hiding the event and creating a new one is recommended.
Remember: Newly created events will appear with the New
badge that will stay for the next 7 days.
Autoload
In this section, you can set the extraction of customer events from the ME database to MBE. This will eliminate the need to use MI for integrating data from ME to CDP, resulting in simplified deployment. Additionally, this approach reduces the probability of errors during configuration and speeds up the process.
Remember: One event type can have only one integration.
Autoload configuration
Click the ‘configure’ button to enable configurations of the CDP to the ME database.
Remember: You may disable these configurations with enable/disable toggle. In case you need to delete configurations of this integration, use the ‘remove’ button.
Transformations
In this section, you can specify the transformations the raw customer profile events might undergo to get the real payload. It is possible to use multiple transformations to achieve the desired result of the payload, and each transformation can be enabled or disabled individually using a toggle located next to each transformation.
Transformations support only value objects and they do not support analyzing and iterating throw array objects.
Remember: the order of transformations is important, as each transformation is applied one by one to the payload in the respective order.
Below, you can find available transformations for definition.
Test run
In the "test run" section, you have the option to click on the "fetch" button to experiment with the event using the specified settings. You can specify the desired number of events to fetch, with a maximum limit of 1000 events. As a result, you will receive an array containing the most recent values for the event time, user identifier, and payload.
2. Edit/ show-hide events
You can edit events at any time, and if necessary, you can hide them from the Meiro interface. While hidden, these events will remain invisible within the Meiro Business Explorer interface; however, they continue to be collected and will be present in stitching rules.
Warning: Not editable fields are: Source, Event Type, and Event Version. If filled wrong, it is recommended to hide the incorrect event and create a new one.
Events marked with the ‘system’ tag cannot be hidden. On the detail page, you may only edit the Schema section or copy the event to proceed with creating a new event.
3. Event example
An example of an event listed in the Data library/ Events tab:
For this event:
- Event Name: Account created on web
- Event Source: Bank website
- Event Type: picked from the drop-down list (in this case "account-created")
- Event Version: the version of this event (for example 1-0-0)
- Schema Title: Bank web account created
- Schema Name: Device family
- Schema Type: string
- Schema Format: text
- Schema Path: JSON path to this event