Building Queries
Common questions about events, controls and record matching.
12. What happens to unrelated activity between the events I select?
Sequence Order: without Any, an unexpected record can prevent the current sequence from continuing. Any allows and captures intervening records.
Any-Order: unrelated records are skipped for matching, but count toward the sequence limit while a candidate is active.
Funnel: records that do not match the next expected milestone are skipped without resetting progress.
13. When should I add an Any control?
Use Any in Sequence Order when you want to allow and capture activity between named events.
Example: Product Viewed → Any → Payment Completed.
Captured wildcard records count toward the sequence record limit. Any-Order and Funnel do not support Any controls.
14. Can I require the same event to occur more than once?
Yes. In Any-Order, add separate copies of the Event. Each copy requires a separate physical record.
Example: Checkout Submitted + Checkout Submitted needs two matching records; one record cannot fill both.
The Funnel builder prevents adding the same User Defined Event twice.
15. What is the difference between adding event copies and using Recurring?
Copies require separate occurrences. Recurring permits additional matching records while the rest of the query is being satisfied, subject to a maximum.
In Any-Order, two Login Failed copies require two records. One Login Failed with Recurring maximum 3 allows one, two, or three records; it does not require three.
16. Does a recurring maximum include the first occurrence?
It depends on the query type.
Any-Order includes the first occurrence: maximum 3 means up to three matching records total.
Sequence Order’s recurring maximum counts additional repeats after the initial matched event: maximum 3 permits the initial match plus up to three repeats.
Both builders allow only one Recurring control or filter per query. The maximum-count setting supports 1-50.
17. Can one record satisfy more than one required event?
One physical record fills one required positive occurrence in Any-Order. Identical copies require separate records.
Funnel also advances at most one milestone per record. Sequence Order timing controls can evaluate a record and hand it to a following named event; that does not create a second physical record.
18. What happens when a record matches multiple event definitions?
A record can satisfy only one required positive occurrence in an Any-Order set. Adding two identical copies therefore requires two separate records.
Use distinct filter conditions when actions should represent different requirements. For example, define Payment Started and Payment Failed using their specific status values rather than combining an all-payment definition with Payment Failed.
Sequence Order and Funnel match against the next expected event.
19. How do event filter conditions differ from system filters?
Event conditions decide whether one record represents an action.
Example: status = failed defines Payment Failed.
System controls qualify or guide matching across records.
Example: Duration Length limits how long the matched actions span.
An Event’s AND/OR conditions and Any-Order’s system-filter AND/OR setting are separate.
20. What does AND or OR apply to in my query?
Within an Event, AND requires all configured conditions; OR requires at least one. Use one logical operator for that condition group.
In Any-Order’s system filter basket, AND requires every configured filter; OR requires at least one. All positive event occurrences are required in either case.
Any-Order supports one each of Duration Length, Duration Difference, and Recurring, for up to three system filters.
Sequence Order supports one general timing control - Duration Length Branch, Duration Difference, or Duration Difference Branch - plus one optional terminal Duration Length. Timing controls cannot connect directly to each other. Terminal Duration Length must immediately precede End. Branching timing controls require all three outputs connected.