Segment and target options

Segments allow you to create groups of users based on behavior, devices, locations, and other properties.

To create a segment in the Target of a message, campaign, A/B test, or in the Users and Analytics Dashboards, start by selecting one of the criteria from the All Users/Add segment dropdown (pictured above).

The tables below define all of the segment criteria/dimensions available in Leanplum.

📘

You can modify these segment criteria using operators like "is greater than" or "is less than," depending on the type of segment. This article is about your segment criteria options, but you can learn more about your operator options here: Segment operators. For more on putting these segments and operators together, see Building segments and targets.

App version

Saved segments

Behavioral (Events and states)

With Leanplum, you can segment based on custom events, states, and parameters specific to users' activity in your application. Here’s a quick refresher on each of these data types:

• Events: Anything that can occur in your app. Events include clicking on a link, sharing, purchasing, etc.
• States: Any part of your app a User can be in for a period of time. For example, some states can include watching a video, playing a particular game level, or browsing an In-App store. All states have a time and a duration. Duration is set automatically when one state begins and the previous one ends.
• Numeric parameters: Additional data associated with an event or state. For example, if an event is "Level 1 complete," you could apply a numeric parameter for "Level Score." (Text parameters can only be viewed in Analytics reports, not in Users or segmenting options. See here for more.)

Monetization (Behavioral)

Test devices

Lifecycle state

Localization

📘

Note on location:

Leanplum's SDK uses IP-based geolocation for all users, and GPS/Cell-based geolocation from the user's device if available. GPS/Cell-based information is always trusted more — we use reverse geocoding to determine the location. Geolocation is gathered only on app start or resume, so user location is the user's location during the most recent session.

We provide methods to disable automatic collection of GPS/Cell-based geolocation (not IP), as well as a method to set user location manually. See our SDK docs for more information.

Timing

Leanplum accepts many different date/time formats for use with our time-specific segment types, such as:

• MM/DD/YYYY -->  08/05/2015
• MM/DD/YY --> 08/05/15
• X months/weeks/days ago --> 3 days ago
• MM/DD/YY XX:XX AM/PM --> 5/13/16 12:01 am
• MM/DD/YY  XX:XX --> 5/13/16 00:00 to 5/13/16 23:59 

📘

If a date without a time is specified, the time will default to midnight (00:00) that day. 
Only use inequality operators with times, such as since, prior to, and between. The operator “is” will not match any users. For more on date time operators, see [Time-related targeting operators.

Technology

Source (User acquisition)

The attribution details for specific users are generally given through 3rd party attribution providers who pass the source details to Leanplum via a postback (webhook).
If you work with a specific 3rd party and want to know if we can integrate, please contact your CSM.

User attributes

User attributes are key-value pairs that describe properties of a User. Keep in mind that User attributes may change after a target segment gets evaluated.

User attributes can store any custom data you collect from your Users. For example, you might set up some attributes like “firstName,” "gender," or “destinationCity.”

🚧

The ISO-8601 timestamp format will work for user attributes being used as message targets, but you will not be able to filter or search for these attributes in Analytics or the Users page. We generally recommend UNIX timestamp for these purposes.

Users and randomized groups