Datetime segmentation operators
This article provides a reference for working with dates in segmentation.
Segmentations which work with dates:
- First occurrence
- Last occurrence
- Last session start
- Last session start time
- First run
- Last active
The following operators are available when working with Dates and Times in segmentation:
Operator | Description |
---|---|
Is after | Happened after a particular time.
Another way to represent this would be "Last occurrence of Purchase > 05/26/2020 12:00 AM PST". |
Is not after | Happened at or before a particular time.
Another way to represent this would be "Last occurrence of Purchase <= 05/26/2020 12:00 AM PST". |
Is before | Happened before a particular time.
Another way to represent this would be "Last occurrence of Purchase < 05/26/2020 12:00 AM PST". |
Is not before | Happened at or after a particular time.
Another way to represent this would be "Last occurrence of Purchase >= 05/26/2020 12:00 AM PST". |
Is between | Happened between two particular times on the calendar.
Another way to represent this would be "05/20/2020 12:00 AM PST < Last occurrence of Purchase < 05/26/2020 12:00 AM PST".
|
Using Exact vs Relative dates
Leanplum lets you chose between using Exact and Relative dates when segmenting based on Datetime properties.
Exact dates work better when building audiences for calendar-driven engagement, such as users who have last logged in before 01/01/2020.
Relative dates are to be preferred when building audiences for automated or triggered campaigns, such as users who purchased last month, but not this month.
Accepted date formats
ISO-8601 supportedLeanplum supports ISO-8601 date formats.
You can track custom dates in Leanplum for user attributes or event parameters.
Updated 13 days ago