Welcome to Cooladata!

CoolaData provides an end-to-end Behavioral Analytics solution that tracks, enriches and stores your events. You can then use the CoolaData web interface to easily generate insights from these events.

 

Getting Started with Behavioral Analytics

Three easy steps will get you started generating user behavior insights on your own:

  1. Plan which events to track
  2. Implement Cooladata
  3. Build your first Dashboard

Within a couple of hours you’ll start getting events in the Dashboard and can query them in the CoolaData interface or database!

 

What Are Behavioral Analytics?

Behavioral analytics observe the user and the user’s behavior over time and show a sequence of events performed by users. This is also called a funnel of events – which is a sequence of specific events that occur in a specific order.

CoolaData is a complete behavioral analytics data analysis platform that connects all your event data from all your data points. It unifies data from a multitude of external and internal sources and inspects it as a single unit, thus facilitating time‑series behavior analysis that yields behavioral insights.

CoolaData provides behavioral analytics widgets and behavior query language (CQL) to make advanced behavioral analysis easy.

How Do Behavioral Analytics Differ from Regular Analytics?

Basic analytics (such as in KPI reports) differ from behavioral analytics in that regular analytics typically display quantitative reports that count data. For example:

  • Count 1 – How many people were leads?
  • Count 2 – How many people received sales calls?
  • Count 3 – How many people made a purchase?

Regular analytics display discrete (distinct) values, meaning that the total quantity of Counts 1, 2 and 3, regardless of their relationship to each other. This means that Count 1 shows the total number of people who were leads, Count 2 shows the total number of people to which home sales calls were made and Count 3 shows the total number of people who made a purchase, regardless of whether they were a lead and regardless of whether a sales call was made to them.

In a Behavioral Analytics report, Count 1 is the same as in the KPI report; however, Count 2 is a subset of Count 1, meaning that it represents the quantity of people who were leads and to whom sales calls were made, and Count 3 is a subset of Count 2, meaning that it represents the people who were leads, to whom sales calls were made and who made a purchase.

Print Friendly, PDF & Email

Step 1 – Plan which events to track

Planning

Try to answer the following questions when planning which events to track:

  1. What are your objectives?
    Think about your business goals and strategies in order to determine the purpose of the data that you want to extract from the events sent to CoolaData. For example, optimizing customer retention, increasing conversions, expanding business leads, growing revenue or enhancing usability.
  2. Which data enables you to achieve these objectives?
    Think about the kind of information that could be sent from your website that would enable you to achieve these business objectives. You can track anything that anyone does in your website and anything that happens at any specific point in time.
  3. Write It Down:
    Each business objective is typically comprised of a series of events that lead up to a target event, such as a purchase. We recommend sending an event for each stage of a user’s journey (funnel) through your website. List the events and the data properties that could be sent to CoolaData at various stages of your users’ experience.

Events

Events represent the path which your users follow through your site.

Examples of typical paths could be:

  • eCommerce: search → view_product_details → add_to_cart → click_checkout → purchase.
  • Gaming: login → start_game → level_up → purchase_bonus_item.
  • Media&Publishing: view_homepage → view_article → click_video → video_completed.

 

Properties

Cooladata supports events with any number of properties, and automatically enriches them with additional properties that are often used.

 

Events by industry

We’ve created a list of recommended events and properties to implement for each industry. See the following links for your industry:

 

 

 

Print Friendly, PDF & Email

Step 2 – Implement Cooladata

Sign up to Cooladata

  1. Go to http://app.cooladata.com.
  2. Click Sign up.
  3. Fill in the form and click Sign up
  4. Wait until you receive an email with a registration link to the email you signed up with, and click the link to log in.

 

Create a Project

To create a new project:

  1. In the top right corner, click the Create your first project button.
  2. Enter the name of the project.
  3. Click CREATE.

With CoolaData, you can put all your data into a single project or you can divide your data up among multiple projects – as you see fit.

Why create multiple projects? 

You control which dashboards, reports and publications users see. However, Admin users can access all the data in any project to which they are allowed access. To control the data that each CoolaData Admin users can access you can create multiple CoolaData projects.

For example, in an ecommerce site, you might have different stores – each belonging to a different company. Therefore, you might only want each company’s Admin user to see the data of their own company. In this case, you should create a project for each company, so that each Admin user can only access their own data in dashboards, publications and using the CoolaData API.

 

Track Events

To start tracking events using the Cooladata trackers:

  1. After creating a project, if the page shown is not already displayed, select Project – Tracking.
  2. Choose the required OS and follow the on-screen instruction.

