The Data Manager allows you to manage the following elements of your project:
- Add, edit, or delete customer and event properties
- Create definitions (Aggregates, running aggregates, event segmentations, and expressions)
- Set event expiration
- Map your events and customer attributes so they can be recognized by Exponea
You can access the Data Manager by navigating to
Data & Assets >
Data Manager. Here you will find the manager with four tabs for each of the key elements:
Mapping. The below sections discuss their functionality in detail.
You can also watch this video to get a basic understanding of the features in the Data Manager:
These two tabs include all of the imported, tracked or manually created customer attributes and events in your project.
Firstly, you can see a green or red dot next to each attribute. This signifies whether that attribute is already tracked in your data (green) or not yet (red).
There are several actions you can do with each property:
Rename a property
Click on the property's name to rename it. This is not possible for those that are already tracked in your data. If you want to rename such property / event, you will need to delete all associated data from Exponea first.
Define the data type
This affects how Exponea treats that property. When filtering data, for example, the data type will decide what type of operators will be shown by default to match that type. It also affects how the values are shown in the customer profile. Learn more about data types here.
Provide a description of the property
This is highly recommended as this will be displayed as a tooltip for all users when working with the properties in Exponea, as shown in the screenshot below.
Hover over a property with your mouse to reveal the following buttons on the right side:
Show tracked values
Opens a report with the actual values tracked for your customers. This is useful for checking whether your tracking works when setting it up.
Click here to learn how to delete a property when it is already tracked in your data.
Mark as personal data
Click on the "lock" icon to mark that property as personally identifiable information (PII). Click here to learn why.
Move the property
You can drag and drop each property to a different place or even a different group. This is important as it also defines how properties are displayed in the drop-down lists when working in Exponea. See the screenshot below.
The order and grouping of properties in the Data manager reflect how they are displayed in Exponea as showed in the screenshot above. This is very useful as it will speed up your work by showing the most important data where you want it.
There is a button
+ Add group at the bottom. You can then place each property into one group for easier navigation. In the screenshot above, we defined a group called "Basic info" (hidden behind the tooltip), containing the most essential data about our customers, and "Others". You can also hide each group in these views by clicking on it.
Note that some elements such as IDs, consents, aggregates, expressions, etc. are grouped automatically.
Events have an additional level (several events and each can have several attributes), which means that you can reorder and group events as well as reorder and group their attributes within each event. Click on the event to manage its attributes. All settings work in the same way as described above.
You can mark each customer and event property as PII (personally identifiable information) by clicking on the "lock" icon on the right side. We strongly recommend doing so for GDPR compliance. Learn more.
Get access to this feature by migrating to the new pricing model that considers processed events.
To delete an event or customer property that has not been tracked yet, simply click on the "bin" icon next to it. If there already are values tracked for this property, you must delete those values first. if you have admin access and you want to delete events follow these steps:
1. Click on the three-dots button in the top right corner and click "Data deletion".
2. Select what you want to delete. You can choose:
- All customers and their events
- Selected events
- Selected customer properties
3. Click "Delete data"
4. Depending on the size of your database, the deletion process might take a few minutes. Once the user confirms the deletion, the delete job starts in the background. If you chose to delete a whole event regardless of the event attributes and time of the tracking you will see a loading icon next to the property in the data manager while it is being deleted and once it is done, the dot on the left will turn red. After that, you can click on the "bin" icon next to that property to delete it from your data structure.
However, if you only chose to delete events with specific attributes and within a specific timeframe there will be no feedback once the job is completed. Any new events created in the time between the job started and finished should not be impacted so some events matching the filter might remain even after the deletion process.
Reimporting deleted data
If you delete imported data you might not be able to re-import them back because the system could recognize them as duplications.
Deleting event property
Event property can be deleted only after deleting all events of given event type.
For example if you have only a few events with session_start.example_property, in order to delete the example_property, you have to delete all events of given type.
In this case you would need to first delete all session_start events.
By default, any events that are tracked or imported to your project will appear in your data, even if not defined in the Data Manager. If you disable this toggle (persist events of types not listed here), any events tracked or imported to your project that is not defined in the Data Manager will be blocked and ignored. This only applies to the event-level (so if you upload an event that is defined in the Data Manager, but with attributes that are not, these will be added).
This is a paid feature that can be enabled by your CSM.
To access these settings go to the Data Manager, click on the three-dots button in the top right corner and then on
Expiration or on the clock icon on the right from an event name.
Data takes a lot of storage and not all types of events are necessary to keep forever. In order to keep your usage under control, it is possible to set up the automatic expiration of events after a certain period of time. By default,
sesion_end are set to expire after 3 months and
page_visit after 30 days. Other events are kept forever unless you change the setting.
You can define the correct data type for each attribute by clicking on the data type field. The data type affects how Exponea treats those values. When filtering data, for example, the data type will decide what type of operators will be shown by default to match that type. It also affects how the values are shown in the customer profile.
The following data types are available:
Textual format. We usually define IDs as strings too.
Binary value. Works with values "true" / "false" and "1" / "0".
Date and datetime
See below for full explanation.
List of individual items.
This can also be an array of objects in the following format:
(Only available when importing data)
Although the data types can be changed at any point, be cautious with the list values as these are processed differently when imported under an incorrect data type.
Exponea has 2 types of the date format - one called "Date" and the other one is "Datetime". The only difference is that a "Date" attribute only displays the date in a customer profile, while an attribute defined as "Datetime" also displays hours and minutes. However, this does not have an impact if you filter data and also both types support all formats described below. That means that even if you import date with hours and minutes only as "Date", Exponea will still store the time and you will be fully able to work with it in the filters. Moreover, you can always change the attribute type later.
Combination of dates, times and timezones from above
Custom HTML / CSS
All distinct formats of ISO 8601 timezone designators (optional, only when time is provided)
The Definitions tab allows you to manage and create Aggregates, Running aggregates, Event segmentations, and Expressions.
Guide to Aggregates and running aggregates
Guide to Event segmentations
Guide to Expressions.
The data mapping functionality enables Exponea to understand your custom events structure and customer properties while keeping your own naming standards.
This makes your recommendation engines better and enables automatic campaign attribution and dashboards. It is then also much easier to setup prediction-based campaigns for your project.
The first section allows you to map the basic essential events. For example, for "Add to cart", you should choose the event
cart_update, then click
add an event attribute and from the other dropdown select
add (if you're not following this naming, just use the attributes with the same function).
This option will be displayed once you mapped the purchase event to map additional attributes.
This function allows you to import elements from other projects, such as analyses, campaigns, and definitions.
Data Manager, click on the three-dots button in the top right corner and click
Definition Import & Export.
Click "Import" in the top panel.
Paste your data in the JSON format. The steps below explain how you can get your data in this format.
Click "Start import" and the elements will appear in your project.
This function allows you to export elements from your project, such as analyses, campaigns, and definitions.
Data Manager, click on the three-dots button in the top right corner and click
Definition Import & Export.
Click "Export" in the top panel.
Select which components you would like to export
Now you have two options:
Clone to project will allow you to directly select a project (only for projects where you have access) where you want to copy the elements.
Start export will export the data in the JSON format, which then can be imported to other Exponea project. Simply copy the JSON text that will pop up and then follow the steps above for importing data to your destination project.
For cloned scenario email nodes, email campaigns, or email templates, the email provider is replaced by the default provider configured in the target project. In case the default provider is not configured, the email provider is left unset.
All campaigns are reset to status ‘Draft’ upon cloning. For example, cloning a running campaign will not start the campaign in the target project.
Authentication integrations (in webhooks) and Ads integrations (in ads audiences) used in scenarios are removed and must be added manually after cloning.
Encrypted parts of the webhook, such as secret headers, or username and password in the case of legacy webhooks, are removed and not imported.
- You can store up to 255 customer attributes with the maximum value size of 128Kbits (or 16KBytes) per attribute. After reaching the storage limit any tracking containing new customer attributes will be discarded.
- You can store up to 255 different event types. After reaching the storage limit any tracking containing new event types will be discarded.
- You can store up to 255 different event properties per event type. After reaching the storage limit any tracking containing new event properties will be discarded.
Clone to another project is a function that allows you to “copy paste” your work from one project to another. You can find it in almost all Exponea functions and modules (reports, scenarios, predictions, etc.).
Different projects have different names for both their customer attributes/events and customer properties, which would normally make cloning between projects complicated. This problem is solved by the function
Use data mapping which automatically modifies your data mapping events´ names and customer properties, so it is compatible with another project. It is turned on by default, but you can switch it off to prevent modification of your original definitions.
If you are unable to clone your event (Exponea saying that “Multiple custom events mapped to the same original event”), adjust your data mapping to make sure that different events do not have the same event attributes.
Updated 17 days ago