In-App messages are interstitials or banners displayed while the user is browsing within the app.

 The In-App message is an excellent way to communicate with your mobile users whether they do activate or not push notifications. Nevertheless, if you want to catch the eye of your users, you need to create an impactful message for specific information (e.g. special offers, update reminders, etc).

All of the information provided below in this article are recommendations, adapted to most devices, but the format can change from one screen ratio to another.

Therefore, you should always test your In-App message on your own devices to verify the real-time display, before running the campaign.

Fullscreen

The fullscreen format must be used when you want to ahead important messages, like big updates or exceptional discounts. Your message must be clear and impactful. 

We strongly recommend that you use: 

  1. Title: 15-35 characters.

  2. Body: 110-200 characters.

  3. CTA: Up to 18 characters or simple action words (e.g: visit now, later, sell it now).

The Banner will allow you to communicate with your users in the app, whether they are opt-in or opt-out to push notifications. The banner format is more discreet and less intrusive unlike the fullscreen format, which allows you to manage all cases where you want to bring the fore secondary features (ex: share app, update reminder, etc.).

We strongly recommend that you use: 

  1. Title: 10-25 characters.

  2. Body: 40-70 characters.

  3. CTA: Up to 18 characters or simple action words (e.g: visit now, later, sell it now).

Modal

The modal format is a good alternative if you need to show an important message to your users, without interrupting them with a full-screen In-App message. Batch allows you to fully personalize your modal with several CTAs, an image, and an auto-close timer.

We strongly recommend that you use:

  1. Title: 10-25 characters.

  2. Body: 40-70 characters.

  3. CTA: Up to 18 characters or simple action words (e.g: visit now, later, sell it now).

Did this answer your question?