Targeting

Thanks to the Batch Query Builder, present on all Orchestration creation interfaces and Segments, you can define precisely who you are going to target.

Our Query Builder is composed of all the elements encompassed in the block called Targeting:

• Collected/Imported tokens.
• Marketing/transactional
• Country
• Language
• Segmentation

This documentation walks you through these different targeting capabilities.

Targeting collected or imported push tokens

This section is visible on your dashboard only if you are in the process of importing app push tokens* from a third party tool (through a CSV upload). For more information on how to import tokens check this documentation.

After uploading your CSV file you will be able to define in the targeting of your Campaigns and Recurring Automations** through the “Filter push tokens” section if you want to target :

• Imported tokens only (tokens not yet known to our SDK).
• Collected tokens only (tokens known to our SDK).
• Both types of tokens, imported and collected.
  • This option is only possible from the Campaign API.
• By default, only collected tokens will be targeted.

Unlike the rest of the targeting at query builder level, targeting is done at installation level and not at profile level.
As a result, if a profile has 2 push tokens, one collected and one imported, if you target the collected tokens then only the collected token of the profile will receive the message and not the other token attached to the same profile.

*This filtering only concerns app tokens and not web tokens.
**The targeting on collected/imported is not available for Trigger Automations.

Defining if the orchestration is Marketing or Transactional

For both SMS and Email Orchestrations, you will have to define in your targeting if:

• Your message is for transactional purposes:
  • If you select this option, all your profiles with the channel on which you are creating a message, opt-in or not, will be targeted.
• Your message is for marketing purposes only:
  • If you select this option, only opt-in profiles on the channel on which you are creating a message will be targeted.

Adding conditions

• Click the "Add condition" button to see the list of Built-in and profile data you can use to define your targeting.
• You can add up to 31 targeting conditions and up to 64 values in each targeting condition and nest them into subgroups.
  • Within a group, the same AND & OR operator established the link between conditions.
  • Between groups, you can use different AND & OR operators.

Adding Segments

Segments allow you to save time when creating your targeting by calling pre-defined dynamic user targets.

• Click the “Use Segment” button to define the Segments you want to include or exclude from your targeting.
• You can call several Segments within the same Segment condition:
  • Up to 10 segments can be called.
  • Segments leverage specific operators allowing you to check the pertenency of a person to at least one of the segments listed (contains any of) or all (contains all of)
• You can access/view the segment from the query builder regardless of the campaign status (draft, running, complete) by clicking on the eye icon.
  • It will open the Segment in a new tab.

Check the complete section on Segments

Adding Audiences

Audiences allow you to upload static user targets exported from your userbase (e.g. top 500 buyers) or created by third-party tools.

• Click the “Use Audience” button or select the “Audiences” condition within the Built-in data to define the Audiences you want to include or exclude from your targeting.
• As for Segments, you can call several Audiences and Audiences leverage specific operators (contains any of, etc.)

Check the complete section on Audiences

Using Countries and Language Targeting

Batch captures users' language and country within Profiles. You can use this data for targeting purpose.

• You can select countries and languages by using the drop-down menu or typing.
• There is no limit to the number of countries and languages you can select.

Targeting on Built-in data

Built-in data allow you to target users based on common and essential information about profiles. They can be automatically collected by Batch (e.g. app version after SDK implementation) or be sent via API or Batch SDK (e.g. email address).

Opt-in statuses

Use it to target users according to whether they are Opt-in or not to your channels:

• Email Opt-in: users who are subscribed to your marketing email communications.
• SMS Opt-in: users who are subscribed to your marketing SMS communications.
• Push Opt-in*: users who are subscribed to push notifications.
  • You can target users according to whether they are opt-in to Web and/or IOS and/or Android push notifications.
  • To define the Push Opt-in Status, we look at the last active install by platform (IOS, Android and Web).

*Imported tokens are not considered as Opt-in.

Has Custom ID

Use it to target users based on whether they have a custom_id or not.
It allows Batch users to target anonymous or identified profiles. For example to target anonymous people and encourage them to create an account.

Last Visit

Use it to target profiles based on their last visit date e.g. the last time the user opened the app or connected on the website.
It is often used by Batch customers to reactivate inactive / less active users.

Email attributes

• Email domain.
• Last email click (transactional and marketing).
• Last email open (transactional and marketing).

Targeting Profile attributes

