7.3.1.1.1 How are connections to AdServers, SSPs, DSPs and other external systems structured in ADvendio?
Role | System Administrator, Order Manager - Fulfilment |
External Systems | Google Ad Manager, Google Display & Video 360, Adswizz, Freewheel, Xandr, Equativ |
Challenge
ADvendio offers a huge variety of direct integrations to external platforms like AdServers, SSPs, DSPs or Third Party Reporting solutions. They are a vital part of the ADvendio features set and allow us to automize and streamline many process steps.
How are these integrations generally handled in ADvendio?
What will be the most important objects and fields to monitor?
And what will be the first steps to use these integrations
Solution
The following page provides an overview about how ADvendio handles integrations of external systems, which are the relevant objects and what is their meaning for different processes?
ADvendio objects and their goal:
ADvendio Object | Purpose | Features that use this |
---|---|---|
Connection | Stores the information needed to authenticate against the external system (like username, password, tokens or network ids) | Every feature that communicates with an external system |
Additional Login | Used to store additional login information for your connections. | Our Programmatic Data import requires such an additional login. |
Connection ID | Stores a technical ID from an external system in ADvendio so it can be reused. This is can be for example certain targeting configurations, videos or inventory, which are important for you Campaign Item configuration. | Connection IDs are referred to in all of our targeting features, such as: but also as part of the targeting pre-configuration of your products as well as in targeting sets. Â |
Ad Type | As part of the Ad Specs, this is part of your product configuration. The Ad Type specifically handles format and technical related settings, hence it is very relevant for all digital items used in AdServers and similar. Also this is used to save which connection is relevant for which Campaign Item. | Is part of the ADvendio product configuration This information is later reused when submitting items to an external system or when check availabilities. |
Account | Represents advertisers or agencies, which you use to plan your Media Campaigns | This information is mainly relevant when submitting items to an external system or creating new orders. |
External Account ID | If an account from ADvendio is used in an external platform, the External Account ID stores the id from that system, so that ADvendio can match it correctly | Will be handled automatically by ADvendio in the background. |
Media Campaign | These are the orders you create for your advertisers. A Media Campaign consists of multiple Campaign Items. Typically the ADvendio Media Campaign also represents an order/campaign send to an external system, but the ADvendio structure allows more flexibility, so that you can combine items from multiple external systems into one Media Campaign! | Defines all the key information needed for an order to be submitted to an external system. Also provides connection to the needed information about involved advertisers, agencies or similar. |
Campaign Item | Represents the line item you will submit to your AdServer or SSP. Stores all information needed for the configuration and will save all relevant IDs received from the external platform. | Defines all the key information needed to check availability and submit a line item to an external system. Â |
Revenue Schedule / Revenue Schedule Daily | Will break down the Campaign Item performance on a monthly or daily base and store key information (for example the delivered impressions) | The monthly/daily delivery reports update these information These are also used for invoicing on actuals (e.g. delivered impressions per month) |
Delivery Data | Additionally to the monthly or daily revenue schedule, delivery data records are used for a more detailed breakdown of the delivery. Especially for delivery data per site/medium. | Activated via sitebased delivery data This data can be used for revenue distribution in Publisher Payout and out Accounting Interface. |
Enhanced Delivery Data | Similar to delivery data, but with even more specific breakdowns (like impressions per device or per key value pair) | Enhanced delivery data import Can also be used in Publisher Payout |
Â
This is roughly how the ADvendio entities are related to each other:
Â
How to start working with ADvendio Connect?
So to start using the full ADvendio connect capabilities, there are multiple steps to be done:
First of will be configuring the connections and login credentials. The following wiki pages provide an overview about supported features for each integrated system and many more details:
https://advendio.atlassian.net/wiki/spaces/SO/pages/101416965
https://advendio.atlassian.net/wiki/spaces/SO/pages/307494916
https://advendio.atlassian.net/wiki/spaces/SO/pages/439779353/7.3.8+Xandr+(AppNexus)+Features
https://advendio.atlassian.net/wiki/spaces/SO/pages/113836038
https://advendio.atlassian.net/wiki/spaces/SO/pages/456851524
Once this is done there need to be additional preparations of the ad types and products to use for your connected system. For example: https://advendio.atlassian.net/wiki/spaces/SO/pages/156958749 , https://advendio.atlassian.net/wiki/spaces/SO/pages/229867524 or https://advendio.atlassian.net/wiki/spaces/SO/pages/604569619
The Inventory Management features of ADvendio can then help to structure these to individual products which later can be used by the Sales and Order team to create Media Campaigns and Campaign Items to sell to your advertisers.
Setup
There is no specific setup needed. Please note that all ADvendio Connect related features require a separate license for ADvendio Connect. You can check our features and editions overview for more information.