Live Events

The Live Events page displays the full details of the last 1,001 events received in your project. It is specifically useful for monitoring incoming data and identifying invalid events or properties, conflicts in data schema, and other unexpected data issues.

Each row describes a single event.
Columns include all Common Properties collected by Cooladata, and special columns:

  • validation: valid/invalid/pending (a new event that will be added to the schema if valid)
  • invalidComments: will specify the reason if the event is invalid.
  • extraComments: will specify any changes made to the event data (such as invalid properties removed).
    For more information see Handling Invalid Events.
  • raw_data: shows the full events JSON string.



The page provides the following functions:

  • Search: click Search to filter the list to only show events which contain specific values. The search applies to all columns by default, but can be narrowed down to only apply to a specific column.
  • Refresh: click Refresh at the top right to update the list with the latest 101 events.
  • Select columns: click Select columns at the top right to choose which columns to display in the list.
  • See raw event data: click any row to see the original event JSON as received by Cooladata.


Print Friendly, PDF & Email


Managing user permissions

You can manage user permission to your project from the Project – Users page.

Add a user to the project

  1. Click the + (Add) button.
  2. Enter the user’s email and permission level. Note that “Viewer” permission can only be given to users who do not have any other type of permission yet, and vice versa.
  3. Click Save.
  4. New users will receive an email invitation to complete sign up – will show “Pending invitation” until done. You can resend the invitation by editing the user.
  5. Existing users’ permission will be updated on their next visit (or after page reload).

Modify a user permission level

  1. Click the user in the users list.
  2. Choose the new permission level. Note that “Viewer” permission can only be given to users who do not have any other type of permission yet, and vice versa.
  3. Click Update. The permission will be update on the next visit of the user (or after page reload).

See the list of dashboards accessible by a user

  • Locate the user in the users list.
  • Click the options icon on the right side of the row (ellipses) and choose “Dashboards”.

Remove a user from the project

  1. Locate the user in the users list.
  2. Click the options icon on the right side of the row (ellipses) and choose “Delete”.
  3. Confirm the deletion. The user will lose permission immediately. Note that you cannot delete the actual user, but only remove him from the project. For more information contact your CSM.


Project permission levels

Users can have one of the following levels of permission:

  • Admin:
    • Can make any changes to the Project, including changing Permissions.
    • Can see, create, duplicate, edit and delete all the Reports in the project.
    • Can create new Dashboards.
    • Can only access Dashboards if shared with him.
    • Can only edit Dashboards if given Edit permission on the dashboard.
  • User:
    • Can see all the Reports in the project.
    • Can create/duplicate Reports.
    • Can only edit/delete his own Reports.
    • Can see the project Event Sources, Live Events (for implementation purposes).
    • Can see the project Schema.
    • Can see, create and duplicate Segments.
    • Can only edit/delete his own Segments.
    • Can’t see/edit any other project page/setting.
  • Viewer: 
    • Only has access to specific Dashboards that have been shared with him.
    • Can change dashboard Date Range.
    • Can see dashboard Filter Report and select values if the filter is set to allow it.
    • Can’t see dashboard Global filters in the top bar or in the reports preview – this allows you to filter the dashboard by any sensitive information, hidden from viewers.
    • Can’t see the project Schema
    • Can’t see/create Reports not in dashboard.
    • Can’t edit any Reports.
    • Can’t access any Project page (menu is hidden).

Note on viewer permission:

A user can only have viewer permission if he does not have any other permission level on any project, and vice versa. To give viewer permission to a user that has already signed up, either use a different email or remove his permission from all other project first. Contact your CSM for additional assistance.


Full permissions list

