Automatically Enriched Properties

User Level:

We identify the user_id, and then look at everything we know about this user. For every event we collect we look to see whether the user was already active in the past. If he was, we assign the same user_internal_id to that user, connecting all his data to the same user_id.

Any user scope property you previously sent is added to the events we received on the user, such as: email, age, address, etc.

Additional information we learned during the last events is added to the user profile to be used in the next events this user will perform.

Session and Event Level:

All the session data we received earlier to that session is added to the event. For example, when we identify a utm_source or a url_referrer parameter in the first event of the session we will copy this information (property) for all the following events during that same session (or until a new value for this property is received). The same is done for all the session scope properties you defined.

• Geo location: from the IP of the event we add the country, city, state and region for any event we receive.
• Device: based on the "device user agent" we add the device type, operating system, browser and other device properties.
• URL: based on the URL of the event, we add the UTM tags, URL referrer, and traffic_source properties.
• is_new: on the first session the user ever did we mark all the events in the session as new (is_new=1). You can use this to distinguish new from returning users.
• event_duration: we add the time (in milliseconds) it took the user to perform each event to the event. This is done by calculating the time that passed from the current event to the following one performed by the same user. Thus, the duration of the last event of every session is always zero. This enables you to see where users stall, or what phases in their path are carried quickly.
• session_duration: the total time passed from the first event in the session to the last. We calculate this when the session is completed (30 mins of inactivity, configurable per project), to enable the analyst to easily understand session durations and the session duration distribution.
• session_length: the number of events the user has performed during the session. We add this number to the session to enable the analyst to see how many events are performed during a session, for example to easily identify extremely short 'bounce' sessions.

Full common Property list:

Manually Enriched Properties

There are additional properties that can be enriched by the server, on the event level, but will need your action. Since not all potentially enrichable properties are relevant to every user, we've built a mechanism that lets you decide specifically which properties you want to have enriched in addition to the Common Properties. The enrichment of those properties is divided into two groups:

• Enrichment based on the event triggering device's IP.
• Enrichment based on the event triggering device.

In order to use those properties you should:

1. Select a property from the list below.
2. Copy its name and add to it the prefix of the relevant group. The prefixes are:
   1. coola_enrich_ip_
   2. coola_enrich_dua_
3. Example: if you are interested in having a property that checks if a visitor to my site is a robot you should use the following phrase:
   1. Prefix: coola_enrich_dua_
   2. Property: isRobot
   3. And put them together like so: coola_enrich_dua_isRobot
4. When you have your enrichment phrase create a Property with that enrichment phrase. Click → Click "Properties":

   

   1. Add new property
   2. Add the name: coola_enrich_dua_isrobot
   3. Add the source: coola_enrich_dua_isRobot
   4. Datatype should be STRING
   5. The Scope should be EVENT
5. Save the new property.

From now on, this property will be used to enrich incoming events (if applicable).

IP Enrichment

Below you can find all the properties of which enrichment is based on the event triggering device's IP. It should be used with the prefix and the property name as so: coola_enrich_ip_<IP_PROPERTY>

If you need more details on the enrichment, based on the device's IP, please have a look here.

DUA Enrichment

Below you can find all the properties of which enrichment is based on the event triggering device. It should be used with the prefix and the property name as so: coola_enrich_dua_<DUA_PROPERTY>

If you need more details on the enrichment, based on the device's User Agent, please have a look here.