Events are the basic data you can collect with Synerise. In this section, you can see a list of events you’re currently tracking in your business profile, manage them, create new ones or delete.
Manage your data
While working in the application, you can decide what kind of events and their parameters you track. You can manage events by adding, editing and removing them in
Data Management → Events.
Add new event
You can add a new event at any time in the application.
- Click Add event in the upper right section.
Fill all required sections:
- Event source - This is the source name of the event. It will not be displayed if you provide the regular event name in the field Event name (2).
- Event name - This is the main name of the event, this name identifies the event in the system and lets you find the event by the name given in this section.
- Description - You can write a detailed explanation about the event and at the same time let other users know what is its purpose.
- Group - Define the groups to which the created event belongs. Groups will help you organize the events and their parameters.
- Show card - Decide if you want to show an event in the dropdown menu in the Analytics module; if not, switch the green button off.
Submit by clicking Save.
Edit existing event
When you have added events, you can edit them in the system at any time.
- Click the three dots and you’ll see two options: edit and remove.
- Click Edit button.
After clicking the edit button, you will see a pop-up with the same settings described in the section above. Change settings and submit the changes by clicking Save.
Delete existing event
When you have added events, you can delete them if needed.
- Search for an event you want to delete.
- Click the three dots icon.
- Click Remove.
Each event has some parameters which are describing the event. Click the event name to open list of parameters assigned to the event.
Edit event parameter
- Click the three dots, you’ll see two options: Edit and Remove.
- Click Edit.
Additionally you can hide the event, so it will not be visible for all users in the business profile. Switch on or off the green button. If you hide the event, it won’t be displayed in the dropdown menu in Analytics module as well.
- Source parameter - This is the source name of the event parameter. It will not be displayed if you provide the regular event name in the field Property name (2).
- Property name - This is the main name of the parameter, this name identifies the parameter in the system and lets you find the parameter by the name given in this section.
- Description - Add a description to a parameter. This one is not obligatory, but it can help other users to understand better the meaning of a particular parameter.
- Property type - You can set what type of data is sent as a value for the current parameter. To do this, choose appropriate type from the dropdown menu in property type option.
- Group - Define the groups to which the created parameter belongs. Groups will help you organize the parameters and events (this function is not available yet).
- Link to - Choose a catalog you want to use to enrich event. You can enrich every single event with data from any catalog based on event parameter and key value from catalog. For example, if you have product feed in Synerise catalog, you can join all products meta data (for example image url, category or product variant) to event. Read more about Catalogs.
The system allows you to enrich the data of events with the data from a catalog. In other words, it allows to add specific parameters to the chosen event, if the value of the particular event parameter has been found in a particular catalog.
What you need to do?
- Create a catalog. When you import the catalog to Synerise, you need to define the key (name of the column) to indicate a particular column of which the values will be analyzed and an event will be enriched with data available in the catalog for a specific value in the column that is marked as the key. In this case it is
- Find an event parameter of the event you want to enrich and define a common denominator for an event and a catalog (
example_keyas the illustration above). The
example_keyis assigned as a parameter of the
- Define the catalog from which information used to enrich the event is sourced. This catalog needs to have a column named like the event parameter. In this case, it will be
catalog_1. If you haven’t prepared such catalog yet, you need to create one.
Custom event occurs, and
example_key (an event parameter) has a specific value assigned (e.g. 11), then the system checks
catalog_1 to find a record with value equal to 11.
If the system finds it, the event will be enriched with three additional pieces of information: the first name of the user, the city and gender: Janine, Indianapolis, female.
The effect of matching the value of
example_key in the event with the value of table
example_key in catalog is visible on the client card in the CRM module. Because the value of
example_key in the event amounts to 11, the system supplied this event with additional information included in the catalog under the record with the same value for