How to build a single view of every club member

Ask a club marketing team a simple question, such as "which Gold members stopped coming in but still open our emails?", and watch what happens. Someone exports from the membership system, someone else from the POS, a third file comes from the email platform, and by Monday there is a spreadsheet nobody fully trusts.

The data exists. It is just spread across six systems that each know one part of the member. Here is how to bring it together.

Step 1: List every system that knows a member

Most clubs have some version of these:

• Membership. Name, member number, tier, renewal date.
• Point of sale. Bar and bistro spend, visit days.
• Gaming. Player card activity, if you run gaming.
• Bookings. Tables, functions and events.
• Email and SMS. Opens, clicks and consent per channel.
• Club app. Logins, orders and renewals.

Write down, for each one, which identifiers it holds: member number, email, mobile, card number.

Step 2: Agree how records match

One member can appear six different ways: "Kelly, Margaret" in membership, a player number in gaming, "Marg K" in the app, a mobile number in bookings, a card ending in four digits at the POS.

Set matching rules in priority order, and keep them readable:

1. Match on member number first, where systems share it.
2. Then on email.
3. Then on mobile number.

Anything that cannot be matched with confidence should go to a person to review, not be merged on a guess. A wrong merge is worse than a missing one.

Step 3: Keep lineage

Every field in the final profile should show where it came from. If the email in the profile came from the app and the tier from membership, staff should be able to see that. It makes errors easy to trace and fix at the source.

Step 4: Track consent per channel

A member might accept email but not SMS. Store consent per channel and check it before every send, not once a year.

Step 5: Apply exclusions before anyone builds a list

If your club runs gaming, members on a responsible gambling watchlist or with an exclusion should be removed from campaign audiences automatically, before a list reaches marketing. Do not rely on someone remembering to filter a spreadsheet. Check your own state and venue obligations with your compliance team.

Step 6: Ask questions, then save the answers as live segments

Once each member is one record, useful questions get simple:

• Who came to last year's Melbourne Cup lunch but has not been back since?
• Which members come to functions but never the bistro?
• Whose renewal is due in the next 30 days?

Save good answers as segments that update themselves. A win-back segment should drop people automatically when they visit again.

Step 7: Send with approval and a record

Before any campaign goes out:

• Consent and exclusions are applied.
• A staff member approves it.
• The query, segment and campaign are logged with who ran them.

Step 8: Keep the data on infrastructure you control

Member data, especially gaming and spend data, is sensitive. Prefer a setup where profiles live in a database you own, with access by role and an audit log of every query.

What good looks like

A Monday where the marketing manager asks three questions, gets three answers with the members behind them, and has a win-back email waiting for approval before morning tea. No spreadsheet Sunday.

Common pitfalls

• Merging on name alone. Two members called J. Smith are not one person.
• Fixing errors in the combined view only. Fix the source system, or the error comes back on the next sync.
• One-off lists. An exported list is out of date the next day. Live segments are not.

See how Mosaic handles this

member dataclubscustomer data platform