> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://learn.nuwebgroup.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://learn.nuwebgroup.com/_mcp/server.

# How do ticketing customer groups support segmentation and presales?

> Customer groups organise eligible buyers into sets that can be used for access, offers, communications and reporting. In ticketing, membership status or pr

**Customer groups organise eligible buyers into sets that can be used for access, offers, communications and reporting. In ticketing, membership status or prior purchasing history may determine whether a customer sees a presale or restricted ticket type.**

## What is a customer group?

A group may be maintained manually, imported from a membership system or derived from a rule such as an active subscription. It differs from an event audience segment used only for marketing: a group used for checkout eligibility must be checked when the booking is created.

## How does a presale use groups?

A venue might allow current members to buy on Monday, subscribers on Tuesday and everyone on Wednesday. The platform should decide which customer is eligible, when the window opens, what inventory is exposed and what purchase limit applies. Simply hiding a ticket link is not the same as enforcing the rule.

| Mechanism                  | Purpose                                | Risk to test                        |
| -------------------------- | -------------------------------------- | ----------------------------------- |
| **Logged-in membership**   | Link entitlement to a customer         | Expired or duplicated membership    |
| **Single-use access code** | Grant one limited purchase opportunity | Code sharing and reuse              |
| **Imported group**         | Sync eligibility from another system   | Stale status after cancellation     |
| **Purchase history rule**  | Reward existing customers              | Incorrect merges or family accounts |

## How should the data be managed?

Document who maintains membership eligibility, how quickly changes propagate and how customer consent is handled separately from purchase permissions. Staff overrides should be traceable. A customer who belongs to several groups may need a clear priority rule so that discounts and allocations do not stack unexpectedly.

## What should buyers evaluate?

Test expired memberships, a shared access code, an existing customer purchasing for companions, and a customer removed from a group mid-presale. Confirm that eligibility can be reported independently from sales volume.

## Related explanations

#### [How do multi-venue groups create a unified customer view?](/data-security/how-do-multi-venue-groups-create-a-unified-customer-view)

Data & Security · Customer data and ownership

#### [Who owns customer data in ticketing?](/data-security/who-owns-customer-data-in-ticketing)

Data & Security · Customer data and ownership

#### [What customer data does ticketing software collect?](/data-security/what-customer-data-does-ticketing-software-collect)

Data & Security · Customer data and ownership

#### [Who controls customer data in a white-label ticketing arrangement?](/data-security/who-controls-customer-data-in-a-white-label-ticketing-arrangement)

Data & Security · Customer data and ownership

[More in Data & Security →](/data-security)