SpringServe is compliant with the IAB OpenRTB 2.4 specification.
To complete an integration, SpringServe will be asking you for information about the following:
- Cookie Syncing
- OpenRTB Bidder Endpoints
- QPS and Throttling Preferences
Details and questions can be found below. For any questions or concerns please email email@example.com.
Cookie Syncing is the process by which SpringServe and the integrating partner (IP) can translate a SpringServe user id into the IP user id. There are two options for integration
SpringServe is happy to host the mapping of SpringServe user_ids to IP user_ids. On bid request, we will pass through your user_id.
Integrating Partner Hosts
If you are hosting the user mapping database you can use the following call to get a springserve user id
where we replace SS_UUID in the redirect_url with the Springserve user id.
In this case we will redirect to springserve and replace SS_UUID with the user's id.
In order to begin a cookie syncing integration, please answer the following questions:
- Who would you like to initiate the cookie sync (default: SpringServe)?
- What is your cookie sync URL?
- Are there any QPS or throttling constraints on your cookie sync URL?
The user mappings can be hosted either by Springserve or by the integrating partner.
For us to initiate cookie sync you need to provide us with your cookie sync url (either to initiate a mapping or to get your user id so we can store the mapping).
Provide us with your openrtb endpoint/endpoints.
Our datacenters are located in:
- Northern Virginia
Let us know if you need us to hit specific endpoints based on the request region.
Our protocol follows IAB OpenRTB API 2.4 specifications. Let us know if you have any specific requirements.