See more details and implementation options in the Sending Data section.

 

Monitor Incoming Events

CoolaData enables you to monitor incoming events so that you can verify proper integration with your application/website, regardless of the type of Tracker you use to send events to CoolaData.

As each event is received by CoolaData, it is classified as either valid or invalid and is displayed in the Live Events window within approximately five minutes. Valid events undergo additional processing by CoolaData and within an hour or two after being received, may be reclassified as invalid. In order to investigate the reason for invalid events, CoolaData provides a details option in the Live Events window and enables you to query its database for invalid events. See Handling Invalid Events for more information.

The Live Events page is used to monitor your incoming events to CoolaData. Open the page from the main menu Project – Live Events.

Events are shown in near realtime – from the time you send an event it may take up to a minute to appear on this page. The page shows the 500 most recently received events, sorted by the time they were received, with the most recent events appearing first. Click any column title to sort the list.

Each row represents an event. Click a row to see the raw JSON format it was sent in.

You can search the list or specific columns in the list from the top left search box.

The columns displayed in this list can be customized from the top right icon. The list of columns contains all available common properties in the project, as well as the following information:

  • raw_data: displays the original JSON sent (can also be seen by clicking the event).
  • Validity: an events can be valid – will be saved, invalid – will not be saved, or pending – a new event that will be saved if doesn’t conflict with other events in the project schema.
  • invalidComments: invalid events will specify the rejection reason in this column.
  • extraComments: pending events will specify the reason in this column.
Print Friendly, PDF & Email

Step 3 – Build your first dashboard

Create a new dashboard

  1. Open your workspace in the CoolaData Administrator console and select Dashboards 5-3.
  2. Click the Add + button. The following displays:
    GSSC 7
  3. Enter a name for the Dashboard and click Create. The new dashboard is displayed.
  4. To change the dashboard’s name, simply click the name and type over it.3-2

Add reports to the dashboard

  1. From the top right corner click the Add Reports button.
  2. Either choose Saved Reports to add an existing report, or New Report to create a new one. From here you can also add filters and descriptions to the sheet.
  3. To edit a report in a dashboard click the Edit button in the top right corner of the report. Note that you must have edit permission on the report to do this (only the report creator or project admin).
    3-9

 

Events will show up in the Dashboard within an hour or two of being received by CoolaData.

 

Share your Dashboard

The dashboard owner and editors can share a dashboard with anyone who has permission to the same projects. This gives them access to the dashboard and notifies them by email.

  1. In the dashboard, select Share GSSC 23 from the top right corner. The following panel opens:
    GSSC 21
  2. Copy the link and send it to anyone who already has permission to the dashboard to access it directly.
  3. In the Invite people field, select the people with whom to share this dashboard, and assign them View or Edit permissions. Only people who already have permission to the project can be invited to share your dashboard.
    • View: can see the dashboard and change the filter and date range for their own usage.
    • Edit: can make any change to the dashboard.
  4. Users who already have access to the dashboard are listed below – from here you can manage (change/remove) permission of users who already have access to the dashboard.

 

 

You can also

Add sheets

  1. Click on the Add + button to the right of the sheet tabs.
  2. Click on the down arrow to next to the sheet name to Rename, Duplicate or Delete it.

Set the dashboard date range

This timeframe applies to all reports in the dashboard unless the report is set to ignore external date range.

  1. Click the dates at the top right:  GSSC 18
  2. Select a timeframe for the Dashboard.

Set the dashboard filters

These filters apply to all reports in the dashboard unless the report is set to ignore external filters.
See more in Dashboard Filters.

  1. Click the Dashboard Filters 3-12 button at the top right.
  2. Set the desired filters and click apply.

Edit saved dashboards

You can open any dashboard you have permission on.
You can only edit/delete a dashboard if you are its owner, or if you were given editor permission on it.

  1. Open CoolaData and select Dashboards 5-3 – a list of the dashboards to which you have permission is displayed.
  2. Click any row to open the dashboard.
  3. To delete a dashboard click the row options and choose Delete, or from inside the dashboard open the dashboard option and choose Delete.
Print Friendly, PDF & Email

Events by Industry – Media & Publishing

Below you can find a catalog of events and their properties, specially designed to track the behavior of Media & Publishing sites/apps. Tracking those events will cover most of the events that you will need to use for your given industry. You can always change the existing events by changing their properties and add your own events with custom events.

Event: ‘page_load’

Use to collect basic data during page load. This event is the standard Cooladata page_load event. For more information see the Cooladata JS tracker.

