In-app

Note

Requirements

For Android apps, the OS versions 6.0 and later are supported.

To show an in-app message in a journey, add the In-App element next to the step that should trigger it. Then choose an in-app page to display.

Click the In-App element to open its settings. Configure the following:

Select template and set expiration

Choose the in-app to show and set how long it stays available:

1. In Media Source, select an in-app template.
2. Set In-app expiration: how many days the message stays available, from 1 to 7. The default is 7 days.

• Template order. The newest templates are at the top of the list. To change the order, click the sort button above the list. The order you pick also applies to the other in-app dropdowns.
• Older elements. If an In-App element was saved with a longer expiration, it opens with 7 days.

Personalize with Liquid

To personalize the in-app with the user’s Tags and the attributes of the event that shows it, write Liquid in the in-app content. Liquid in in-apps is off by default. To enable it for your account, contact your Customer Success Manager or support.

Choose when to show the in-app

In Show in-app, choose when the user sees the message. On next app launch is selected by default.

• On next app launch: when the user reaches the In-App element, the message is shown right away if the app is open. If the app is closed, it is shown the next time the user opens the app.
• On event: the message waits for the event you select and is shown in the same session, right after the user triggers it. Use it to show an in-app message at the moment of an action, for example when the user opens the cart.

Set up the On event mode

To show the in-app message when the user triggers an event:

1. In Show in-app, select On event.
2. Select the event that shows the in-app message.
3. Optional: click Add condition to filter the event by its attributes. For the available operators, see Tag operators by type.
4. Click Save. The element saves only when an event is selected and its conditions are complete.

How On event mode works

In On event mode:

• The in-app message reacts only to events that happen after the user reaches the In-App element.
• If the event doesn’t happen within the In-app expiration period, the in-app message isn’t shown.
• To check which event a running journey waits for, open the In-App element details. The event and its conditions are listed under Shown on event.

Set message type

Choose Marketing message or Transactional message:

• Marketing message: For campaigns and promos. All rules and limits apply. Respects: frequency capping and the silence period. Excludes: the control group users.
• Transactional message: For operational or service messages. Rules and limits don’t apply. Bypasses: frequency capping. Sent to: the control group users.

Until you choose a type, the element shows the Message type not selected warning. A journey that reaches the element from a Trigger-based or API-based entry can’t be launched until you do.

Note

If the element is reached only from an Audience-based entry, Marketing message is shown as selected and marked Default.

Learn more about the difference between marketing and transactional messages.

Set frequency capping

Note

Frequency capping options are available only when Marketing message is selected. When you choose Transactional message, frequency capping doesn’t apply and these options are disabled.

Use Frequency capping to limit how often users receive in-app messages, preventing over-messaging and reducing churn. In the In-App element settings, choose one of the following options:

• Use global frequency capping settings

  Apply the project-wide limits configured in your Global frequency capping settings.

  For example, if the global limit is set to 3 messages in 9 days, additional messages exceeding this limit will be skipped.

• Send messages without global frequency capping

  The user will receive this message even if they’ve exceeded the channel’s message limits. Use this option with caution to avoid over-messaging.

• Use custom frequency capping

  Set a custom message limit for this message. If the user exceeds this custom cap, the message will be skipped, and the user will proceed to the next step.

  Important

  Custom frequency capping replaces global capping for this message, so only the custom limit is checked. The message still counts toward the channel’s global counter, though, so it can use up part of the shared quota for other in-app messages that rely on global capping. Learn more.

  Choose a counting mode for this custom limit: Rolling window or Calendar day.