Audiences

Building an audience is essential to sending a relevant message to your users. Audiences allow you to segment your users based on their behaviors within your app (and your messages) and their profiles. Audiences can be built using events, sessions, or profile data.

Audiences are also highly customizable. Some profile and behavioral attributes are tracked by default with the Localytics SDK out of the box. Other attributes can be created and tracked using your own additions to the SDK. For more information, talk to your Development team or Services team.

When building an audience, keep two things in mind:

  • Segmenting your users to give them the most possible value from the message
  • Keeping the audience large enough that you’re actually getting a return on your investment in the message

Building an audience

To build an audience:

  1. Go to Marketing in the left pane and select Audiences.
  2. To create a new audience, select the green Green + (plus) button button in the upper-right corner.

  3. Select New Audience and enter a descriptive name so you’ll be able to access your audience from different parts of the product (for example, messages) by its name.

  4. Build your audience using behavioral conditions or profile conditions or both.

  5. When you have finished building your audience, select Calculate the number of users in this audience to calculate the estimated size of the audience.

    Keep in mind, this is just an estimate and it might not fully align with the total number of users who end up receiving your message. For more information, see Why is the estimated audience size different than the number of messages sent?

  6. When you are done, select Save.

Adding behavioral conditions

To add a behavioral condition to your audience:

  1. Select + Add Behavioral Condition.
  2. In the Behavior field, select on each individual device or across a person’s devices (so you don’t have to worry about double messaging a user who’s logged in on both their iPad and iPhone).

  3. Select the time frame for the behavior:

    • Select last 180, last 90, last 60, last 30, or last 7 days from the drop-down list.
    • Select last and fill in a number of days.
    • Select static range and select a from date and to date from the calendar.

  4. From the People who drop-down list, select a behavior that users need to perform (or not perform) in order to qualify for the audience:

    • Performed event
    • Did not perform event
    • Had a session

    • Did not have a session

  5. If you selected performed event or did not perform event, select a custom event from the (choose event) drop-down list.

    Work with your Development team to build out custom events that will appear in this list for your app. If your SDK is installed properly, the following default custom events will be available in the drop-down list:

    • Localytics Inbox Message Viewed

    • Localytics In-App Displayed

    • Localytics Place Entered

    • Localytics Place Visited

    • Localytics Places Push Opened

    • Localytics Push Opened

    • Localytics Push Received

    • Localytics Push Registered

    • Localytics Push Sent

    • Localytics Re-engagement

    • Localytics Uninstalled

  6. If you selected performed event or had a session, specify the parameters for the number of times the event or session occurred.

  7. If you selected did not perform event or did not have a session specify the parameters for the number of days the event or session did not occur.

  8. To further refine the behavior condition, you have the option of adding up to five dimensions from the Where drop-down list:
    • To add a dimension, select Add Filter +.

    • To remove a dimension, select — (minus) at the end of the row.

    Here’s a quick example of a behavioral condition:

    • Behavior: Across a person’s devices during the last 30 days
    • People who: Did not perform event Localytics Push Opened
    • In the past: 30 days (but were active in the earlier range)
    • Where: Push Enabled is one of Enabled
  9. To further refine (or further open up) your audience, you can add a second behavioral condition.

  10. To specify how the two behaviors interact with each other, select AND, OR, or AND THEN.

    Modifier Meaning
    AND User must fulfill both of these behaviors
    OR User can fulfill either of these behaviors

    AND THEN

    		 User must fulfill both behaviors sequentially

When you’re satisfied with your behavioral conditions, you can consider your audience definition complete, or you can continue on to add profile conditions.

Adding profile conditions

A profile is a user-level record. You can attach different properties (known as profile attributes) like gender or last website visit. Profile attributes can be dates, text fields, numeric values, or a non-ordered collection called a set.

Use profiles to select a group of users with a shared set of characteristics, or attributes. When building an audience, you can select up to five profile attributes.

Note: It’s important to note that profiles are memory-less, so they can contain only the user’s current state, with no associated history.

To add a profile condition to your audience:

  1. Select + Add Profile Condition. Profiles are available across devices only.
  2. Select a custom profile attribute from the People where drop-down list.

    If your SDK is installed properly, the following custom profile attributes will be available in the drop-down list:

    Scope Profile Attribute Description
    App/Org User typeLocalytics detects whether a profile is known or anonymous.
    App/Org Last session dateLocalytics detects the last observed session per profile.
    App Last CustomDimensionNameFor each custom dimension tracked by your app, Localytics will preserve the last observed value per profile.
    AppLast app versionFor the last logged session per profile, Localytics captures the app version. If a user updates the app subsequently without recording a session, this attribute may not reflect the current app version.
    AppLast OS Version Localytics detects the last OS version being used by a profile.
    AppTotal sessionsLocalytics computes the total number of observed sessions per profile.
    AppFirst session date

    Localytics detects the first observed session per profile.

    App Push enabled

    For the last observed session per profile, Localytics detects whether push messaging was enabled or disabled. If a user updates this subsequently without recording a session, this attribute may not reflect the current status.

    AppLast push opened dateFor the last push opened, Localytics detects the date the profile opened it.
    AppLast in-app displayed date

    For the last in-app displayed, Localytics detects the date the profile opened it.

    OrgLast CountryLocalytics detects the last country a profile was in.
    OrgLast time zoneLocalytics detects the last time zone a Profile was in.
    OrgLast city Localytics detects the last city a profile was in.
    Org Language Localytics detects the last language a profile was using.

    You can also create as many custom profile attributes as you’d like. For more information, see custom profile attributes.

  3. Depending on the type of attribute (numeric value, text field, etc), select an operator and a value to further define the attribute.

  4. To further refine the profile condition, you have the option of adding up to five dimensions:
    • To add a dimension, select Add Filter +.
    • To remove a dimension, select — (minus) at the end of the row.

  5. To specify how the profile attributes interact with each other, select AND or OR to toggle the setting for all added dimensions.

    Modifier Meaning
    AND User must fulfill both of these behaviors
    OR User can fulfill either of these behaviors

    Here’s a quick example of a profile condition:

    • People where Last Push Opened is on or before 14 days ago

      AND

    • Language is one of English