1. Home
  2. /What's New
  3. /In-App Automation updates: Server-Side Tags and More

In-App Automation updates: Server-Side Tags and More

In-App Automation just keeps getting better.

Server-side Tag Support

You asked for it, and now you can use tags set from your backend, such as a CRM or POS system, when selecting your target audience.

In the Audience step of the In-App Automation workflow, select the Tags condition, then search for your tags or tag groups.

Use cases

  • Prompt a user who has made a purchase to rate your app.
  • Display a message to users who have a specific tag set from your backend, e.g., likes-cats.
  • Display a message to users who purchased a specific version of your product or who have a specific feature enabled.
  • Display an exclusive message to users who have reached a VIP status.

New Feature: Missed Message Behavior

In-app messages are stored on a device and displayed when certain conditions are met. Now you can specify what happens when audience conditions are not fully met:

  • Cancel: The message cannot be displayed again on the device, even if the message is edited.
  • Ignore: The message will not count toward the display limit set in Repeat this message, and the waiting period will not apply. The trigger event must occur again before the message is eligible for redisplay.
  • Increment: The message will count toward the display limit set in Repeat this message, and the waiting period will apply. The trigger event must occur again before the message is eligible for redisplay.

For instance, you could display a message on devices that have a particular tag after the app opened a certain number of times. With Missed Behavior set to Ignore, if a user completes the display condition (a certain number of app opens) but they don’t meet the audience condition (the specified tag is not yet on the device), the message is eligible for display again after the next time the message display is triggered.

Missed Behavior can also be set on a per-message basis.

Custom HTML Updates

Custom HTML messages now:

  • Default to the modal style rather than fullscreen. You also have the option to override that setting, making them appear as fullscreen on devices with small screens, e.g., mobile phones.
  • Have a border radius setting.

Default Settings Changes

We updated the Settings menu page where you configure the default settings for your in-app automation messages’ appearance and behavior:

  • The Banner, Modal, and Fullscreen tabs are now under a single Default Design tab. Now you’ll select each message style from a dropdown menu, then configure its design.
  • Another new tab is Advanced Options. This is where you’ll find the new Missed Behavior feature setting. Background push was also moved from the Settings » Configuration side menu into this new tab.

Resources