- Name the rule — Choose a clear Name; the system creates a Key used when storing tags.
- Add conditions — In Tag Conditions, add one row per activity check: pick an Event, set Count and Months, and fill parameters when shown. See the analytics events catalog.
- Combine conditions — On Rule Information, choose AND (must meet all rows) or OR (any row is enough).
- Optional filters — On Rule Information, you can restrict by profile status, turn on Invert, and set tag Lifetime. See Profile status, invert & lifetime before using invert.
- Save and activate — Save a new rule; set Rule status to active when ready.
- Link to profiles (optional) — Use Create Attribute so the tag appears as a normal attribute under External Info.
- Run — Click Execute to test, or wait for the nightly automatic run. Review Matching Profiles.
Full side effects: Tag Rules
| Column | What to enter | Effect |
| Event |
Pick from the analytics event catalog. |
Defines what activity is counted. Changing the event clears dependent parameter pickers. |
| Param 1 |
Optional. Label changes per event (for example questionnaire name, screen id, login result). |
Filters the event stream before counting. Leave blank to count all occurrences of that event type. |
| Param 2 |
Optional second filter when the event supports it (for example introduction response reaction). |
Further narrows which events count toward the threshold. |
| Count |
Minimum number of matching events required (whole number). |
Member must meet or exceed this count inside the lookback window. |
| Months |
Lookback window in months. |
Only events within this many months are included in the count. |
Parameter labels and dropdown options come from the selected event — see analytics events catalog for param hints per event. Multi-select params store several values; the member qualifies if any selected value matches.
Create Attribute / View Attribute: After save, use header actions to materialize the rule key as an External Info attribute (default group external) so filters and communications can reference the tag like any other profile field.
Matching Profiles: After Execute or the nightly job, open this tab to preview which profiles received the tag under current conditions.
| Field (Admin) | What to enter | Effect when the rule runs |
| Profile Statuses (multi-select) |
Pick one or more lifecycle statuses (for example Approved, Active). Leave empty to ignore status. |
When at least one status is selected, only members whose current profile status is in that list are considered for tagging. Event counts are still evaluated first; this filter applies to the resulting list. |
| Invert (toggle) |
Off by default. Turn on only when Profile Statuses is set. |
Normal (off): Tag people who matched your event conditions and have one of the selected statuses. Inverted (on): Tag people who did not match the event conditions, and have one of the selected statuses, and whose account was created more than 30 days ago. Useful for “inactive” or “missing activity” campaigns—test with Execute before relying on the tag in communications. |
| Tagged Expiration Days (Lifetime) |
Optional number of days. Leave blank for tags that never auto-expire from this rule. |
On every manual Execute and nightly automatic run, the system removes stored tags for this rule’s key when the tag row has not been refreshed within that many days. Members who still qualify on the next run get the tag written again. |
How invert interacts with event conditions
Event rows (event type, count, months, parameters) are always evaluated against analytics first. Invert does not flip AND/OR on those rows—it changes which profiles receive a tag after the event query completes:
- Invert off — “Tag everyone who did enough of this activity (and passes profile status, if set).”
- Invert on — “Tag everyone in the selected statuses who did not appear in the activity results (and joined more than 30 days ago).” Event counts are not written as the tag value in invert mode—the tag marks presence with a simple flag-style value.
If Profile Statuses is empty, invert has no effect in the processor—always pick statuses when using invert.
Lifetime in plain terms
Think of lifetime as “refresh or expire.” A member who keeps qualifying each run keeps the tag. A member who stops qualifying will still show the old tag until the lifetime window passes without a refresh, then the tag is removed automatically. Pair lifetime with communications or reports that read External Info so stale segments do not linger indefinitely.