Getting started with REDS

If you are a partner or advertiser interested in using Raw event data stream (REDS) as one of your reporting solutions in The Trade Desk platform, you have several access and configuration options to choose from. After you decide on your data access method, the respective user guides will walk you through the necessary steps. This page provides only a high-level overview of what you need to know and do to get started.

What you need to know

Before setting up REDS, keep the following requirements and constraints in mind:

• All configurations are subject to business approval.
• Data privacy and retention regulations and policies may affect the data you are eligible to receive.
• The setup process requires close collaboration with your Technical Account Manager.

Setup requirements

During setup, provide the following information:

• The IDs of the partner, advertiser, or group of advertisers whose data should be included in the feeds.
• The types of feeds to enable for the selected partner and advertisers: Impressions, Clicks, Conversions, and Video Events.
• The data processing option for handling GDPR consent, if your customer data may fall under GDPR regulations.
• Your preference for including the GDPR Consent feed, which depends on the data processing option you select.

Data delivery

To help you plan your ingestion and parsing workflows, be aware of the following:

• The Trade Desk delivers field values as they appear in the platform and does not modify data to meet individual consumer parsing needs. You are responsible for parsing the data you receive.
• The only exception is characters that violate TSV format (tab, line feed, carriage return), which The Trade Desk handles automatically.
• To map entity IDs to their names after setup is complete, The Trade Desk provides an Entity-ID-to-Name Mapping feed through Amazon S3 or API.

For ingestion recommendations and other best practices, see Best Practices.

What you need to do

To get started, complete the following steps:

1. Review these articles to familiarize yourself with the concepts, available feed data, data regulations, and alterations based on the originating traffic:
   Data practices
   Data available in REDS
   
2. Provide the required information for your access method:
   • Snowflake
   • Amazon S3
3. (Optional) To enable Viewability and post-events feeds, you must enable Post-Bid Viewability Reporting in the platform UI, select a provider, and then inform your Technical Account Manager. For details, see Post-bid viewability in the Knowledge Portal.

If you have any questions, contact your Technical Account Manager.

Best practices

After you set up your REDS configuration, we recommend following these guidelines:

• Ingest data at least once per day to maintain data integrity and timeliness.
• Ingest only the fields and tables relevant to your use case.

  NOTE: As datasets grow, you're responsible for managing your data pipelines accordingly.

• To accommodate future schema changes as data evolves, design your system to be flexible.
• Design pipelines to be resilient. Pipelines should process non-corrupted files or rows while isolating or flagging corrupted ones.
• Parse data as delivered. The Trade Desk delivers field values as they appear in the platform and does not modify data for individual consumer parsing needs. The exception is characters that violate the TSV format (tab, line feed, carriage return), which The Trade Desk handles.