On the Data > Data Overview page, you will find the following:
- Account Insights
- Sessions per month
- Account Usage
- Events (last 7 days)
- Fields
Account Insights
In the Account Insights you will find Total Profiles and Matched Profiles. With these numbers you can calculate the match rate.
The match rate is a percentage of the number of email addresses to which website behavior can be linked. This link makes it possible to send trigger based emails, such as abandoned cart emails.
What is a Matched Profile?
In short, this is a profile where we can match the behavior in the browser with a personal identifier. In concrete terms, these identifiers are email address, email hash or userID, the idea is that you send these via a front-end (browser) event, so that we know which events are associated with a known user. This is necessary for many use cases such as shopping cart abandoners, otherwise that user's events appear on an anonymous, unmatched profile.
How can I see the number of matched profiles of an audience?
How do I calculate the match rate?
You can then calculate the match rate as follows: Matched profiles / the number of email addresses in Spotler Activate (the count of the field email). The average matchrate is between 30% and 50%.
The matchrate is automatically increased by events that meet the following conditions:
- Collected through Frontend Tracking (with Backend Tracking there is of course no information about the cookie)
- Contains the data field 'email' (otherwise no email can be linked to the cookie)
The following popular events meet these conditions: EmailOptIn, PrePurchase, Purchase.
Account Usage
Spotler Activate gives you the ability to manage how long data is stored in your account and on your customers' devices. This allows you to ensure that you stay within the maximum data storage capacity of your account and communicate transparently to customers after how much time data will be deleted.
There are events that are rarely used after a certain period, but they do count for the account usage and can cause more costs if you exceed your maximum GB. You can delete selected events after the merchant retention period. In Settings, you can select events you want to delete for known and active profiles as well, after the retention period. This gives you more control over the storage and costs. When this is set, you will see the deleted events after clicking the Deleted data stats link:
Events (last 7 days)
The name of the events in Spotler Activate refer to the triggers of the interactions. In each event it is mentioned when the event was received and which (if any) url triggered the event. The events of a profile can be found in the event data of the profile.
What are the most commonly used events?
Fields
Data fields are stored in Spotler Activate as profile or event fields. Custom fields can be created to store special data. To understand this overview it is important to know the different type of fields and their function: What are profile, product and event fields?
- Field name: the name of the field
- Data type: the type of data of the field
- Count: the number of fields in Spotler Activate
- Profile field: this field is selected if it is a profile field
- URL Parameter: a tick mark if the value is stored based on a parameter in a URL
At the end of all fields you see these possible actions:
- Show archived fields
- Add custom field
- Product custom fields: this will transfer you to Products > Sources.
Archived fields
It is not possible to change the name of data fields or to delete them. Changing and deleting data fields will have provided consequences for the existing data in the Spotler Activate account. You can archive the field, so it won't be visible in your overview. Do this by using the archive button, available for custom fields:
Add custom field
When creating a custom fields, it is possible to change the following settings:
- Name: the name of the field (Note: custom is already set)
- Data type: the type of data in the field, for example Text, Number, Counter, Calculator and Date
- Profile custom field:
- Uncheck this option for the properties of profile fields
- Uncheck this option for the properties of event fields
- Contains PII: check this option when this field contains personal data
- Fetch data from URL parameters: check this option when this value will be fetched from a url instead of from an event