> For the complete documentation index, see [llms.txt](https://docs.feedb2b.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feedb2b.com/guides/event-mapping.md).

# Event Mapping

Different sports data providers use their own identifiers for sports, competitions, teams, players, and events.

FeedB2B maps corresponding events from different providers together, allowing you to identify the same real-world event across multiple providers.

### How Event Mapping Works

When multiple providers offer data for the same sporting event, FeedB2B identifies the corresponding events and maps them to a common FeedB2B event.

For example:

| Provider   | Provider Event ID | Event              |
| ---------- | ----------------- | ------------------ |
| Provider A | 874521            | Arsenal vs Chelsea |
| Provider B | 1928473           | Arsenal vs Chelsea |
| Provider C | 553821            | Arsenal vs Chelsea |

Although each provider has its own event ID, FeedB2B recognizes that these records represent the same sporting event and connects them through a common FeedB2B event.

### Why Event Mapping Matters

Without event mapping, switching between providers requires your platform to identify and match the same events independently.

FeedB2B handles this mapping as part of the platform.

This allows you to:

* Identify the same event across multiple providers
* Switch providers without remapping events on your side
* Compare data from different providers for the same event
* Add additional providers with significantly less integration work
* Use different providers for different events while maintaining a consistent event structure

### Provider Event IDs

Provider-specific event identifiers are preserved within FeedB2B.

This means you can identify both:

* the unified FeedB2B event
* the original event from the provider

This is useful for troubleshooting, comparing provider data, and tracking the origin of an event.

### Mapping Availability

Event mapping depends on the availability and quality of data received from each provider.

Not every event will necessarily have a corresponding event from another provider. An event may:

* Be available from multiple providers and mapped together
* Be available from only one provider
* Become available from another provider later

FeedB2B continuously processes provider data to identify and maintain corresponding events.

### Switching Between Providers

Once events from different providers are mapped, you can move between available providers for the same event without implementing provider-specific event matching.

For example:

**Provider A → FeedB2B Event ← Provider B**

If Provider A and Provider B both cover the event, your platform can identify both provider feeds as belonging to the same sporting event.

This is especially useful when testing alternative providers, expanding coverage, or changing the provider used for a particular sport or event.

### Important

Event mapping connects corresponding **events** across providers. It does not mean that all provider data for those events is identical.

Different providers may offer different:

* Markets
* Odds
* Statistics
* Live events
* Update frequencies
* Settlement information

Always treat provider data according to the provider from which it originates.

### Next Steps

Continue with **Markets, Bets & Settlements Mapping** to understand how sports, competitions, events, markets, bets, and outcomes are organized within FeedB2B.

For implementation details and event identifiers, see the **API Documentation**.