Relevant Yield gathers data from API sources daily. Depending on your geographical location, there may be slight variations throughout the day, but our goal is to consistently provide fresh data for your work sessions.
This article is about API connection. You should always use the API if possible. However, if for some reason the SSP doesn't provide API connection, you may consider the CSV import option described in this article: Set up a new SSP connection through a scheduled daily CSV file
How to setup a new SSP connection in Relevant Yield:
1. Create an API user in your SSP
Your Relevant Digital Technical Account Manager will supply you with a dev_[customer name]@relevant-digital.com email address. You'll need this address to establish a new API user within the SSP. Note that the API user may differ from a standard user, depending on the SSP.
The primary concern is ensuring the user's access to the SSP's API features.
You may need to provide details regarding the frequency of API calls, typically averaging around 5 calls per day. Fortunately, most SSPs/ad servers don't impose additional charges for API access, simplifying the process of obtaining it.
2. Add a new SSP connection in Relevant Yield
To add a new SSP connection, go to Configuration -> Integrations and click "+ New SSP"
3. Fill in the required fields
In the settings pop-up, you'll need to specify the type (which SSP) and a name for the connection. Additionally, you can define how you wish to manage the imported data.
If you have any questions regarding the settings, please don't hesitate to reach out to our support team. It's important to note that the settings may vary depending on the SSP.
Please note:
- It's important to understand how the mapping is performed in your SSP before populating data in Relevant Yield.
- Utilizing the API is most effective when your placements have unique IDs, as this allows for more granular reporting capabilities and ensures optimal performance.
4. Add SSP API credentials
You will enter the credentials (the newly created API user from your SSP) at the bottom of the settings pop-up.
The required credentials vary depending on the SSP. In some cases, only the 'API user email and password from the SSP UI are needed, while in others, the credentials may include a consumer secret and consumer key. If you're uncertain, please reach out to your technical account manager for additional guidance and support.
5. Populate data
After adding your credentials, the system will populate with data, which becomes visible when generating a new API report. Data may populate automatically, typically by the following day. Alternatively, you can manually initiate an import, ensuring to import one day at a time to prevent overloading the system.
6. Find the "not yet mapped" API structure
Once you can see data coming in, you can always use the Admin - Missing SSP traffic, to see the name of the site/placements imported, and then go on to map the new SSP IDs, to the websites.
