# Build and verify a guest audience

**Console: Marketing → Campaigns → Segments.** A segment defines which guest
profiles match conditions; it does not grant permission to contact them.

1. Create or open the segment and enter a useful name.
2. Add conditions such as spend, visits, lifecycle, tags, source, saved profile
   fields, ordered items, or booking history. Check comparison, value, period,
   and business currency where applicable.
3. In the simple view, guests match **ALL** conditions. **Advanced (any /
   groups)** enables **all of**, **any of**, nested groups, and **NOT**. Read
   the complete logic rather than assuming every condition is combined the same
   way.
4. Review the live estimate and any missing-data notice. An unavailable estimate
   is not zero matches, and a birthday condition cannot match guests with no
   saved birthday.
5. Choose **Available to campaigns** and **Can trigger automations**
   deliberately.
6. Use **Create segment** or **Save changes**, then reopen and verify the rules.

Starting from a recipe can replace current conditions; review the confirmation.
Removing a group also removes its conditions and nested groups. To turn off
Advanced, simplify to the supported flat matching list first.

A surprising count should prompt checking conditions, units, exclusions, and
available data—not loosening thresholds merely to make a bigger audience. Before
deleting or editing a used segment, inspect the campaigns and automations that
depend on it.

The campaign resolves unique included guests, exclusions, and consent/send
eligibility separately. A matched guest may still be held back. See
[Consent](/marketing/consent) and [Campaigns](/marketing/campaigns).

If saving fails, keep the rules and fix highlighted conditions. Reopen before
repeating an uncertain creation. Escalate with segment reference, intended
logic, observed count/state, and error, without exporting raw guest records.