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.

When the message is displayed

• If the app is open when the In-App element is triggered, the message is shown immediately.
• If the app is closed, the message is shown the next time the user opens the app.

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

Select template and set expiration

In Media Source, select an in-app template. The list shows the newest templates first. To change the order, click the sort button above it. The order you pick also applies to the other in-app dropdowns. Set In-app expiration (number of days the message is available).

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.

No message type is preselected. Until you choose one, the element shows a Message type not selected warning. If the element is reached only from an Audience-based entry, Marketing message is shown with a Default badge. Choose Transactional message if the message is a service one.

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.