Setting Up a New SSP Connection Through a Scheduled Daily CSV File

If the SSP does not provide an API, follow this documentation to set up a mail import SSP via CSV imports on Yield.

It is always better to utilise the API first, but CSVs can be used as well. Read more about how to set up an API connection:  Setting Up a New SSP Connection with API

Setting Up the CSV Report

You need to ask the partner company to generate automatic daily reports in .CSV format. The daily email must contain exactly one .CSV file. In some systems, you are allowed to do this yourself as well.

Here are a few things to take into consideration:

1. The report needs to be in CSV format. Excel files don't work.
2. Only Gmail is supported as the mailbox.
3. The subject line of the report should be unique. This is especially important if you work with multiple email import SSPs coming from the same sender address.

They should send the email reports to: dev_[customer]@relevant-digital.com. You should have already been given a similar email, but if you're unsure, feel free to reach out to your Technical Account Manager or our support team, and they can provide you with the correct email.

The reports should contain the following fields (please note that it might not be possible to obtain all of these, but the more, the better):

• Date column*
• Placement ID column *
• Placement name column *
• Revenue column *
• Sold Impressions column *
• Deal
• Deal ID
• Advertiser
• (and if possible "Ad Requests")

In Yield, you will need to set up both access to the mailbox and configure the column names in the report.

Setting Up the Integration on Yield

Navigate to Configuration → Integrations and click to add a new SSP integration. The SSP type is "Mail Import SSP." Give the new integration a name; this will appear as the SSP name in the reporting.

Then fill in the required fields (*) and as many additional fields as possible. The columns in Relevant Yield should match the columns in the CSV file sent to the email.

(Not Mandatory) Add how the data should be handled.

• In case the report currency is not EUR, you need to check Use Default Report Currency and then select the currency from Default Report Currency.
• Fill in the fields as mentioned above, depending on the naming of the columns in the .CSV report file.
• Pay attention to the date format in the date column, as you may need to enter it in the Date Format field (this is necessary if the date is not in a standard JavaScript format; if you’re uncertain, ensure that you fill in this field).

To add the credentials for the Gmail account at the bottom of the page, use the same procedure as described for Google Ad Manager.

Using Scheduled Reports with Rubicon/Magnite

By default, we use Magnite's preferred partner connection. If, for any reason, there's a need to set up a Magnite connection as a mail import SSP, here are the step-by-step instructions.

First, create a saved report like this:

• Time Period: Yesterday
• Columns should be:
  • Date
  • Advertiser
  • Zone
  • Zone ID
  • Ad Requests
  • Paid Impressions
  • Gross Revenue
  • Deal
  • Deal ID
  • Buyer
  • DSP
  • Creative Size

Add a filter: Paid Impressions >= 1. This is to avoid adding unnecessary rows in the reports (for advertisers with bid requests that have no impressions). The reason is the 50,000 row report limit in Rubicon, as detailed below.

First, run the report manually and check how many rows it contains. If it exceeds or is close to Rubicon’s 50,000 row report limit, you might need to remove the Advertiser column to avoid losing data. Unfortunately, this means that advertiser reporting in Yield for Rubicon will not be available.

Now, schedule the report daily to the dev_[customer]@relevant-digital.com email address provided by Relevant.