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.