> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/ads/dsp-cookies-and-attribution/sportradar-attribution.md).

# Sportradar Attribution

**Key Points**

* For the best algorithm and advertising campaign optimization Sportradar is integrating own tracking solutions on websites.
* To have the best optimization in place, the signals that Sportradar receive from the website, need to be integrated based on Sportradar documentation and requirements.
* To guarantee the best performance Sportradar tech requirements needs to be followed.

**Attribution Tracking Ways**

Sportradar is using Cookie, Cookie less/Fingerprinting and Hybrid Postback methods to track user's conversions.

**Used Data Flow**

For correct and valuable tracking and Sportradar being able to do post click or post view attribution based on users individual action, DSP platform should use same data, that is available in bid-process as Sportradar buy traffic/ad placements, combined with advertising served on publisher websites to an user and finally the tracking code call on the operator's website.

**Cookie Attribution Tracking**

 

For cookie tracking Sportradar is using from tech point of view cookies, Sportradar is placing on the website. The cookies could be also seen online on the Sportradar website <https://sportradar.com/cookie-notice/> you have the freedom to more read about the cookies.&#x20;

Based on the cookies, Sportradar is placing on the operator website and as the ad is delivered on publisher websites, those will be combined and in that way Sportradar is aware which users are converting being impacted by Sportradar advertising.

The attribution default windows used for cookie tracking are 7 days post view and 30 days post click.&#x20;

**Cookie less/Fingerprinting Attribution Tracking**&#x20;

Data points used from tech point of view to build users fingerprinting ID:

* user's IP address (process of course GDPR conform)&#x20;
* user's device user agent (information about device, browser, etc.)\
  &#x20;example - "Mozilla/5.0 (iPhone; CPU iPhone OS 13\_1\_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.1 Mobile/15E148 Safari/604.1"
* user's browser language and other user browser details

Sportradar is using fingerprinting methodology in order to create the users fingerprint IDs (out of the above shared data), which is giving Sportradar the ability to do attribution between the tracking placed on the operators website and the ad delivered on the publisher website. In that way Sportradar is aware which users are converting and being impacted by Sportradar advertising. Heavily now days happening on browsers like Safari (iOS), where Safari doesn't allow anymore to place 3rd party cookies to the users browser.&#x20;

The attribution default windows used for fingerprinting tracking are 7 days post view and 30 days post click.&#x20;

**Hybrid Attribution Tracking for Deposits through Postback**

For the hybrid attribution is a process having First Time Deposit and Recurring Deposit events integrated via postback (server to server).\
\
Hybrid integration especially is processing Sportradar Tag Manager events like Page View, Registration Start, Registration Finished and Login from frontend standard script integration and the Deposits from postback (server to server) integrated way. \
\
Why hybrid ? Due to betting operator payment methods, which could take longer (like hours), and are not in real time processed with sending the script event information to the user browser after the payment success, the additional process is to utilize deposit postbacks (server to server). This is a custom integration with Sportradar **on request.**\
\
The attribution default windows used are 7 days post view and 30 days post click.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportradar.com/ads/dsp-cookies-and-attribution/sportradar-attribution.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.