With Batch you can track events and assign profile attributes to your users in order to personalize your messages and refine your targeting.

There are 3 categories of custom data:

• Attributes: they define users based on their settings (signup date, etc), user profile (user city, user gender, etc) or their current status (nb remaining credits, etc). They can contain different type of data (string, number or decimal, boolean, date).
• Tag Collections: A tag is a collection of strings. Tags may be called Channels or Topics with other push providers. The difference is that Batch attaches a "tag" to your user and will only make the list of users once you have created your Campaign on the dashboard or from the API.
• Events: Events allow you to target your users based on how they interact with your app (read article, play video, follow user). Every event has a key, an occurence date, an optional label, and an optional data object.

Event Targeting

With Batch Event Targeting you can :

• Target on all events, with no source limit: mobile SDKs, Web SDKs, Profile API.
• Perform multi-attribute targeting on a single event.
• Use a wide range of operators of different types to refine targeting.

To use Event Targeting, start by choosing your events. When on the query builder, click on “Add conditions”. You will see all the custom events you track among the different targeting conditions. To find your events more easily, we recommend that you use the search. Select your events, and click on the “Add conditions” button.

Once back on the query builder, you can build your Event Targeting by choosing among the 3 options :

• Last_event : Use it to target profiles based on the last occurrence of the event.
  • Example : If you want to target profiles who completed a purchase in the last 30 days.
• Count : Use it to target profiles based on the number of occurrences of the event within the past 3 years (the event retention period) without specifying a time period over which the events were triggered.
  • Example : If you want to target profiles who read more than 30 articles.
• Count_since : Use it to target profiles based on the number of occurrences of the event over a specific time period.
  • Example : If you want to target profiles who read more than 3 articles over the past 7 days.

If you want to specify the attributes that need to be attached to the event for it to be taken into account in the targeting, for example the type of article / the product category / the brand, then you can filter the event using the icon to the left of the cross at the far right of your query. It will open a new line under the event query where you can pick your attributes and specify their values.

• Example : If you want to target profiles who completed the purchase of a specific product (a red dress for example).

Be aware that :

• All following Event attributes are supported : String, Number, URL, date, Array, Boolean.
• You can filter on up to 10 attributes.
• Only the “and” operator is supported between attributes.

Retargeting

Use retargeting to target users based on if they have reacted or not to a previous Email or SMS communication :

When on the query builder, click on “Add conditions”.
You will see 3 new Built-in data, in the “interaction” section :

• Sent message
  • Event available on Email and SMS, does not include skipped, does include bounces.
• Opened message
  • This event is only available on Email and does not include machine opens. It only includes the first open action.
    • If a user opens the same email 5 times , we will only consider the first open (because that is the engagement action) and the date associated with this event is the date of the first open. This is identical to the way Analytics works.
• Clicked message
  • This event is only available on Email and does not include clicks on unsubscribe links. It only includes the first click action on each link.
    • If a user clicks on the same link 5 times, we will only consider the first click. However, if a user clicks on different links in the same Email, it will count as several clicks.

For each Retargeting Event you need to :

• Specify an occurrence of the event, either within an allotted time (count_since) or not (count), or look at the last occurrence (last_event).
  • To find out more about operators, check the previous section on Event targeting.
• Specify if you want to observe this event on either a particular orchestration (and optionally, a particular step), or on one or more channels.

Retargeting Events are available :

• In Campaigns and Automations targeting.
• In Yes/No Splits.
• In Segments.

You can also quickly create a new Campaign to retarget users who have reacted to a previous Campaign by clicking on its additional actions menu and selecting 'Retarget campaign'. You can then choose which reaction event you wish to retarget and which channel you are going to use to send your new Campaign. You will then be redirected to this new Campaign.

i : Note that Retargeting events are stored for 90 days, so you can retarget an Orchestration that was sent up to 3 months ago.

Estimated Reach

The potential reach indicator shows you the approximate number of users who are going to receive your message, based on your current targeting options.
To be relevant, this value needs to be displayed relatively quickly, which rules out calculating it on the entire userbase. Reach estimation is extrapolated by running the selection on a sample of the userbase.

Move the mouse over the value of your estimated reach to see the steps and details of its calculation.

Note that what is explaind on this page is focused on how targeting works for email, SMS and Push v2 channels. For Push v1, the behavior is slighly similar with a few differences. For exemples there is no notion of segments in Push v1.