Welcome, Guest Login

Support Center

EachScape Reporting

Last Updated: Oct 14, 2016 12:35PM EDT
EachScape Reporting


Introduction
EachScape apps can be configured to use 3rd party Analytic systems, such as
EachScape integrates and maintain these 3rd party SDK.
These integrations depends on the plan you subscribe to.
 
  • You can also use EachScape's reporting system.

EachScape Reporting Set Up

To turn on EachScape reporting:
  1. Go to App Edit
  2. Select the 3rd Party Tab
  3. Select 'Reporting' then 'EachScape Reporting'
  4. Select 'Yes'


 

Unless you configure reporting, your app will have none. Read the following sections to determine the relevant information needed to add tracking to your app.
 

Asynchronous Reporting

EachScape reporting has an asynchronous nature, so reports are delayed in arriving at our server.

The logging capabilities of EachScape apps relies on capturing small bits of information as users progress through the app and then intermittently sending that data up for analysis. This results in an asynchronous reporting environment, which gives it some distinct differences from web reporting.

  1. Smartphones on GSM networks such as AT&T and T-Mobile do not have synchronized clocks: people can choose to let the carrier network set the time on the device, but not always. On those devices that are not phones, the setting of the time is up to the whim of the user, always.
     
  2. Because the transmission of activity is asynchronous, it tends to lag behind actual usage. In other words, let's say you go through several actions in the app, they might be buffered up and not sent when the app shuts down. They will be stored until the next session, when they might be sent. Whether the activity is sent during the same session or not will depending on two factors: the logging module in the app waits until it has “enough” to send rather than constantly sending each loggable event one at a time (called “buffering”). Also, if there is no network available, the logged events will be buffered for future transmission.


These two characteristics, potentially inaccurate timestamps and buffered transmission of reports, result in a few scenarios that the reporting system must deal with.

  1. Any reports that arrive and have a timestamp more than 27 days before the current date or 2 days after the current date will be ignored. So if the time is woefully off on the device or there are more than 4 weeks of elapsed time between two sessions of the app, that activity will not appear in the reports.
     
Due to the buffering of reports, they may not be delivered until a subsequent session of the app, and then only if the network connectivity is present. Thus activity for a given day might not arrive on the same day it occurs. This can result in report data for a particular day changing over time: The data for July 1 can start to appear as early as June 29 and will continue to update until July 28. Also, the actual report data is analyzed overnight, so the data received on July 28 will be incorporated into the reporting system on July 29.

‚ÄčLearn more
- Google Analytic
- Adobe Marketing Cloud (Omniture)

Help us improve! Rate this article:

Yes I found this article helpful

Ask a Question   

support@eachscape.com
http://assets1.desk.com/
false
eachscape
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete