Salesforce for sport and media: one fan profile, sponsors and rights

21 October 2026
Arcsen

In the Gulf, a race weekend or a cricket tournament leaves fan data everywhere: in the ticketing platform, the official app, the streaming service, the shop and the newsletter list. Each system holds part of the fan, and none of them holds the whole. When race week arrives, marketing has days to reach the right people in Arabic and English, while the commercial team sells next season’s partnerships from spreadsheets and email.

Broadcasters and publishers have the same split between viewers, readers, subscribers and advertisers. On Salesforce, the answer is a design across four products: one fan profile in Data 360, activation in Marketing Cloud, sponsorship and rights sales in Sales Cloud, and fan service in Service Cloud. This guide covers each.

One fan profile in Data 360

Data 360 is the name Salesforce has used for Data Cloud since 14 October 2025. It ingests batch or streaming data from each source, unifies it into profiles with identity resolution rulesets, and activates segments to channels. For a sports body or an event, the sources are usually these:

Ticketing: purchases, seats, transfers and gate scans, which show who attended as well as who paid.
The app: sign-ins, favourite teams or drivers, and notification permissions.
Streaming and content: subscriptions and viewing, for rights holders and broadcasters with their own service.
Shop, hospitality and fan service: orders, packages and cases.

Where a platform has no ready connector, an integration layer such as MuleSoft carries its data in. Matching is where fan data goes wrong. One buyer often books for a family or a group, names arrive in Arabic and in several Latin spellings, and the same fan signs up to the app with a different email. Salesforce’s match methods include Exact Normalized for email, phone and address, and Fuzzy methods for most fields. The High Precision fuzzy method covers international alphabet characters and cross-cultural spellings, and its examples are in Latin script. Match on normalized email and phone first, and test fuzzy name matching on real Arabic and transliterated names before you rely on it. Corporate partners belong in accounts, where fuzzy methods are unavailable.

Race weeks and tournaments in Marketing Cloud

An event runs to a fixed calendar, so campaigns can be built backwards from the date: on-sale, pre-event information, travel and access, the day itself, the follow-up and the next on-sale. In Marketing Cloud Engagement, each automated campaign has one entry source: a data extension that admits contacts on a schedule, or an API entry event, which Salesforce recommends when the activity happens outside the platform, such as a ticket purchase or an app sign-up. Segments built in Data 360 drive the scheduled sends, and events from ticketing and the app drive the triggered ones.

WhatsApp needs planning. For conversations your business starts, Marketing Cloud Engagement must use template messages, which need WhatsApp approval before sending, and approval can take up to 24 hours. Submit every race-week template in Arabic and English well before the week, with an email or SMS fallback.

Consent decides who can be reached. The privacy data model in Data 360 records consent per contact point, per channel and per data use purpose, and Salesforce notes that deciding how to honour privacy preferences is up to you. Where you rely on consent, SDAIA’s guide to the Saudi Personal Data Protection Law says it should be freely given, and people can withdraw it at any time. Treat sharing data with a sponsor as a purpose of its own, asked for at ticketing and app sign-up.

Rule of thumb for race week: templates approved, segments tested and agent answers reviewed in both languages before the week starts. During the week, change the content and leave the data model and the rules alone.

Sponsorship and commercial rights on Sales Cloud

Partners buy rights by property, category, territory and term, and the commercial team needs to know what is sold, what is held and what renews. Sales Cloud carries this from lead to renewal:

Stage	In Sales Cloud	Decide before you build
1. Enquiry	A lead for the brand or agency, with the property and category it asked about	Who qualifies enquiries, and how agency deals are credited
2. Availability	Rights packages as products, with property, category, territory, platform and term	Which categories are exclusive, and who may hold a package for a prospect
3. Proposal	An opportunity with packages, price and term, and approvals for discounts and bespoke packages	Discount limits, and which deals need the commercial director
4. Contract	The contract and its deliverables: placements, hospitality, content and any data rights	Which deliverables become records, so delivery can be reported
5. Delivery	Deliverables tracked against each event, with evidence such as photos and audience reports	Who confirms each deliverable, and when the partner sees the report
6. Renewal	A renewal opportunity created at signature, due well before expiry	How early renewal talks start, and what evidence the partner receives

