Welcome to CoolaData!

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

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

  1. Plan which events to track
  2. Integrate CoolaData into Your Pages
  3. Monitor Incoming Events
  4. 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.

Enjoy your insights!

Print Friendly

Step 1 – Planning Which Events to Track

Think about the following –

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.

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.

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. For example –

  • In a gaming website the path might include: Login → start_game → level_up → purchase_bonus_item.
  • In a content publishing website, the path might include: view_homepage → view_article → click_video → video_completed.
  • In an eCommerce website, the path might include: search → view_product_details → add_to_cart → click_checkout → purchase.

For simplicity, we suggest that you start with 2 or 3 paths, each with up to 10 events – and each event with up to 10 properties.

CoolaData supports events with any number of events and properties and automatically adds a variety of properties to each event that you send.

GSSC 1To see examples of properties that you might add.

GSSC 1To see a list of the automatically added properties.



Print Friendly

Step 2 – Integrating CoolaData into Your Pages

Step 1– Registering to CoolaData

  1. Go to http://app.cooladata.com.


  1. Click Sign up.


  1. Fill in the form and then register by using your Google+ credentials or by typing in a new password.
  2. Click Sign up and wait until you receive an email with a registration link.
  3. After you confirm the registration link, log in again.

Step 2– Creating a Project

After you login, you see the following:

To create a CoolaData project:

  1. In the dropdown menu in the top right, select the Create New Project option.


  1. Enter the name of the project and leave the other fields with their default values.
  1. Click CREATE.
Awesome! You’ve now got your own CoolaData project!

Step 3– Copying the CoolaData JavaScript Snippet

Here’s how to integrate CoolaData JavaScript into your website.


To start tracking your website using the CoolaData JavaScript snippet:

  1. If the page shown above is not already displayed, then in the CoolaData Administrator console, select Project Project-icon – Tracking and in the dropdown menu in the top right, select the project name or select Create New Project.
  2. Copy/paste the JavaScript tracking snippet on the bottom right of the Project page (shown above) into each page that you want to track before the closing <head> tag. This code already has your CoolaData app key inside.

Step 4– Sending Events

Here’s how to add CoolaData trackers to each page that you want to track so that events are automatically sent to CoolaData.

To send events to CoolaData:

Track events by calling the JavaScript method cooladata.trackEvent and specify the event name and its properties. Event names and property names should not contain any spaces or special characters (except for an underscore) and should not use Reserved Words.

  • Enter the Event‘s Name: The event name should describe the event that occurred, such as Purchase_bonus_item, view_article or joined. This is the only mandatory property.
  • Add Your Own Properties: You may also want to send your own additional properties according to your event plan. For example, when tracking purchases, you may want to send the details of each purchase – cooladata.trackEvent(‘purchase’), {‘product_name’:’Flora-Mini- Dress’,’size’:’4′,’product_ID’:64372′});
  • Automatic Data Type Mapping: You can specify any property you like, along with any value. There is no need for pre-definitions or preparation of any type. Data types are determined automatically the first time the property is received:
    • String – A value with double quotes (such as “any value”) is mapped to String.
    • Float – A numerical value without quotes and with a decimal point (such as ‘5.6’) is mapped as Float.
    • Integer – A numerical value without quotes and without a decimal point (such as 120) is mapped as Integer.
    • Timestamp – To send values that are automatically mapped as a Timestamp property, add these to the schema from the Project Properties page.
Awesome! You can now start live monitoring of the events sent to CoolaData!

Managing User IDs

Please follow one of these two alternatives to manage user IDs:

  • If your website manages unique user IDs, then you can send this unique user ID to CoolaData in the user_alternative_id property of each event of that user.
  • If your website does not manage unique user IDs or a user’s ID is unknown (for example, before the user logged in), then CoolaData has a cookie that automatically identifies the user.


Print Friendly

Step 3 – Monitoring Incoming Events


CoolaData enables you to monitor incoming events so that you can verify proper integration with your application/website. Monitoring is the same 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.

Start Monitoring

To start monitoring incoming events:

  1. Implement one of CoolaData’s many integration options so that you can send events to CoolaData using a Tracker.
  1. Open your workspace in the CoolaData Administrator console and select Project Project-iconLive Events.

Events should start populating this window within a few minutes of being sent.

GSSC 1See more information about the contents of this window.

If no events are displayed in this window within five minutes of sending them, see the troubleshooting instructions.

  1. After proper integration, all the events that you send are shown in the Live Events window with the value Valid in the Validity column. Invalid events have the value Invalid in the Validity column. To see the invalid events that were received by CoolaData, click on the Validity column title to sort the events so that all invalid events are displayed at the top of the window.
  1. Check out the invalid events and the quantity of events received:
    • Event Details Pane: The Event Details Pane in the Live Events window displays the properties of each event, which can typically be seen within approximately five minutes of being sent. See how to display the Event Details.
    • Query Invalid Events: Within an hour or two after events are received by CoolaData, you can query the CoolaData database for the invalid events within the time range that you specify. See how to query invalid events.
    • Query Invalid Events by Reason: Within an hour or two after events are received by CoolaData, you can query the CoolaData database for the invalid events according to the reason they were classified as invalid. See how to query events by reason.
    • Count Events: Within an hour or two after events are received by CoolaData, you can query its database for the events received within a specific time range in order to verify that the number of events received is the same number of events that you sent within the time range that you specify. See how query the quantity of events.
    • Search: In the Live Events window, you can search for any event property.
  1. Resolve the invalid events by ensuring that the CoolaData configuration (settings and expected property data types) is compatible with the events that you are expecting to send, as follows:

GSSC 1Check out the reasons that an event might be invalid and for suggestions of how to resolve each reason.

    • In some cases, you may need to use the CoolaData Administrator console to reconfigure the expected property data types.
    • In some cases, you may need to reconfigure the settings in the CoolaData Administrator console. For example, to configure the allowed date range of events.
    • Once you resolve the issues (as described above), newly received events are handled accordingly. Previously streamed events remain invalid in the CoolaData database.

Print Friendly

Step 4 – Building Your First Dashboard

Step 1 – Creating a New Dashboard

To build your first dashboard:

  1. Open your workspace in the CoolaData Administrator console and select Dashboards .
  2. Click the + button in the top right corner of the page.


  1. Enter a name for the Dashboard and click Create. The new Dashboard is displayed.

Step 2 – Naming Your Sheet / Create More Sheets

To name sheets and create additional sheets:

A Dashboard can contain multiple Sheets, each Sheet appears as a tab that the user can click to see it. The first Sheet is automatically added with the name Sheet 1. To rename a sheet double click its name or select “Rename” from the sheets options.

To add additional Sheets click the “+” icon on the right end of the tabs list.

Step 3 – Creating a New Report – CQL

Each Sheet of the Dashboard can contain one or more Reports. Each report holds a CQL query that determines the data that is retrieved from CoolaData and presented.”

To create a new report:

  1. Click GSSC 11.


  1. Click the + button to display a dropdown menu of report types.
  2. Type in the name of the report in the top left corner of the page.
  3. Select the CoolaData Query Language (CQL) option.


  1. Enter a query written in CQL into the center of the page. For example, the following query counts the number of events received by CoolaData today.

Events are available in the call a data database within an hour or two of being received. Before then, the following message may be displayed when you click Compute: No data in the selected date range.

GSSC 1For more details about CoolaData Query Language (CQL).

  1. To publish this report:
  • Click on the three dots in the top right corner of the page to display a toolbar.



  • Select the Publish option.


  • Fill out the window to specify the recipients to receive this report, the frequency and the time of day.
Awesome – the new report now appears in the Dashboard and is sent to the specified recipients daily.

Step 4 – Creating a Funnel Report

Here’s how to define a report that shows a specific sequence of events performed by a user (also called a funnel).

To create a new Funnel report:

  1. Click GSSC 11.
  2. Click the + button to display a dropdown menu of report types and select Funnel.


  1. In the Did field, in the Select Events field select one of the names of the events already sent to CoolaData. The most frequently occurring events appear at the top of the dropdown menu.
  2. In the Following by field, in the Select Events field, select an event name that occurs after the event selected in the Did field occurred (described above).


  1. A + is then displayed on the right of the Followed by field. You can click on it to add an additional Followed by field so that you can define additional events in the funnel sequence.
  2. Type in the name of the report in the top left corner of the page.
  3. Select a timeframe in the top, right of the page GSSC 18.
  4. Click Apply and then click the Compute button to display an example of the results of this query, as shown below:


  1. Click Save.

Step 5 – Defining the Dashboard Time Period

From the top right corner of the Dashboard, select a timeframe for the entire Dashboard GSSC 18. This timeframe applies to all the reports unless a different timeframe was defined for a specific report.

Step 6 – Sharing Your Dashboard

Here’s how to share your Dashboard with your colleagues.

To share your dashboard:

  1. In the CoolaData Administrator console, select Dashboards GSSC 25 in the left pane, display your dashboard and then select Share GSSC 23 in the top right corner. The following displays:


  1. In the Invite people field, select the people with whom to share this dashboard and assign View or Edit permissions.


  • View: These people can see the dashboard and change the filter and date range.
  • Edit: These people can change the dashboard itself and have the same permissions as you do.

The people that have been invited are listed below.
Only people who already have permission to access your project can be invited to share your dashboard.


Print Friendly