Overview

Tag rules automatically label ("tag") members based on patterns in their in-app activity — for example, how many times they opened a questionnaire, or whether they sent a specific event within the last few months. The tag is written as an attribute value on the member's profile, which you can then use in filters, matching adjustments, and reports.

Tags come from aggregated app activity data, not from manual profile edits. Each rule queries how many times an event occurred per member over a time window and compares it to a threshold.

Open tag rules from Users → Tag Rules.

Every rule below is built from condition rows (event + count + months). A rule can instead run a dynamic SQL query generated from a plain-language prompt — the same underlying process, tags, and expiration behavior, but able to answer questions condition rows cannot (ratios, sequences, joins against Postgres tables like introductions or profile_responses). See Dynamic SQL tag rules.

Tag rules list

ColumnWhat it shows
NameThe rule's display name.
KeyThe attribute key automatically generated from the name. This is what the tag is stored as on member profiles.
DescriptionOptional notes about what the rule does.
LifetimeHow many days before the tag expires. Blank means the tag never expires automatically.
StatusActive or inactive. Only active rules are processed by the nightly job or manual execute.
CreatedWhen the rule was created.

Click Add Rule to create a new rule. Click any row to open and edit it.

Rule information fields

FieldWhat to enterNotes
Name A clear name for this rule. Required. The system auto-generates a unique key from this name.
Tagged Expiration Days Number of days until the tag is automatically removed from profiles. Leave blank for tags that never expire. The expiry is evaluated each time the rule runs.
Description What this rule is for. Optional.
Profile Statuses Limit the rule to only run against members in these statuses. Leave blank to run against all statuses.
Operator Choose AND (all conditions must match) or OR (any one condition must match). Controls how multiple conditions combine.
Invert When turned on together with Profile Statuses, the rule tags members in those statuses who did not meet the event conditions—instead of tagging those who did. Only applies when you also pick at least one profile status. The nightly run also limits inverted tags to members whose account was created more than 30 days ago. Leave Invert off for normal “did this activity” rules. See building tag rules — invert & profile status.

Saving: When creating a new rule, click Save. For existing rules, every change auto-saves immediately — there is no Save button on existing rules.

Tag conditions

Each condition defines an event threshold that members must meet to be tagged.

FieldWhat to enter
Event Which in-app analytics event to count. Choose from the dropdown. See Analytics events catalog for a description of every available event.
Param 1 / Param 2 Optional filters on the event. The options change depending on the event you selected. For example, a questionnaire-related event may let you filter to a specific questionnaire name. Leave blank to count all occurrences regardless of parameters.
Count The minimum number of times the event must have occurred. For example, entering 3 means the member must have triggered this event at least 3 times in the lookback window.
Months The lookback window in months. Only events within this many months are counted. For example, 6 counts events from the last 6 months only.

You can add multiple condition rows. Whether all must match or any one must match is controlled by the Operator field in the rule information.

Changes to conditions auto-save on existing rules.

Running a rule

Tag rules run in two ways:

MethodWhen it runsWho it applies to
Execute (manual) Click the Execute button on the rule page. This runs the specific rule immediately against all matching profiles. Profiles matching the rule's status filter
Nightly job (automatic) Every night at 2:00 AM UTC, all active rules for all brands run automatically. Inactive rules are skipped. All brands, all active rules

Only active rules are processed. An inactive rule can be saved and configured, but it will not tag anyone until you set it to active.

When a rule has a Tagged Expiration Days value, the run also removes tags from profiles where the tag is older than that number of days.

The Execute button only appears on saved (existing) rules, not while creating a new rule.

Linked attribute

Each tag rule writes its result as a profile attribute using the rule's Key. For the tag to be useful in filters and matching, you need to make sure an attribute exists with the same key.

  • If no attribute exists yet, a Create Attribute button appears on the rule page. Click it to create the attribute automatically using the rule's key.
  • If the attribute already exists, a View Attribute button appears instead, linking you directly to it.

Once the attribute exists, you can use it in Users by Attribute filters, in group rules, and anywhere else attributes are used.

Matching profiles

The Matching Profiles section on the rule page shows which members currently have this tag. It looks up profiles that have the rule's attribute key set (via the external info lookup). Use it to verify the rule is tagging the right people after a run.

Reference