ReportsAdd newYesYesNo
ReportsEditYesOnly ownNo
ReportsDeleteYesOnly ownNo
DashboardsAdd newYesYesNo
DashboardsDuplicateOnly own/sharedOnly own/sharedNo
DashboardsViewOnly own/sharedOnly own/sharedOnly shared
DashboardsEditOnly own/shared as "Edit"Only own/shared as "Edit"No
DashboardsDeleteOnly own/shared as "Edit"Only own/shared as "Edit"No
Dashboards permissionsShare/edit/delete permissionsOnly own/shared as "Edit"Only own/shared as "Edit"No
Dashboards date rangeViewYes, saved only for the user/when first sharedYes, saved only for the user/when first sharedNo
Dashboards date rangeEditYes, saved only for the user/when first sharedYes, saved only for the user/when first sharedNo
Dashboards filtersViewYes, saved only for the user/when first sharedYes, saved only for the user/when first sharedNo
Dashboards filtersEditYes, saved only for the user/when first sharedYes, saved only for the user/when first sharedNo
Dashboards filter reportViewYesYesYes
Dashboards filter reportEdit valuesOnly own/shared as "Edit" dashboards, or if filter is set to allow itOnly own/shared as "Edit" dashboards, or if filter is set to allow itNo
Dashboards filter reportEdit conditionsOnly own/shared as "Edit" dashboardsOnly own/shared as "Edit" dashboardsNo
Active projectViewYesYesNo
Active projectEditYesYesNo
Active projectAdd newYesYesNo
SchemaView YesYesNo
Event SourcesView YesYesNo
IntegrationsAdd newYesNoNo
Linked Data SourcesAdd newYesNoNo
Linked Data SourcesViewYesNoNo
Linked Data SourcesEditYesNoNo
Linked Data SourcesRunYesNoNo
Linked Data SourcesDeleteYesNoNo
SegmentsAdd newYesYesNo
SegmentsViewYesOnly ownNo
SegmentsRunYesOnly ownNo
SegmentsDeleteYesOnly ownNo
Aggregation TablesAdd newYesNoNo
Aggregation TablesViewYesNoNo
Aggregation TablesEditYesNoNo
Aggregation TablesRunYesNoNo
Aggregation TablesDeleteYesNoNo
AlertsAdd newYesNoNo
PublicationsAdd newYesOnly "Send now" from reportsNo
PublicationsDeleteYesOnly unsubscribe himselfOnly unsubscribe himself
JobsAdd newYesNoNo
Live EventsAdd newYesNoNo
Live EventsViewYesNoNo
Live EventsEditYesNoNo
Live EventsRunYesNoNo
Live EventsDeleteYesNoNo
EventsAdd newYesNoNo
PropertiesAdd newYesNoNo
UsersAdd newYesNoNo
Print Friendly, PDF & Email


The project settings page allows you to modify the following details:

Project Name

Rename the project. This does not effect your data or any of your reports or dashboards.

Session Timeout

Session lengths in CoolaData end after dead time, or after an event reaches the session configuration max time (the default is 30 minutes). Consult our Customer Success team to change the session length configuration. For more, read our blog post about sessionization.

Client Timestamp Override

Event timestamps is derived from the client device, or forced to take the project timestamp. It can be configured in the CoolaData admin tool.

Data Scheme Configuration

When updating your meta data, any project in CoolaData can be set to one of the following three modes:

  • Locked – Lock the mapping. Do not store new properties and event names. Default value. New events are marked as invalid and are not stored. New properties are removed from events, i.e. the event is valid and saved, but does not save the new properties.
  • Self-Learned – Automatically add new event names and properties to the mapping and store values. All new events and properties are stored. If any of the properties in the event is invalid, the entire event will be marked invalid and will not be stored. Also pay attention that the process of recognizing and registering new entries to the schema can take up to 5 minutes; new entries that will be received in this period might be marked invalid until the schema is updated.

Print Friendly, PDF & Email

Anonymizing Personal Data

AS part of the GDPR efforts, Cooladata now enables you to anonymize personal data in your project.  Since you control what data you send to Cooladata and what is stored, you are responsible for defining what is personal information and what is not.

This feature will allow you to hash properties marked as personal user information.  

Notice that we automatically collect IPs so if you need the IPs we have collected to be hashed before they are stored you are responsible to use this functionality to set this up.  Hashing IP’s will not affect the geolocation enrichment we provide out-of-the box.

Keep in mind that this feature will only hash future data being sent to Cooladata and will not update historical data.

Marking Properties as Personal Information

  1. In Cooladata, go to the project menu -> properties – to see the project’s properties list
  2. Search for the wanted property and click on it
  3. In the Edit Property side bar mark the “anonymize data” to mark this property as data that should be hashed:

Notice that STRING type properties will be hashed using MD5 so the data will remain unique per value, but INTEGER,FLOAT and TIMESTAMP data types will be Nullified.


Setting up a project wide condition for anonymizing data

You can also set up a project-wide condition to define that only data that meets this condition will be hashed. Due to legal issues, this is done offline using a form. Please contact or your CSM to set this up.

Once you set up a condition, all properties with “anonymize data” checked will be hashed once the condition will be true. Even if the property will be marked after setting up the condition.


Print Friendly, PDF & Email