> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zeotap.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Sportradar
> Configure a Sportradar destination in Zeotap CDP to deliver an audience as a suppression list, so the users in it are excluded from downstream targeting.
## What this is
Sportradar is a global sports data and technology company whose advertising arm runs targeted campaigns across its media network. A Sportradar destination in Zeotap CDP delivers a linked audience to Sportradar as a list of user IDs, so Sportradar can apply it as a **suppression list** — the users in the audience are excluded from targeting rather than targeted.
Because delivery is file-based, this destination is designed for batch audience delivery, not real-time event streaming. Event data cannot be sent through it.
In the destination picker the tile is labelled **Sportsradar**. Search for `Sport` to find it.
## Prerequisites
Before you start, confirm the following. Only the last two are entered in the Zeotap CDP app.
* **Delivery location** — the cloud storage location Sportradar reads from, and its credentials, are configured by Zeotap during onboarding. If your organisation has not been onboarded to Sportradar yet, contact your Zeotap account manager.
* **Destination and audience permissions** — you need access to the **Integrate** application to create destinations, and to the **Audiences** application to link an audience to one.
* **The brand or property the audience belongs to** — this determines which action you select, so identify it before you start.
* **An audience** — create the audience in Zeotap CDP first. See [Create an audience](/articles/segment-customer/create-an-audience).
### Supported identifiers
This destination accepts a single destination field, **User IDs** (String) — the user identifier Sportradar matches against the users it can reach. Map one Catalogue attribute to it.
### Available actions and supported features
Your Sportradar destination is provisioned with **one exclusion action per brand or property your organisation runs**. Each action sends the user ID for that brand, so the action you choose and the audience's brand must line up. Action names follow the pattern `Send User ID to [brand] for Exclusion`.
| Action | [ID EXTENSION](/articles/segment-customer/extend-your-audience#id-extension) | [DELETE](/articles/segment-customer/delta-upload-and-delete-functions) | [DELTA UPLOAD](/articles/segment-customer/delta-upload-and-delete-functions) |
| :-------------------------------------- | :--------------------------------------------------------------------------- | :--------------------------------------------------------------------- | :--------------------------------------------------------------------------- |
| `Send User ID to [brand] for Exclusion` | - | ✅ | ✅ |
If your organisation runs more than one brand, create a separate destination and mapping per brand, and name each one so the brand is obvious — for example `Sportradar – [brand] exclusion`.
## How the connection works
Zeotap delivers to Sportradar through a **cloud storage drop** rather than a direct API call:
1. Zeotap writes the audience to the storage location agreed during onboarding.
2. Sportradar reads that location on a schedule and ingests the audience.
3. As audience membership changes, Zeotap writes delta files so Sportradar's copy stays current.
You do not enter bucket details, folder paths or access keys anywhere in the Zeotap CDP app — the destination form asks only for a name and an instance.
## Configure the destination
Sign in to the Zeotap CDP app and go to **Integrate → Destinations**.
Click **+ Create Destination**. Under **All Destinations**, search for `Sport` and select the **Sportsradar** tile.
On the **Enter Destination Details** screen:
1. In **Destination Name**, enter a name that makes the brand and purpose obvious — for example `Sportradar – [brand] exclusion`.
2. In **Destination Instance**, enter a unique instance name for this destination. This value identifies the destination as distinct, so give each destination its own.
There are no credential fields to complete — the connection itself is configured by Zeotap.
Click **Next** to go to the Mapping screen.
1. At the top of the screen, click the pencil beside **Untitled Mapping** and give the mapping a name.
2. Under **Choose your Action**, select the exclusion action for the brand this audience belongs to.
3. Under **Map the Fields**, map the Catalogue attribute holding that brand's user identifier to the **User IDs** destination field.
The brand name is redacted in this screenshot. In your workspace the action carries your own brand name — for example `Send User ID to [your brand] for Exclusion`.
Click **Create Destination**. The destination is added to the list in the **Audiences** application and can now be linked to an audience.
## Link an audience to the destination
Once the destination exists, link an audience to it from the **Audiences** application. Open the audience, choose **Select Destination**, and search for the destination you created.
Select the mapping you created, and check it matches the audience's brand — a brand's audience must send that brand's user IDs.
Under **Destination Settings**, review **Channel Consent Rule**, then set **Refresh Frequency**:
* **One-time push** sends the audience once and creates no recurring schedule — the destination becomes inactive after the push completes. By default it runs as soon as you click **Save Destination**; set a **Start Date** and a specific time, with a timezone, if you want the single push to run at a particular moment instead.
* A **recurring schedule** syncs on a cadence — hourly, daily, weekly or monthly — and requires an end date.
For exclusion targeting, a recurring daily refresh keeps the suppression list current.
Click **Save Destination**. The audience is queued for delivery to Sportradar.
For the full linking flow see [Link an audience to the destination](/articles/integrate-customer/link-an-audience-to-the-destination); for every scheduling option see [Audience Scheduling](/articles/segment-customer/audience-scheduling). If a consent rule is configured for the mapping or its parent channel, it is applied on top of your audience definition before activation — see [Consent Orchestration](/articles/protect-customer/consent-orchestration-2830401643#consent-rule-at-channel-level).
## Understand delta updates
After the first delivery, Zeotap sends only what has changed. Both **associations** (users joining the audience) and **dissociations** (users leaving it) are handled automatically as delta updates, so Sportradar's copy of the suppression list tracks the audience as it changes.
You do **not** need to create a separate delta or removals mapping. Once the audience is linked and saved, the changes are sent on their own. For how delta and delete operations work across destinations, see [Delta Upload and Delete functions](/articles/segment-customer/delta-upload-and-delete-functions).
## Confirm the audience was sent
Delivery goes straight from Zeotap to Sportradar's cloud storage. That location is not exposed to you, so there is no bucket or folder you can open to check the files — you cannot verify the delivery yourself.
What you can confirm in the Zeotap CDP app is that the audience was linked and the refresh ran:
1. Open the audience in the **Audiences** application and confirm the Sportradar destination card is attached, showing the mapping you selected.
2. Check the destination's last refresh against the schedule you set under **Refresh Frequency**.
To confirm the audience actually arrived, or to check the user ID count on Sportradar's side, contact **Zeotap support** or your **Sportradar support** contact. Sportradar reads the storage location on its own schedule, so the audience lands on their side after their next ingestion run rather than immediately on save.
## Troubleshoot common issues
| What you see | What it means | Where to look |
| :------------------------------------------------------- | :---------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------- |
| No exclusion action appears under **Choose your Action** | The destination has not been provisioned with an action for your organisation's brands | Contact your Zeotap account manager |
| The wrong brand's users are being suppressed | The mapping's action does not match the audience's brand | **Audiences → your audience → Destination Settings**, and the action on the mapping |
| The audience never reaches Sportradar | The refresh has not run yet, or the schedule was left as a one-time push that has already fired | **Destination Settings → Refresh Frequency**, and [Audience Scheduling](/articles/segment-customer/audience-scheduling) |
| Fewer users than expected arrive | A channel consent rule is being applied on top of the audience definition | [Consent Orchestration](/articles/protect-customer/consent-orchestration-2830401643#consent-rule-at-channel-level) |
| Users who left the audience are still being suppressed | Sportradar has not yet ingested the latest delta file | Confirm the last refresh time, then contact Zeotap support or your Sportradar support contact |
If the audience has refreshed successfully and none of the rows above match, contact Zeotap support with the destination name, the linked audience name, the mapping name, and the expected time of the last refresh in your time zone.
## FAQ
The action is brand-specific, so the mapping must match the brand whose user IDs you are sending. Create a destination and mapping that reflect that brand, and name both clearly so the right one is easy to pick later.
That change is captured as a dissociation and sent to Sportradar as part of the automatic delta update. No manual action is needed.
No. Associations and dissociations are both handled automatically once the audience is linked and saved.
No. The storage location and its credentials are configured by Zeotap during onboarding. The destination form asks only for a destination name and an instance.
No. Delivery goes directly from Zeotap to Sportradar's cloud storage, and that location is not exposed to you — there is no bucket or folder for you to open. You can confirm in the Zeotap CDP app that the audience is linked and the refresh ran; to confirm the audience arrived, contact Zeotap support or your Sportradar support contact.
No. The action sends a single destination field, **User IDs**. This destination delivers audience membership for suppression, not event data or profile attributes.
## Next steps
* [Explore linking an audience to a destination →](/articles/integrate-customer/link-an-audience-to-the-destination)
* [Explore the scheduling options for a linked audience →](/articles/segment-customer/audience-scheduling)
* [Explore how delta and delete operations work →](/articles/segment-customer/delta-upload-and-delete-functions)