# What your rule will actually match

URL: https://kywi-docs-production.up.railway.app/targeting/what-your-rule-will-actually-match
Type: docPage

Groups are OR-ed and conditions inside a group are AND-ed; a "does not equal" rule also matches every visitor missing that signal entirely.

An audience's condition groups are OR-ed against each other, and the conditions inside one group are AND-ed together. That logic is fixed — it isn't something a rule can change, only something a rule is built inside of.

## Any group, every condition in it

An audience matches a visitor the moment any ONE of its groups matches, and a group matches only when every condition inside it passes. Add a second group to widen who an audience reaches ("marketing visitors OR return visitors"); add a second condition to the same group to narrow it ("marketing AND on a pricing page").

## A missing signal is not "no"

A signal a visitor never sent — no UTM parameter, no query string, no referrer — resolves to nothing at all, and the operators disagree about what that means. **Does not equal** treats a missing signal as not equal to the value you typed, and matches it. Every other comparison — Equals, Contains, Starts with, Matches glob, Is one of, Greater than or equal, Less than or equal — fails on a missing signal rather than matching it.

Four signals are never missing, so none of this applies to them. Entry Page always resolves — to the current page when nothing was stored. Referrer Source Type is always one of its named values, "direct" when there was no referrer. Pages Visited is a list, and an empty list is an empty value rather than an absent one. Is Known Visitor is always literally true or false, never unset — which is what makes Is true / Is false safe to reason about where "does not equal" is not.

## "Does not equal" also matches visitors with no value at all

A rule reading "UTM Source does not equal newsletter" doesn't only match visitors tagged something other than newsletter — it also matches everyone who arrived with no UTM parameters whatsoever, because an absent value is never equal to the one you typed. If you mean "tagged something, but not this," you need a second condition in the same group confirming the signal is there at all.

The rule tester spells each condition out on its own line as you test it, which is where you'll see this play out:

utm.source does not equal newsletter Matches: utm.source = "google", "partner-x", … AND every visitor with no utm.source at all.

## Operators are fixed per signal, not freely combinable

Text signals — the UTM fields, Referrer Domain, Entry Page, Pages Visited, self-ID answers and query parameters — offer Equals, Does not equal, Contains, Starts with, Matches glob and Is one of. Is Known Visitor is a true/false signal and takes Is true and Is false, compared as the words "true" and "false" rather than a real boolean. Greater than or equal and Less than or equal convert the signal's value to a number first, so a value that isn't numeric compares as nothing at all: every numeric test against it quietly fails instead of erroring.

## Matches glob isn't a shell glob

Matches glob supports exactly one special character, `*`. There's no `?`, no character classes, and no way to escape a literal `*` — a pattern containing one is always read as a wildcard, never as the character itself.

Both ends of the pattern are anchored, which is the part that surprises people: `/blog/*` matches only values that *start with* `/blog/`, and `*/pricing` only values that *end with* `/pricing`. Text between two wildcards is the only part that floats. A pattern with no `*` in it is just an exact match, so use Equals for that instead — and if you want "starts with" or "contains" a fixed string, those operators say so more plainly than a glob does.

## Score conditions ride along, but don't gate the group

A group can mix rule conditions with score-contributing ones. The score conditions still add their points to the audience's running total, but they don't themselves decide whether the group's AND passes — only rule conditions (and any custom-registered condition types) do that. See [Score-based audiences](/targeting/score-based-audiences/) for what the total is compared against.
