> 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 multi-venue groups create a unified customer view?

> Explore how multi-venue operators join buyer, ticket and attendance records without confusing identity, consent and event ownership.

**A unified customer view connects permitted records about a customer across venues and booking channels so teams can understand interactions without manually combining spreadsheets.** It may bring together an account identifier, purchases, attendance, support interactions, membership entitlements and marketing preferences.

## What is a unified customer view?

It is not necessarily one physical database. Operators often maintain transactional data in ticketing systems, approved contact records in CRM and analysis models in a warehouse. The goal is a consistent interpretation of identity and events.

## Why is joining records difficult?

One person can use two email addresses, purchase on behalf of a family, transfer a ticket or book through an external partner. **Buyer, attendee and member are different roles**, and collapsing them into one row produces misleading marketing and attendance figures.

| Situation                              | Recommended modelling distinction                      |
| -------------------------------------- | ------------------------------------------------------ |
| **Parent buys four tickets**           | One payer, potentially four attendees                  |
| **Corporate hospitality order**        | Corporate account, purchaser and guests                |
| **Ticket transfer**                    | Original transaction and current entitlement holder    |
| **Third-party allocation**             | External seller identifier and local fulfilment record |
| **Guest booking then account sign-up** | Linked records with recorded matching confidence       |

Avoid automated merges based on name alone. Design a policy for ambiguous records and reversing incorrect matches.

## What architecture works in practice?

Start by defining stable IDs for customer, order, ticket, event, venue and brand. Record source systems and timestamps, map consent and retention at the appropriate level, and decide which system is authoritative for each field. Use event-driven updates or scheduled extracts depending on latency and reliability needs.

A central reporting model can show unique buyers, repeat visitation and cross-venue purchase patterns, while access controls prevent one venue viewing another venue’s identifiable records without a legitimate basis.

## How do you know whether it works?

Test a refund, transfer, account merge, imported third-party sale and a person who withdraws marketing consent. Reports should distinguish booked tickets from scanned attendance and deduplicate purchase events.

**Bottom line:** a unified view is a data-governance and identity problem as much as an integration problem.

## Where identity matching gets difficult

Two purchases with the same email address are not automatically proof of one person: email addresses can be shared, mistyped or changed. A unified view needs identity-matching rules, conflict resolution, consent management and an explicit distinction between a customer account, an attendee and the person who paid. For example, a parent can buy tickets for four different attendees; merging all admissions into the parent’s profile may be operationally useful but should not be misrepresented as four visits by the same person. Trial the model on duplicates and guest-checkout orders before combining reporting across brands.

## Related explanations

#### [How do multi-venue groups unify ticketing data and reporting?](/by-organisation/how-do-multi-venue-groups-unify-ticketing-data-and-reporting)

Organisation Guides · Multi-venue groups

#### [How do ticketing customer groups support segmentation and presales?](/data-security/how-do-ticketing-customer-groups-support-segmentation-and-presales)

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

#### [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)