How to use In-App interaction tags?

Here are the steps to tag users who have interacted with the buttons of your In-App automations using our built-in actions.

This guide is specific to Batch's Mobile Engagement Platform (More on the difference between Batch's CEP and MEP).

Prerequisites

SDK version

First of all, make sure your app integrates the 1.16 version of the SDK or higher. It includes a built-in action for In-app messages: batch.user.tag.

In-app feature

Built-in actions are actions associated with the call-to-action of an In-App message, which allows you to set up more complex actions than the typical actions associated with a button. These actions do not require any development and can be activated directly via the dashboard when editing the automation.

How to do it?

Set a tag in your In-App automation

1. When you edit your first automation, you need to manage the formatting of the buttons. Let's imagine the scenario of an In-App message presenting new app features. The buttons would be: Discover now and Discover later.

2. Below the dismiss button Discover later, click on Add secondary action and then on Add tag.

3. Create a new collection and the tag(s) to add to your users, or search for tags that exist in the system.

4. A tag is now associated with your dismiss button Discover later, so all your users who will click on this button will be associated with this tag.

Once this tag is set up, it will show up in your custom data. You need to activate it in your Settings > Custom Data so that they appear on the dashboard when creating future In-App automations.

Then you will be able to retarget all of the users who want to discover the new features of your app later on. This will give you an additional way to segment your userbase precisely.

Note that in this example, it would also have been possible to set a tag on the Discover now button, so in case you want to send a second campaign presenting the features, you could exclude users who have already discovered them.

Select a tag in a second automation

When editing the second automation, in order to retarget or to exclude users grouped under a tag, you will have to add the corresponding collection in the targeting section and then select the desired tag:

Other use cases

You can do the same thing in various other use cases.

For example:

• In the context of a rating In-App automation in order to group all users who have clicked on Rate the app under a tag : you could then exclude them from future rating automations.

• If you want to communicate about a contest via an In-App message, you can set a tag on the Participate button. Then in a second automation, you will be able to exclude all users who clicked on the Participate button in order to target only those who have not entered the contest.