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

Think about the following 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 by Industry

Events

Events represent the path which your users follow through your site. Examples of typical paths could be:

  • Gaming: Login → start_game → level_up → purchase_bonus_item.
  • Content: view_homepage → view_article → click_video → video_completed.
  • E-Commerce: search → view_product_details → add_to_cart → click_checkout → purchase.

Properties

Cooladata supports events with any number of properties, and automatically adds properties to each event that you send.

Below you can find a collection of events and their properties specially designed to track the actions eCommerce customers take during their shopping journey. Tracking them will cover most of the events that you will need to use for your given industry.

HTML/JavaScript

Ecommerce

Event: ‘page_load_enrich’

Use to enrich the page_load data in the cart, checkout and thank you pages.

PropertyExample ValueDescription
user_alternative_id6c84fb90-12c4-11e1-840d-7b25c5ee775aThe ID used by the user on the eCommerce platform
item_nameLight saberThe name of the product in the catalog
item_id22529378The unique ID of the product in the catalog
item_categoryToysThe category the product belongs to
item_quantity2The quantity of products (of same type) that were added to the cart
item_discount49.5The discount the product received
item_discount_typeBuy one get oneThe type of discount that was applied to this product
total_discount49.5The total discount for the current purchase
item_catalog_price99Product price before product customization or discount
item_price 49.5Actual product price in catalog
currencyUSDThe currency in which the product was purchased in
number_of_items5The number of purchased item for the current purchase
order_total189The total order amount for the current purchase

Expand for ‘page_load_enrich’ event code 

Event: ‘user_search’

Use to capture a search action by the user.

PropertyExample ValueDescription
search_resultsA list of products that match the user searchThe search results the query returned
search_results_count10The number of search results the query returned
search_term"villains' light sword" The search term used by the user for the search
current_page_number2The number of results page (INT, 1 if NULL)
items_per_page20How many items per page were presented to the user (INT, 0 if NULL)

Expand for ‘user_search’ event code 

Event: ‘log_in’

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

PropertyValue TypeDescription
user_alternative_id6c84fb90-12c4-11e1-840d-7b25c5ee775aThe ID used by the user on the eCommerce platform
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

Expand for ‘log_in’ event code 

Event: ‘add_to_cart’

Use to capture data when the customer adds a product to the cart.

PropertyExample ValueDescription
item_nameLight saberThe name of the product in the catalog
item_id22529378The unique ID of the product in the catalog
item_categoryToysThe category the product belongs to
item_quantity2The quantity of products (of same type) that were added to the cart
item_discount49.5The discount the product received
item_discount_typeBuy one get oneThe type of discount that was applied to this product
item_catalog_price99Product price before product customization or discount
item_price 49.5Actual product price in catalog
currencyUSDThe currency in which the product was purchased in
item_genderUnisexThe gender the product is meant for (clothing & jewelry specific)
item_colorSilverThe color/colors of the product
item_stylecrossguard Any styles related to the product
item_descriptionThe perfect villain gift: the crossguard lightsaberPartial/full description of the product

Expand for ‘add_to_cart’ event code 

Event ‘add_to_wish_list’

Use to capture data when the customer adds a product to the wish list.

PropertyExample ValueDescription
item_nameLight saberThe name of the product in the catalog
item_id22529378The unique ID of the product in the catalog
item_categoryToysThe category the product belongs to
item_quantity2The quantity of products (of same type) that were added to the cart
item_discount49.5The discount the product received
item_discount_typeBuy one get oneThe type of discount that was applied to this product
item_catalog_price99Product price before product customization or discount
item_price 49.5Actual product price in catalog
currencyUSDThe currency in which the product was purchased in
item_genderUnisexThe gender the product is meant for (clothing & jewelry specific)
item_colorSilverThe color/colors of the product
item_styleCrossguard Any styles related to the product
item_descriptionThe perfect villain gift: the crossguard lightsaberPartial/full description of the product

Expand for ‘add_to_wish_list’ event code 

Event: ‘remove_from_wish_list’

Use to capture data when the customer removes a product from the wish list.

PropertyExample ValueDescription
item_nameLight saberThe name of the product in the catalog
item_id22529378The unique ID of the product in the catalog
item_categoryToysThe category the product belongs to
item_quantity2The quantity of products (of same type) that were added to the cart
item_discount49.5The discount the product received
item_discount_typeBuy one get oneThe type of discount that was applied to this product
item_catalog_price99Product price before product customization or discount
item_price 49.5Actual product price in catalog
currencyUSDThe currency in which the product was purchased in
item_genderUnisexThe gender the product is meant for (clothing & jewelry specific)
item_colorSilverThe color/colors of the product
item_styleCrossguard Any styles related to the product
item_descriptionThe perfect villain gift: the crossguard lightsaberPartial/full description of the product

Expand for ‘remove_from_wish_list’ event code 

Event: ‘cart_remove_item’

Use to capture data when the customer removes a product from the cart.

PropertyExample ValueDescription
item_nameLight saberThe name of the product in the catalog
item_id22529378The unique ID of the product in the catalog
item_categoryToysThe category the product belongs to
item_quantity2The quantity of products (of same type) that were added to the cart
item_discount49.5The discount the product received
item_discount_typeBuy one get oneThe type of discount that was applied to this product
item_catalog_price99Before product customization or discount
item_price 49.5Actual product price in catalog
currencyUSDThe currency in which the product was purchased in
order_total189The total order amount for the current purchase

Expand for ‘cart_remove_item’ event code 

Event: ‘checkout_form’

Use to capture data when the customer is submitting the checkout form.

PropertyExample ValueDescription
first_nameJakeThe first name of the recipient
last_nameLandThe last name of the recipient
street_nameMain St.The street name of the recipient
house_number35The house number of the recipient
postal_code94101The postal code of the recipient
citySan FranciscoThe city of the recipient
countryUSAThe country of the recipient
stateCAThe state of the recipient (if applicable)
phone_number(415) 765-77241The phone number of the recipient
shipping_methodUSPS Express MailPreferred shipping method by recipient
user_emailjake.land@jakeland.ioRecipient's email address
notification_optintrueDid the recipient opted-in for shipment/news notifications?

Expand for ‘checkout_form’ event code 

Event: ‘newsletter’

Use to capture data when the customer is submitting the newsletter request.

PropertyExample ValueDescription
user_emailjake.land@jakeland.ioThe user's email address for sending the newsletter
email_errorPlease enter a valid email addressErrors while filling the newsletter form

Expand for ‘newsletter’ event code 

Event ‘impression’

Use to capture data when a product is seen by the customer.

PropertyExample ValueDescription
item_nameLight saberThe name of the product in the catalog
item_id22529378The unique ID of the product in the catalog
item_categoryToysThe category the product belongs to
items_per_page10How many items are shown per single catalog page
item_page_position3Item position on the page
catalog_page_number1The number of page in the catalog the product was shown on

Expand for ‘impression’ event code 

Event ‘click_item’

Use to capture data when a customer clicks a product.

PropertyExample ValueDescription
item_nameLight saberThe name of the product in the catalog
item_id22529378The unique ID of the product in the catalog
item_categoryToysThe category the product belongs to
items_per_page10How many items are shown per single catalog page
item_discount50The discount the product received
item_discount_typeBuy one get oneThe type of discount that was applied to this product
currencyUSDThe currency in which the product was purchased in
item_page_position3Item position on the page
catalog_page_number1The number of page in the catalog the product was shown on

Expand for ‘click_item’ event code 

Event ‘click_social’

Use to capture data when a customer clicks a social link.

PropertyExample ValueDescription
social_network_nameTwitterThe name of the social network
social_network_urlhttps://twitter.com/villainit?lang=enThe URL of the social network

Expand for ‘click_social’ event code 

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