Ad Server Credentials
API credentials for ad servers are created using master data. Ad servers may use different methods for authorization and authentication. You must create API credentials for each ad server in an applicable way.
API credentials for ad servers are linked to the customer group (Corporate Agency) and can be created at this level in the customer group master data view. The API credentials are then retrieved in the campaign detail view based on the selected campaign ad server and corporate agency.
All customers who are connected to the ad servers via the agency group are displayed via the view in the campaign mask:
If a customer's own ad server is to be accessed, it must be created as an ad server in MYDAS. e.g. customer name_DFA
Generally, the maintenance of the ad server credentials should be the responsibility of the customer administrator, since this information is used to exchange access information to the ad server.
If there is more than one Ad Server API credential, the user can choose which one to use. Typically, Ad Server API credentials are associated with different ad server accounts (for example, Sizmek and Adform).
There is only one API credential for DFA Ad Server. The user can then select the appropriate account in the user interface if the DFA user is actually connected to different accounts.
Once users have selected credentials (and account), they are stored at the campaign level and cannot be changed.
Stored campaign credentials are used to communicate with the ad server.
| Field | Description |
|---|---|
| Name | |
| Ad Server | |
| Username | |
| Password | |
| Sizmek Application Key |
Sizmek uses an so called application key for the
API which must be stored in MYDAS. |
| DFA Credential Secrets |
With Google DFA a JSON object is created which must
be stored in the Ad Server Credentials. |
| Corporate Agency | Selection of the agency to be registered to use the
ad server. |
Sizmek Account
As already described in the section about API credentials and accounts, the API credentials for Sizmek Adservers are associated with an ad server account. The user should create Ad Server API Credentials for each account he wants to use in the customer group master data.
The user should be able to display all API credentials for the ad server in the campaign view with the Sizmek Ad Server that belong to the corporate agency of the campaign.
To create a valid Sizmek API credential, the fields User Name, Password and Application Key must be filled in the customer group master data.
DFA Account
DFA Ad Server API Credentials are created in a different way than Sizmek and Adform API credentials. They are also associated with the corresponding enterprise agency.
The API Credentials for the DFA Ad Server are tied to the DFA Ad Server to use the API because the Online Campaigns server has a file named StoredCredential set for that user. The StoredCredential file is used to generate valid access tokens when communicating with the Google DFA ad server.
If you are logged in as a specified user, you must go to https://console.developers.google.com/apis/credentials?project=mydas-onlinekampagnen and create new credentials for the application type (if you have not already done so) "Other" on this page. Once the credentials have been created, the contents of the JSON file containing them must be copied and pasted into the DFACredentials field (this is only a required field) in the customer group master data view and saved.
The user [DAN Account] may be connected to multiple accounts (user profiles), and the user can select the appropriate account (user profile) in the Campaign view. When the user selects the appropriate DFA credentials in the Campaign Details view, the selection field "Accounts" is filled with all possible accounts that the user can select to use.
In the corresponding configuration for [DAN user account], the user must define all desired accounts (user profiles) that are displayed in the selection field Accounts in the campaign detail view.
DFA Data Transfer
All online campaign data is transferred to three objects on the DFA ad server:
- DFA Campaigns
- DFA Placement Groups
- DFA Placements
DFA Campaigns
The DFA campaign name is copied from the MYDAS campaign name (1).
The DFA campaign advertiser is copied from the MYDAS campaign advertiser selection (2).
The start date of the DFA campaign is copied from the MYDAS variant which is valid from field (3).
The end date of the DFA campaign is copied from the valid MYDAS variant in field (4).
DFA Placement Group
For each approved MYDAS placement a DFA placement group was created.
The advertiser in the DFA Placement group is copied from the selection field for MYDAS campaign advertisers.
The DFA placement group is linked to the DFA campaign.
The DFA placement group type is set to "PLACEMENT_PACKAGE".
The price plan for DFA placement groups is created. The start date of the price plan for DFA placement groups is copied from the MYDAS placement that is valid from date (1). The end date of the price plan for DFA placement groups is copied from the MYDAS placement that is valid to date (2).
A price plan for a DFA placement group has a period. Period units are defined as MYDAS Placement volume * MYDAS Placement fixed factor (4 and 5). The start date of the period is copied from the start date of the schedule. The end date of the period is copied from the end date of the schedule.
The price type DFA placement group pricing procedure is copied from the price type MYDAS placement (3).
The DFA placement group name is formed from the tracking ID, site, and channel as the tracking ID_site_channel.
DFA placement group ExternalId is the same as trackingID.
DFA Placement
Each MYDAS technical price has precisely one DFA placement.
The DFA placement name is created from the template if a placement name template is defined. Otherwise, MYDAS AdFormat AdGapId is used. The placement name for the MYDAS AdFormat ad server is used (1).
DFA Placement ExternalId is identical to the MYDAS AdFormat AdGapId.
DFA Placement compatibility is set to "IN_STREAM_VIDEO" if the technical price for the MYDAS AdFormat AdFormat placement type is "IN_STREAM_VIDEO", otherwise it is set to "DISPLAY" (1).
AdForm Account
As described in the API Credentials and Accounts section, the API credentials for Adform ad servers are associated with an ad server account. For each account that the user wants to use, the user should create API credentials for ad servers in the customer group master data.
The user should be able to see all Ad Server API credentials in the campaign view with Adform Ad Server that belong to the campaign's corporate agency.
To create a valid Adform API credential, the username and password fields in the customer group master data must be filled in.