How to interpret differences between third-party analytics and Batch statistics?

Batch and your analytics tools measure user visits to your app in different ways.

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.).

The analysis period in Batch is measured in days using the UTC zone. Make sure this period aligns with the analysis period in your analytics tool.

Direct opens vs. sessions

If you notice more direct opens from a Batch campaign than sessions in your analytics tool, this could be due to several reasons.

Different calculation methods

On Batch's side, each click on a push is counted as a direct open (without grouping push opens within a specific time window). This measurement is precise, as it is directly provided by our SDK. Calculation methods can vary across different tools. Keep in mind that:

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

  • Your analytics tool may group multiple visits within a specific time frame into a single session (e.g., 'Google Analytics groups hits received within 30 minutes 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:

  • The user has not provided consent for session tracking in the app (e.g., via your Consent Management Platform).

  • The notification contains a deep link that opens in the device's web browser instead of the app.

Daily Active Users, Installations, and Starts

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

  • A "Start" as shown on Batch's 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, see our Guide on how to integrate Batch into your CMP), 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 do not include unsupported platforms (e.g., Internet Explorer), but your analytics tool is likely to include them.

In any case, we recommend you double-check your analytics tool's integration.

Integrate a "ready-to-go" event dispatcher

To track your campaigns effectively, you should implement an event dispatcher (Guides: iOS/Android). This enables the automatic dispatching of push opens and in-app displays from Batch's SDK to your analytics tool.

Read these guides for more details:

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

Last updated

Was this helpful?