Settings

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.

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 support@cooladata.com 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.

\

Update User API

CoolaData provides an API that can be used  to update user information without having to send events especially for this purpose. This can be used for a bulk update of user information, or for ongoing updates.

The update support only existing user scope properties in the project (adding new properties is not supported with this API) and will affect any future events sent for this user.

The API is called using customer_user_id (the actual user id sent in events, not the internal_user_id Cooladata allocated per user). The API will work only for existing users that sent events in the past. Notice that since Cooladata deletes users after a period of inactivity, the user updated might not exist in Cooladata records if the period has past. For more information about the period Cooladata keeps users for please contact support@cooladata.com or contact your CSM directly.

 

API End Point

https://app.cooladata.com/api/v2/projects/{projectId}/users/update

Replace the [project_id] placeholder with your actual Project ID found in the project settings.

Method

POST

Header

ContentType:application/json
Authorization:Token [User_API_Token]

Replace the [User_API_Token] placeholder with your actual user API Token found when clicking on your user in the application.

The request will be permitted only for ADMIN user permissions.

Payload

[
{
 "customer_user_id" : "<user_id>",
  "properties":{
   "user":{
    "<property name>":"<new value>",
    "<property name2>":"<new value>"
   }
  },
  ...
}
]

Sample Payload

[
{
 "customer_user_id" : "458dsf832-4324h3-dsfsf34532-dsf73d",
  "properties":{
   "user":{
    "email":"johng@4x4videos.com",
    "plan_type":"Premium"}
   }
  },
{ "customer_user_id" : "29fh84g7-fg86fg0gh-dsfsf34341-239hf47", 
   "properties":{ 
     "user":{
       "email":"neo.goldman@gmail.com",
       "plan_type":"Free",
       "plan_update_date":"2018-05-23" } }  
}
]

 

Response

  • Success: 200 ok + number of users updated
  • Failure: 400 bad request
    •  No customer user id <id> for project <project id> – this means the user_id you requested to update does not exist (never sent events) or was deleted since the period of user inactivity defined in your project has past.