How to use Batch Built-in data in your push notifications and In-app scenarios?

Discover how to use Batch's native data through simple-to-implement use cases that offer real added value to your CRM strategy.

Thanks to the Batch SDK implemented in your mobile application or website, certain "built-in data" are automatically collected to allow you to target your users based on essential information, or to create automated scenarios.

You can find all the details regarding the native data right here : Targeting on Built-in data

Which built-in data and for what purpose?

With the following built-in data, here are some ideas of use cases that can be implemented easily:

Built-in attributes

Device attributes

Data	Description	Use case example
App version	App version in use	Encourage users to update the app to the latest version
Installation date	Date when the app was installed	Target new users from the past 7 days / 10 days, etc.

Interaction attributes

Data	Description	Use case example
Last visit	The last time the user opened the app	Reactivate your inactive members
Opened message	The user opened the push notification	Retarget your users for a specific campaign
Sent message	The user received the push notification	Retarget your users for a specific campaign
Clicked message	Email only (all clicks, except unsubscribe)

Reachability attributes

Data	Description	Use case example
Has Custom ID	The user is currently logged in to is account	Connection incentive message for users who are not logged in
Push opt-in	The user has agreed to receive push notifications	Communicate with opt-out users (In-app channel)

Built-in events

Data	Description	Use case example
Subscribed to mobile/web push notifications	The user has just agreed to receive push notifications (Mobile or web)	Welcome scenario
New session (for In-app)	The user just opened the application (Except 1rst opening)	Reopt-in scenario (In-app message)

How to build added-value use cases with native data?

A. Welcome Scenario (Push notification)

Automation

The welcome scenario is the first CRM message users receive after installing the application. With Batch, you are able to create an automation trigger scenario that will welcome your users and which will establish a relationship of trust with your customers, as soon as they opt-in to notifications.

You can follow this documentation step by step : How to create your own welcome scenario?

B. Reopt-in scenario (In-app)

Automation

This use case is really helpful to improve your opt-in rate. Turning opt-out users into push subscribers is a powerful lever for engagement and can be implemented in just a few minutes with an in-app message.

You can follow this documentation step by step : How to create a re-optin campaign to improve my opt-in rate?

C. Re-engagement scenario (Push notification)

Automation

When users become inactive, re-engagement notifications help re-establish contact. By reminding users of the app’s value or highlighting relevant content, pushing incentives, this scenario provides a clear reason to return and helps extend user lifetime.

You can follow this documentation step by step : How to create a re-engagement campaign to win back your inactive users?

D. Retargeting on sent or opened message (Push notification)

One-shot / Automation

Retargeting based on whether a message was sent or opened allows to adapt follow-up communication to a real user behaviour. This makes push notifications more relevant and improves overall engagement and conversion rates.

You can follow this documentation step by step : How to retarget users who have received or opened a push notification?

E. Encourage users to update the application (In-app)

Automation

Encouraging users to update their app ensures they benefit from the latest features and improvements. With an In-app message, you can explain the value of updating the app at the right moment and help maintain a high-quality user experience.

You can follow this documentation step by step : How to encourage users to update their application?