The Telerik Platform product is retired.Learn more

Your First Data

This article will describe how to get your application's very first data into the Analytics dashboard. It will also describe why you may not see the data you are expecting to see.

Seeing your first data

So, you have created a Analytics application. You have logged into your account using the analytics client and you have clicked on the dashboard. But instead of seeing colorful graphs you are being treated to a set of empty boxes, proclaming you have "No data yet":

Seeing "No data yet" in the Analytics Dashboard

What is going on? And what can you do about it?

As you integrate the monitor in your software and start tracking your sessions and features you may find that data is not appearing in your Analytics dashboard as you expected it to. The data has to make its way from your device to the Analytics servers and down to the dashboard, so there are a number of places where you can troubleshoot the missing data.

Let us revisit every single step of how analytics data comes into the dashboard:

The Analytics service at a glance

  1. You create an application and get a unique product key, like b1bd264....be34c
  2. You integrate the monitor into your application, calling Start and Stop
  3. You run your application once
  4. You wait up to five minutes

If you are seeing the "No data yet" message then obviously you have already completed step 1. Congratulations, you are almost there - now let us look at what can go wrong in steps 2-4.

Make sure you are looking at live data

When you look at your Analytics dashboard you will see data from yesterday and earlier by default. This is because the Analytics dashboard shows you aggregated daily data by default and not real-time data as it arrives from your tracked software. For newly created applications you will typically encounter an empty dashboard, even though you have just submitted the first data. In this case you can turn on Live Mode in the Analytics client in order to observe data as it is processed by the Analytics servers. The view mode is toggled below the period selector. If you are seeing the indicator below then you are in live mode:

Viewing data in "Live Mode"

Live Mode will restrict the date range to the last few days but will also include the newly processed data from your application. Note that there are typically a 5 minute delay from data being received by the Analytics servers until it is available in the Analytics client.

Also, the dashboard does not refresh itself automatically. You can manually click the refresh-button or enable autorefresh. Those options are in the upper-right corner in the dashboard:

Dashboard refresh options

In the Analytics Client you can also inspect incoming data sessions in details and see precisely what is coming in, even delving into the specific statistics data that is reported in each session - feature tracking, exceptions, etc. The live report in the left-hand menu will show you that:

Viewing specific live incoming data sessions

Make sure data is not hidden by filtering

You may have applied a global filter that does not match the incoming data. For instance, you may have selected to view only internal sessions or data coming from a specific country. If incoming data does not match that filter then it will not be shown.

Using global filtering for your data

Check the filter and period selector to make sure you are actually asking to see the data you are expecting to see.

Make sure the monitor is used correctly

When the application is created it is assigned a specific type (such as Hybrid, Native, AppBuilder, .Net, Javascript, etc.). If data from a given application is sent to the Analytics servers from a monitor that is of another type, then that data is silently rejected by the servers. For instance, if you try to submit data to a Java application using a .Net monitor, the data is simply not processed.

When you create an Analytics application a unique product key is generated. Make sure that you are actually using this very product key in the application. If data is received by the server for a non-existing product key it will be silently discarded.

Make sure that your application actually calls the Start method on the monitor. Otherwise no data is tracked and no data is sent to the Analytics servers. Please see the article on Monitor Integration for more info.

Finally, for the monitor to be activated and submit data, you need to run your application at least once, and you need to run it on a device or machine that is online (connected to the internet). What happens if you are not online? The gathered statistics are stored locally on the device until you eventually run the application while online. What happens if you kill the application before Stop is called? Then statistics may fail to be submitted, but will be submitted at the next application start-up.

Enable logging

You can enable logging in the monitor. The logger will receive messages from the monitor when it starts and stops, as well as when it has attempted to deliver data to the analytics servers. You will also receive error messages if something happens internally or if something is going wrong.

Logging is turned off by default, but if you are having problems then you should definitely turn it on. The specifics on doing that are described in Logging Monitor Activity

A note on simulators

Specifically for AppBuilder applications: running your application in the device simulator will produce no analytics, because the analytics code is simply not engaged in the simulator. You will only receive analytics data when running your app on a real mobile device.

Make sure there is network connectivity

Make sure that your device can connect to the analytics servers. The communication is using port 80 (or 443 for SSL communication) and will most likely pass through firewalls without problems.

There is one simple way of testing network connectivity from your device to the Analytics servers: Open up a web-browser and go to (or for SSL). If you get a simple text response saying something like "Analytics" then your device can successfully connect to the Analytics servers.

In some environments there is a need to specify a proxy setup. Your browser is probably doing this for you automatically but you may need to setup specific proxy settings to connect to the Analytics servers. For details on doing this, please see the article on Network Traffic.

You may also find it useful to inspect the network traffic using a suitable tool such as Fiddler (Windows) or Charles (MacOSX). For example, if you are on a mobile device then you can setup Fiddler as a network proxy on a regular PC and specify that machine's address as the monitor's proxy address - thid will direct network traffic via Fiddler, allowing you to then inspect it. When you are inspecting network traffic we recommend not turning on SSL in the monitor as that makes the capturing more difficult.

Make sure data is accepted for your account

You may have exceeded the limitations of the account in terms of the amount of data you are allowed to receive. The Analytics servers will reject data from applications that belongs to accounts that have exceeded their data plans. An email warning of this will be sent to the contact person for your account.

By its very nature it is highly unlikely that account restrictions will pose a problem for receiving your very first data.

Contact us

Still reading? Then you have probably exhausted all the options you can do on your own and you are still not receiving data on the analytics dashboard. At this point you should not hesitate in contacting our support team or posting to our analytics forum where we will help you get things up and running.

See Also

Contact us: +1-888-365-2779
Copyright © 2016-2018, Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.