Skip to content

Commit a9b759a

Browse files
author
Olesia
authored
Added information on timestamp format for time comparison operators
1 parent fa1449b commit a9b759a

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

src/engage/audiences/index.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,11 @@ You can also use computed traits in an Audience definition. For example, you can
4242
> info ""
4343
> Engage supports nested traits, but the Audience builder doesn’t support accessing objects nested in arrays. When you send arrays of objects, they are flattened into strings. As a result, the same conditions that work on strings will work on the array. Within the builder, you can only use string operations like `contains` and `does not contain` to look for individual characters or a set of characters in the flattened array.
4444
45+
### Time Comparision
46+
47+
You can use various time comparison operators in your Audience definition. Such operators are: before date, after date, within last, within next, before last, after next. Only ISO timestamps can be used with these operators.
48+
If the timestamp is not a valid ISO timestamp (for example, a trailing 'Z' is missing), it will not be processed by Real-time compute. See [Real-time compute compared to batch](docs/engage/audiences/#real-time-compute-compared-to-batch)
49+
4550
### Funnel Audiences
4651

4752
Funnel audiences allow you to specify strict ordering between two events. This might be the case if you want an event to happen or not happen within a specific time window, as in the following example:

0 commit comments

Comments
 (0)