Reporting Concepts


Data Categories Tracked:

Sessions are defined as:
  • A new user visits your app or site.
  • 30 minutes elapses from the user's last interaction.
  • For web tracking, the user re-enters the site or app from a different source (campaign, referrer, or search engine)
  • An event is an activity performed by a user, like 'App Launch', or 'Signup'. Events are tracked via API calls. Events can track any extra data. For example, a signup event can also pass in the user's name and other info.
    For web tracking, pageviews and page navigation can be tracked.
    Users are visitors to your website or app.
    A person is a known user, which means you have identified the user with the 'setPerson' API call. Generally, a person is known to you when they log in or identify themselves in some other way. People can be tracked across devices, however, users cannot be..

    Tracking records data called 'attributes'. We collect a large number of attributes per session and these can be reported on immediately. Attributes can be either elements or metrics:

    Definitions of attribute types:

    A generic term for either an element or a metric. Attributes are also known as 'fields' or 'properties'. Example attributes are 'sessions' and 'platform'.
    An attribute (generally a string or date) that reports can be grouped on. For example, 'Event Name' or 'Campaign'.
    A numeric attribute that can have summary operations computed on, like totals, averages, etc. For example, 'Average Session Length'.

    Entities and Attributes

    You can see a list of all entities and attributes here.

    Segments and filters are very similar, as they both create a subset of your data on reports. The primary difference is the segments are used for comparing different data sets within a report. Also, a filter applies to the whole report, including all segments. So, you can define a report with 'Mobile' and 'Desktop' segments that both appear on the report. Then, you can create an overall filter that applies to both segments.

    Yes. The tracking scripts for each do not interfere with each other.

    Yes. We automatically track utm_source, utm_campaign, utm_medium, utm_content and utm_term.

    Known users can be tracked across devices if they are known to you, via a login or some other means. Once you know the user, use the 'setPerson' API call. Then, you can view the user's profile for every device they are known on.

    We retain all data for as long as the account is in good standing.

    Yes, and so are session and person data. See our API.

    Yes. On each project, you can create custom attributes on sessions, event and people. In addition, this attributes can be defined to behave like standard attributes, including how they are displayed, totaled, etc. See the 'Setup / Projects' menu item on your account, then find the 'Attributes' button for the project you wish to add the custom attributes.

    Yes. Reports are displayed in the timezone of the account holder. This can be modified at any time.

    We track 22,000 (and growing) separate devices and their manufacturers.