A DSP is used to purchase media inventory programmatically. ADvendio supports a number of DSP integration which can help you:
So what needs to be done in order to connect a DSP to ADvendio?
To use the features of ADvendio, there are different direct integrations of DSPs available.
At the moment we offer a direct integration of the following DSPs:
To use the direct integration a connection record needs to be created.
Via the app launcher, go to connections and click the new button to create a new connection.
Select the record type of the system you want to connect and then enter the required information, like user name, password, api token or similar.
Here is an overview about which information are needed for which specific system.
Google Display & Video 360 requires to generate an OAuth Token in order continue. This can be done with a simple click on the button ‘Generate OAuth Token’ on the connection.
Once all information are entered, click check login button, to see if everything is configured correctly.
During generation of the OAuth Token for Google Display & Video 360 it might be that a warning message is shown, the app isn’t verified.
Please click on advanced settings and then ‘Go to ADvendio Connector (unsafe)’
We’re at the moment at the verification process with Google, the ADvendio Connector is only used to build the connection between ADvendio and Google DV360.
Import of Targeting IDs and next steps
Once the basic connection is configured you can start to synch targeting criteria and other IDs between the DSP and ADvendio. Our targeting import wizard, can support you in that step.
See also which IDs are supported for which system: https://advendio.atlassian.net/wiki/spaces/SO/pages/1613398028
This step is needed for the buyside support and the creation of orders and line items for the DSP from ADvendio. For the invoicing of media spend, the programmatic data import needs to be planned next.
In order to configure your DSP connection, make sure that the user doing those steps has sufficient edit rights to the following:
Object Connection and all fields
Object Additional Login and all fields
the relevant records types of the Connection object
See also this page for additional guidance on the required permissions: