Jump to: navigation, search

This change has been introduced with the update 11/2012.

For some metrics the date range is reduced to prevent misconfigurations in charts that lead to unpredictable results.

This can be the case for metrics that are created to show unique users (for example "number of users that generate custom events"). As soon as you use an x-axis that is not "date", the date range for those metrics is changed to 1 day.

In order to see data of more than one day, just use the "cumulative sum over"

When you`re testing new configurations for a chart, don`t rely on the data of today. The data of today is transmitted in real time and can change any second. So if you want to watch how results change due to changes in the setup, you should use older data.

The user lifetime is calculated daily accurate for all users that are active today. If your game has lots of loyal users, it can make sense to limit the user lifetime to newer users. You can achieve this by using a "signup date" filter.

If you don't want to send us your events immediately after your users did actions in your game you could also send us the events as bulk packages each hour, day or within similar intervals. Please recognize that you have to switch off the option Always use tracking servers time of conception within your product administration. We also prefer that you send the packages to our special data import servers instead to our standard tracking servers. Our standard tracking servers are optimized and built for receiving huge amount of events in a streaming way, but if you send us your events just once a day we recommend to use the host "dataimport.tracker.honeytracks.com", this host is optimized to receive huge packages instead of small pieces.

We recommend using Chrome for optimal performance. We also support Firefox and Internet Explorer.

  • We recommend not putting more than 10 charts on one page. More charts can slow down the page load.
  • We recommend putting not more than 5 Custom Events metrics or 10 standard metrics into one chart. More metrics can slow the chart loading times down.

If you want to make a clear cut between your games versions (e.g. closed beta to open beta, beta to release version), we recommend creating a new product as soon as a new version starts. You can do this in the product administration (Settings-> Products). You just need to switch the API keys in the events and all your new data is sent to the new product.

The first (by Timestamp) Identifier we receive for a user is saved and not overwritten. If you send an identifier in a TrackClick event and a second one in TrackSignup, the one sent in TrackClick will be saved for the user.