Segmentation by segments engagement
Description
Two levels of nested rules are supported in the Altcraft segmentation:
- Main level — AND/OR rule in the database query
- Additional level — AND/OR rule in query rules group
If you want to use complex selection, that combines several queries to one or more databases, you can use Segment selection group.
In this case, segment is used as external data source for cross selection. If the file, list or website already contains necessary data, you can apply segmentation by external sources. If you need even more exact selection, you can use segmentation by crossing with sql database.
Dynamic segment engagement
To use Segment rule, you need to make selection in one or more databases and save it as certain segment. Than, you need to create a new segment for the final count and add appropriate rule to this segment. Two operators are available for this segment:
- Is in segment
- Is not in segment.
If it is possible, try to avoid Is not in segment operator, especially when you deal with big selections. Rules that uses this operator will compare selection with all segment count result. Crossing data massives will take many system resources.
You can use unlimited amount of these rules in the segment. But segments used for selection can not contain selections by other segments.
These limits were made because of dynamic segment type. All connected segments will be counted for selection, which may take some time.
Static segment engagement
Yo can segment your customers by static segment engagement thus querying for control groups participants. Both current activity and frequency rules are available:
- is in segment
- has been once
- has never been
- once in the past
- is not in segment
- at least [n] times during [x] days
- at least [n] times during period
- never during [x] days
- never during period
