> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why a "Preferred Email is unknown" rule doesn't catch supporters without an email address

> The Preferred Email condition in Tag/Message/Journey rule builders is a Personal/Work/Alternate selector, not an email address field -- its 'is unknown' option checks whether that selector is set, which it usually is by default, so it won't reliably find supporters who have no email address at all.

# Why "Preferred Email is unknown" doesn't find supporters without an email

If you're building a Tag, Message, or Journey rule to target supporters
who don't have an email address on file, the **Preferred Email**
condition with **is unknown** is the option it's tempting to reach for —
but it won't do what the name suggests.

## What "Preferred Email" actually is

Preferred Email isn't an email address field. It's a setting that says
*which* of a supporter's email addresses (Personal, Work, or Alternate)
should be treated as their main one. Every supporter record has this
setting, and it defaults to **Personal** even if that supporter has no
email address entered at all.

Because of that default, "Preferred Email is unknown" only matches the
rare case where this setting itself was never set — not the much more
common case of a supporter who simply has no email address in any of
their email fields.

## What to use instead

To find supporters who genuinely have no email address, build your
condition on the individual email fields directly:

1. Open the rule builder (Tag entry rule, or a Message/Journey
   audience rule) and use **Advanced Filters** rather than the AI
   assistant, since this needs more than one condition.
2. Create a filter group with its operator set to **AND**.
3. Add one condition per email field — **Email 1 is unknown** AND
   **Email 2 is unknown** AND **Email 3 is unknown**.
4. Apply the filter. This returns supporters where none of their three
   email fields are populated, which is the actual "no email address"
   case.

If you only care about one specific email field (for example, you know
your organization only ever uses the first email field), a single
condition on that field is enough — the three-field AND group above is
for when any of the fields could be populated and you want to be sure
none of them are.

## Need help?

If you're not sure which email fields your account's data actually
uses, or a rule still isn't returning the supporters you expect, reach
out to WeGive Support with the rule you've built — we can help confirm
what's being tested.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.