Begin with the fan journeys
A supporter may buy a ticket with one email address, browse the website without signing in and use an app account created years earlier. Calling those records one person is an identity problem before it is a dashboard problem.
List the journeys that matter most: discovering fixtures, purchasing tickets, attending, using the app, buying merchandise and taking part in loyalty. For each step, note the system involved, the identifier it stores and the permissions attached to the data.
Choose a reliable identity spine
A shared account can provide a strong connection between channels, but it rarely covers every fan from day one. Matching rules should be conservative and explainable. An email address may change or be shared; a device identifier should not silently become proof of a person’s identity.
Keep a record of how profiles were joined. Give teams a way to investigate duplicates and separate records linked in error. That makes the profile useful for service as well as marketing.
Put permissions beside the data
A single fan profile is not a license to use every signal in every campaign. Store consent and communication preferences in a way that follows the person across connected products. Limit access according to staff roles, and make data retention and deletion part of the design.
The organization should agree who controls each source before integration work begins. This becomes especially important when a league platform serves several clubs.
Make the first version useful
Choose a small number of trustworthy fields and one operational use case. Attendance and purchase history might help a club identify lapsed supporters. Account and loyalty activity might help staff answer a service question without switching screens.
Check the result with the people who will use it. If they cannot see where a value came from or act on it confidently, improve the data flow before adding more charts. A useful fan profile is a maintained product, not a one-time import.