PropertyExample ValueDescription
user_id15e7a61137553b-09451a8fc6d1d2-e313761-100200-15e7a611379e2bThe unique ID that identifies the user.
page_urlhttp://go.lightsaber.com/free-demo
The page URL of the viewed page
referring_urlhttp://go.lightsaber.com/The previous page that linked to the current page
page_titleThank You for Downloading Behavioral AnalyticsThe page title
session_duaMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36The directory user agent. Refers to a web browser telling a website information about the browser and operating system.
session_platformWin32The platform the user is operating from (Windows, iOS, Android etc.)
event_namepage_loadThe name of the event
session_ip174.19.217.119The ip from which the call originated
referring_domaingo.lightsaber.comThe domain that referred to the current page

Event: ‘page_load_enrich’

Use this event to enriching data after page load (DOMContentLoaded) as some data can be used to send an event only after the page loaded.

PropertyValue TypeDescription
content_urlhttp://mylightsaberjournal.com/scifi/and-then-all-turned-darkThe URL of the content item.
content_id14785905The unique id of the content item.
tags_listlightsaber, villainsA list of tags relating content item.
publication_datetime9999-12-31 23:59:59The date and time on which the content item was published.
content_nameStar Wars 33: Saber ClashThe name of the content being viewed.
content_items_per_page10How many items per page were presented to the user (INT, 0 if NULL).
content_impression_names[Lightsaber/Legends, The Kyber Saber Crystal Chase, Search for the Kyber Saber, Star Wars 33: Saber Clash]A list of content (articles/videos) items that show up in the content item the user is currently viewing.
content_impression_ids[125987, 125991, 123532, 123021]A list of the unique IDs of content (articles/videos) items the user is currently viewing.
content_categoryMarvelThe outcome of the action the user performed.
content_sub_categoryMarvel Star WarsThe subcategory of the content.
content_descriptionThe plot of the Saber Clash are being unraveled in this hair raising story. The description of the content.
ad_blockerfalesIs the browser using an active ad blocker?
comments_count754The number of comment/talkbacks this content item had.

Event: ‘user_search’

Use to capture a search action by the user.

PropertyExample ValueDescription
search_results[Lightsaber/Legends, The Kyber Saber Crystal Chase, Search for the Kyber Saber, Star Wars 33: Saber Clash]A list of content (articles/videos) that match the user's search.
Search_result_content_id[125987, 125991, 123532, 123021]A list of the unique IDs of each content item.
search_results_count4The number of search results the query returned.
search_termlightsaberThe search term used by the user for the search.
current_page_number1The number of results page (INT, 1 if NULL).
content_items_per_page10How many items per page were presented to the user (INT, 0 if NULL).

Event: ‘log_in’

Use to capture the user’s log-in data.

PropertyValue TypeDescription
user_alternative_id6c84fb90-12c4-11e1-840d-7b25c5ee775aThe unique ID that identifies the user on the platform.
user_emailjake.land@jakeland.ioThe email used by the user to log into the system
login_successtrueWas the log-in successful?
login_errorEmail address invalid, please try againAny error that is presented to the user during the log-in process

Event: ‘click_iframe’

Use to capture the user’s click on an iframe. iframes are often used to house ads or different kinds of 3rd party widgets.

PropertyValue TypeDescription
content_urlhttp://mylightsaberjournal.com/scifiThe URL of the content item, in which the iframe is located.
content_id14785905The unique id of the content item (e.g. article page) where the iframe is located.
content_nameStar Wars 33: Saber ClashThe name of the content being viewed.
tags_listlightsaber, villainsA list of tags related to the content item.
publication_datetime9999-12-31 23:59:59The date and time on which the content item was published.
content_items_per_page10How many items per page were presented to the user (INT, 0 if NULL).
content_categoryMarvelThe outcome of the action the user performed.
content_sub_categoryMarvel Star WarsThe subcategory of the content.
ontent_descriptionThe plot of the Saber Clash are being unraveled in this hair raising story.The description of the content.
comments_count754The number of comment/talkbacks this content item had.
iframe_urlhttp://myfakeadlink.comThe iframe's underlying URL.
iframe_height200The height of the iframe in pixels.
iframe_width300The width of the iframe in pixels.
iframe_position_top250The distance of the iframe topside from the top of the page.
iframe_position_left30The distance of the iframe topside from the left of the page.

Event: ‘article_completion_rate’

Use to capture how far the user got in going through the content. This event can measure video or text content.

