> 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/third-party-connections-and-integrations/flashtalking-adserver.md).

# Flashtalking (Adserver)

Sportradar Demand Side Platform is connected to  Flashtalking Adserver <https://www.flashtalking.com/>.\
The connection to Flashtalking Adserver is helping Sportradar DSP technology to track and count conversions from Flashtalking system.&#x20;

* Collection and storage of the Flashtalking conversion data
* Machine learning based on Flashtalking data
* Data analytics based on combined technologies Sportradar<->Flashtalking

#### **Sportradar custom macros and what does Flashtalking ad tag creative need to have by default, before being added to the Sportradar DSP UI ?**

The most crucial and first TO DO, Sportradar macros need to be applied/setup on ALL running Flashtalking ad tags within Sportradar UI on Flashtalking parameters  **"ft\_custom",v:"${PC\_CONV\_CONTEXT}"},"ft\_section",v:"${PV\_CONV\_CONTEXT}"**

#### **Daily Report Setup and what does Sportradar need to receive from Flashtalking system?**

1\. Sportradar needs to receive a daily custom csv report from the Flashtalking UI.  &#x20;

* The type of the report inside the Flashtalking UI is “**Transaction**”.
* The file type is “csv”.
* The date range is “Last # days” and # of days is “1”

2\. The daily “Transaction” csv report needs to include following Flashtalking content and columns/grouping.

**Content:**

* **The Advertiser**, which is needed for the data collection. Example: “All Advertisers activated for Sportradar”
* **The Campaigns**, which is needed for the data collection. Example: “All Campaigns activated for Sportradar”

**Columns and Grouping:**

* The **“conversion name/identifier”** metric. This can be the matric, which is used for the conversion name identification. Sportradar needs to know which metric this is and what is the exact naming! Example metric: It can be “**Item Name**” or “**Spotlight**”. Example value: “Sportsbook First Time Deposit Successful”
* The **custom\_section** metric. This metric is used by Sportradar to provide own macro for the trackings. On this parameter inside the Flashtalking creative script, Sportradar will provide the Sportradar impression macro values.The client needs to activate this metric, to be visible to Sportradar inside Transaction report/Flashtalking UI.
* The **custom\_string** metric. This metric is used by Sportradar to provide own macro for the trackings. On this parameter inside the Flashtalking creative script, Sportradar will provide the Sportradar click macro values. The client needs to activate this metric, to be visible to Sportradar inside Transaction report/Flashtalking UI.
* The **Conversion Type** metric. This metric is used by Sportradar to identify if the conversion type was “impression” or “click”. The client needs to activate this metric, to be visible to Sportradar inside Transaction report/Flashtalking UI.
* The **Sales Timestamp** metric. This metric is used by Sportradar to identify the timestamp of the conversion.
* The **Click / View Timestamp** metric. This metric is used by Sportradar to identify the timestamp of the click / view.
* The **Client Unique User ID like U3 column** metric. This metric is used by Sportradar to identify the client user ID and cross map to Sportradar User ID.

3\. The Scheduling of the Transaction custom report needs to be setup:

* The **Report** needs to be setup as “Daily”.
* The **Time for Starting and Ending** needs to be setup. Example: The Ending can be setup for the “whole year”, just that the Sportradar Connection endpoint does not stop receiving data.
* The **File Delivery** should be setup as “Active”.
* The **File Delivery Connection** should be specified for the Sportradar connection name.

4\. As the last step of the Flashtalking UI integration and availability for Sportradar to receive the daily Transaction custom report, the **File Delivery Connection** needs to be setup:

* The Flashtalking UI **Name of the File Delivery Connection** should be clearly specified as “Sportradar”.
* The **Storage Provider** is **Google Cloud Storage**.&#x20;
* The **Google Cloud Storage Bucket Name** will be provided by Sportradar outside the integration document.
* The **Google Cloud Project ID** will be provided by Sportradar outside the integration document.&#x20;
* The **Path** will be provided by Sportradar outside the integration document.
* The **Google Cloud Service Account JSON Key** will be provided by Sportradar outside the integration document.

All those key points together gives Sportradar the power to access Flashtalking data and to analyse/optimise/develop solutions combining two technologies.


---

# 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/third-party-connections-and-integrations/flashtalking-adserver.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.