All Collections
Campaign Edition & Analytics
How to interpret the differences between my third-party analytics tools and statistics provided by Batch?
How to interpret the differences between my third-party analytics tools and statistics provided by Batch?

Batch and your analytics tools have different ways of measuring a user visit of your app.

Lucie avatar
Written by Lucie
Updated over a week ago

You may observe discrepancies between Batch direct opens, Daily Active Users, starts, installations and the number of sessions tracked by your third-party analytics tools (AT Internet, Firebase Analytics, Google Analytics, Mixpanel etc.).

Note: The analysis period in Batch is counted in days in the UTC time slot. Ensure that this period corresponds to the analysis period of your analytics tool as well.

Direct opens vs. sessions

If you see more direct opens related to a Batch campaign than sessions in your analytics tool, this may happen for multiple reasons.

Different calculation methods

On Batch side, each clicks on a push counts as a direct open (without grouping push opens that occur over a specific time period). This measure is guaranteed as it is directly provided by our SDK.

The calculation rules may vary from one tool to another. You should keep in mind that:

  • Your analytics tool may count sessions after a minimum delay or a number of interactions on your app/website.

  • Your analytics tool may group many visits on a specific time period into the same session (e.g. "Google Analytics groups hit that are received within 30 minutes of one another into the same session", see GA's documentation).

Timing of the measure

Direct opens are measured by Batch when the user opens the notification, while your analytics tool measures a session when the app has effectively been opened.

After the notification has been clicked, your analytics tool may not count a new session depending on the configuration, for example, if:

  • The user did not provide consent for session tracking in the app (via your Consent Management Platform for instance).

  • The notification contains a deeplink that opens in the web browser of the device instead of the app.

Daily Active Users, Installations and Starts

The number of visits in your analytics tool may be higher than Batch' active users, installations or starts. You should bear in mind that:

  • A "Start" as shown on Batch dashboard corresponds to a start of the Batch SDK.
    If Batch SDK has been disabled by some users (e.g. by not giving their consent), a visit may be counted in your analytics tool but not in Batch.

  • You may also have defined specific rules to allow Batch to start in your app/website (e.g. IP filtering, after a specific action, a minimum delay etc.).

  • For the web, Batch analytics don't include unsupported platforms (e.g. Internet Explorer), but your analytics tool is likely to include them.

πŸ’‘ In any case, we recommend that you double-check the integration of your analytics tool.

Integrate a "ready-to-go" event dispatcher

In order to track your campaigns at best, you should implement an event dispatcher (iOS/Android). It allows you to dispatch push opens and In-App displays from Batch SDK to your analytics tool automatically.

Read these guides for more details:

Note: The analytics displayed in your analytics tool will still be subject to calculation rules that are specific to this tool.

This article belongs to Batch's FAQ. Need more help? Find insightful articles, documentation, case & market studies, guides, and even more in our website's Resources section on and our blog.

Did this answer your question?