PropertyValue TypeDescription
content_urlhttp://mylightsaberjournal.com/scifi/taking-fire The URL of the content item.
content_id14785905The unique id of the content item.
tags_listlightsaber, villainsA list of tags relating content item.
publication_datetime9999-12-31 23:59:59The date and time on which the content item was published.
content_nameStar Wars 33: Saber ClashThe name of the content being viewed.
content_items_per_page10How many items per page were presented to the user (INT, 0 if NULL).
content_categoryMarvelThe category of the content.
content_sub_categoryMarvel Star WarsThe subcategory of the content.
content_descriptionThe plot of the Saber Clash are being unraveled in this hair raising story. The description of the content.
content_size1500The content size can be measured using different values: the physical size of screen pixels, the number of words or the length of the video.
completion_rate30The amount of content the user went through. This is the portion of the article being scrolled in the page. The measurement should be in percentage.
comments_count754The number of comment/talkbacks this content item had.

Event: ‘video_completion_rate’

Use to capture how far the user got in going through the content. This event can measure video or text content.

PropertyValue TypeDescription
content_urlhttp://mylightsaberjournal.com/scifi/and-then-all-turned-darkThe URL of the content item, in which the video is located.
content_id14785916The unique id of the content item.
tags_listlightsaber, villainsA list of tags relating content item.
publication_datetime9999-12-31 23:59:59 The date and time on which the content item was published.
content_nameThe death star chroniclesThe name of the content being viewed.
content_items_per_page10How many items per page were presented to the user (INT, 0 if NULL).
content_categoryDisneyThe category of the content.
content_sub_categoryDisney sci-fiThe subcategory of the content.
content_descriptionThe rise and fall of the darkest star in the galaxy.The description of the content.
content_viewing_time2:30The length of time the user viewed the video.
completion_rate50The amount of content the user went through. This is the amount of time spent viewing a video. The measurement should be in percentage.
content_size5:00The total length of the video.
content_quality4KThe video quality the video was viewed in.
content_height340 The embed height size of the video player.
content_width560The embed width size of the video player.
comments_count115 The number of comment/talkbacks this content item had.

Event: ‘video_action’

Use to capture changes the user is performing on the video player. This could include, among others, volume change, screen size change etc..

PropertyValue TypeDescription
content_urlhttp://mylightsaberjournal.com/scifiThe URL of the content item, in which the video action was performed.
content_id14785905The unique id of the content item.
tags_listlightsaber, villainsA list of tags relating content item.
publication_datetime9999-12-31 23:59:59The date and time on which the content item was published.
content_nameStar Wars 33: Saber ClashThe name of the content being viewed.
content_items_per_page10How many items per page were presented to the user (INT, 0 if NULL).
content_categoryMarvelThe category of the content.
content_sub_categoryMarvel Star WarsThe subcategory of the content.
content_descriptionThe plot of the Saber Clash are being unraveled in this hair raising story.The description of the content.
action_typevolumeDescribe the video action the user performed.
action_descriptionThe user can change the volume of the video.Describe the video action the user performed in more detail (if needed).
action_value100%The outcome of the action the user performed.
comments_count115The number of comment/talkbacks this content item had.

Event: ‘view_later_add’

Use to capture the action of a user adding an article/video to the platform’s favorites.

PropertyValue TypeDescription
content_urlhttp://mylightsaberjournal.com/scifi/and-then-all-turned-darkThe URL of the content item.
content_id14785905The unique id of the content item.
tags_listlightsaber, villainsA list of tags relating content item.
publication_datetime9999-12-31 23:59:59The date and time on which the content item was published.
content_nameStar Wars 33: Saber ClashThe name of the content being viewed.
content_items_per_page10How many additional items per page were presented to the user (INT, 0 if NULL).
content_categoryMarvelThe outcome of the action the user performed.
content_sub_categoryMarvel Star WarsThe subcategory of the content.
content_descriptionThe plot of the Saber Clash are being unraveled in this hair raising story. The description of the content.
comments_count754The number of comment/talkbacks this content item had.

Event: ‘view_later_remove’

Use to capture the action of a user removing an article/video from the platform’s favorites.

PropertyValue TypeDescription
content_urlhttp://mylightsaberjournal.com/scifi/and-then-all-turned-darkThe URL of the content item.
content_id14785905The unique id of the content item.
tags_listlightsaber, villainsA list of tags relating content item.
publication_datetime9999-12-31 23:59:59The date and time on which the content item was published.
content_nameStar Wars 33: Saber ClashThe name of the content being viewed.
content_items_per_page10How many items per page were presented to the user (INT, 0 if NULL).
content_categoryMarvelThe outcome of the action the user performed.
content_sub_categoryMarvel Star WarsThe subcategory of the content.
content_descriptionThe plot of the Saber Clash are being unraveled in this hair raising story. The description of the content.
comments_count754The number of comment/talkbacks this content item had.

Event: ‘registration’

Use to capture the action of a user registering/subscribing to your platform.

PropertyValue TypeDescription
street_nameMain St.The street name of the registering user.
house_number35The house number of the registering user.
postal_code94101The postal code of the registering user.
citySan FranciscoThe city of the registering user.
country USAThe country of the registering user.
stateCAThe state of the registering user (if applicable).
phone_number(415) 765-77241The phone number of the registering user
first_nameJakeThe first name of the registering user
last_nameLandThe last name of the registering user
user_emailjake.land@jakeland.ioregistering user's email address.
notification_optintrueDid the registering user opted-in for shipment/news notifications?
error_messageStreet name is missingWhat error messages were triggered while filling up the form.

Event: ‘newsletter_opt-in’

Use to capture the action of a user filling up a newsletter form.

PropertyValue TypeDescription
content_urlhttp://mylightsaberjournal.com/scifi/and-then-all-turned-darkThe URL of the content item, in which the newsletter is located.
content_id14785905The unique id of the content item in which the newsletter is located.
tags_listlightsaber, villainsA list of tags related to the content item.
publication_datetime9999-12-31 23:59:59The date and time on which the content item was published.
content_nameStar Wars 33: Saber ClashThe name of the content being viewed.
content_items_per_page10How many items per page were presented to the user (INT, 0 if NULL).
content_categoryMarvelThe outcome of the action the user performed.
content_sub_categoryMarvel Star WarsThe subcategory of the content.
content_descriptionThe plot of the Saber Clash are being unraveled in this hair raising story. The description of the content.
comments_count754The number of comment/talkbacks this content item had.
user_emailjake.land@jakeland.ioRecipient's email address.
email_errorEmail address is incorrect, please check.The response the user gets in case of issues with the email.

Event: ‘content_item_impression’

Use to capture the action of a user being exposed to multiple content items on a page, for example content items inside a content category.

PropertyValue TypeDescription
publication_datetime9999-12-31 23:59:59The date and time on which the content item was published.
content_id14785905The unique id of the content item.
content_nameStar Wars 33: Saber ClashThe name of the content item being viewed.
content_descriptionThe plot of the Saber Clash are being unraveled in this hair raising story. The description of the content item.
content_categoryMarvelThe category of the content item.
content_sub_categoryMarvel Star WarsThe subcategory of the content item.
contents_per_page20The total number of items on content item.
content_position5The order position of the content item. This is the position of the item when counting the order of content items from the top of the page.
content_impression_names[Lightsaber/Legends, The Kyber Saber Crystal Chase, Search for the Kyber Saber, Star Wars 33: Saber Clash]A list of content (articles/videos) items that show up in the content item the user is currently viewing.
content_impression_ids[125987, 125991, 123532, 123021]A list of the unique IDs of content (articles/videos) items the user is currently viewing.

Event: ‘click_share’

Use to capture the action of a user clicking a social link.

PropertyValue TypeDescription
content_urlhttp://mylightsaberjournal.com/scifi/and-then-all-turned-darkThe URL of the content item, in which the social/share button is located.
content_id14785905The unique id of the content item where the social/share URL was clicked.
tags_listlightsaber, villainsA list of tags relating content item.
publication_datetime9999-12-31 23:59:59The date and time on which the content item was published.
content_nameThe death star chroniclesThe name of the content being viewed.
content_items_per_page10 How many items per page were presented to the user (INT, 0 if NULL).
content_categoryDisneyThe category of the content.
content_sub_categoryDisney sci-fiThe subcategory of the content.
content_descriptionThe rise and fall of the darkest star in the galaxy.The description of the content.
social_network_nameTwitterThe name of the social network.
social_network_urlhttps://twitter.com/villainit?lang=enThe URL of the social network
comments_count754The number of comment/talkbacks this content item had.

Event: ‘profile_page’

Use to capture actions related to the profile section of the user.

PropertyValue TypeDescription
display_nameVillainMonger The nickname the user is known by on the platform.
tags_listlightsaber, villains A list of tags relating to the user's interests. In some cases users will be adding content to the platform or having conversations with other users so those tags can also originate from this kind of interaction.
created_content[How to trace a villain, How to capture a villain]A list of content items created by the user.
visited_content[Old Sith Wars, Mandalorian Wars]A list of content items visited by the user.
profile_impressions720How many times this user profile was viewed.
profile_reputation321Reputation points the user earned.
Print Friendly, PDF & Email