Automate the exclusivity check: before an opportunity closes, confirm that the category is free for that property, territory and term. For the largest partners, Sales Cloud account plans hold objectives backed by metrics and a SWOT analysis, so renewal planning starts from what the partner wanted and what it got.

Broadcasters and publishers also sell advertising and subscriptions, and that is the scope of Salesforce’s Media Cloud. Its page covers advertising sales, converged media planning, omnichannel campaigns, subscriber lifecycles and churn, and names an Ad Proposal Agent. A sports body selling sponsorships and rights can usually stay on Sales Cloud.

Fan service, with an agent for the busy hours

Fans ask the same questions in waves: where is my ticket, which gate do I use, can I bring a bag, is there step-free access, how do I get a refund. In Service Cloud, every question that needs a person becomes a case with the event, the ticket and the fan profile. An Agentforce Service Agent can answer the rest from approved content, and four rules shape the design:

Inbound only. The service agent only supports inbound conversations, and a session closes 72 hours after the conversation starts. Race-week notices go out through Marketing Cloud, and the agent handles the replies.
Arabic is Beta. Salesforce’s language support list marks Arabic as Beta and warns that languages in beta may be inconsistent when retrieving information. Review Arabic answers before the event and keep an Arabic-speaking person on duty.
Limit what the agent sees. Data masking through the Einstein Trust Layer is disabled for service agents, so give the agent only the fields it needs.
People keep the hard cases. Refunds outside policy, accessibility needs, safety concerns and complaints go to a person, with the conversation attached.

Our work in sport and media

Saudi Motorsport runs Formula 1 on Marketing Cloud and Data 360: fans, drivers and corporate partners from every SMC platform, unified into one Salesforce estate and activated for race week. The International Cricket Council, the global governing body for cricket, runs rights-and-services sales from lead to renewal. Our media, sport and entertainment clients also include Shahid and Argaam.

Where to start

List every source of fan data, its owner and the identifiers it holds: email, phone, ticket account and app ID.
Agree the match rules and test them on real Arabic and English names before the first load.
Write the consent purposes, sharing with sponsors among them, and ask for them at ticketing and app sign-up.
Plan the next event backwards: templates submitted, campaigns tested and agent answers reviewed in both languages.
Put the rights inventory and renewal dates into Sales Cloud before the next sales cycle.

Planning a fan profile or fan service for your next event? The Agentforce Readiness Assessment takes ten working days and gives you three use cases and a costed pilot plan. See our media and entertainment work, or talk to our media and entertainment team.

Frequently asked questions

Which fan data should go into Data 360 first?

Ticketing and the app, because they carry the identifiers most fans share, email and phone. Add streaming, shop and service data once the match rules work on real Arabic and English names.

Does a sports body need Salesforce Media Cloud?

Usually not. Media Cloud is built for advertising sales and subscribers, which suits broadcasters and publishers. Sponsorship and rights sales can run on Sales Cloud, with Data 360 and Marketing Cloud for fans.

Can Marketing Cloud send WhatsApp messages for race week?

Yes, through Marketing Cloud Engagement. Messages your business starts must use templates approved by WhatsApp, and approval can take up to 24 hours, so submit race-week templates in both languages early.

Can an Agentforce agent answer fans in Arabic?

Yes, with a Beta label. The service agent only answers conversations that fans start, so race-week notices go out through Marketing Cloud, and an Arabic-speaking person should review answers and take over hard cases.

How should sponsorship renewals work in Sales Cloud?

Create the renewal opportunity when the contract is signed, track deliverables against each event, and start renewal talks with the delivery report and the partner’s account plan.