1. Overview of transferable data by AdServer

The following data gets imported into the Object AdServer IDs and assigned a type and number. Read more about data import in the linked chapters below.

AdServer/
Import Type

Inventory Data

Creative Templates

Key-Value Data

Targeting Ids

Devices & Connection

Geo- and Technical Targeting Data

Video Content

Content Bundles

Accounts

How to import3.5.5.1 Import Inventory Data3.5.5.4 Import Creative Templates (Google Ad Manager)3.5.5.3 Import Key Value / Audience Segment Targeting3.5.5.7 Import Targeting Ids (Labels)3.5.4 Import Geo- and
Technical Targeting Data
3.5.4 Import Geo- and
Technical Targeting Data
3.5.5.5 Import Video and Content Bundles3.5.5.5 Import Video and Content Bundles3.5.5.6 Import Accounts
SMART
  • Site,
  • Page,
  • Page Group,
  • Pack,
  • Format
  • AdvertiserExclusionCategory
  • InsertionExclusionCategory
-
  • Key
  • Value


  • Imported if using REST API
  • for SOAP data can be requested from SMART and manually imported using the Dataloader or similar
--

-

AOL ONE (ADTECH)
  • Website
  • Page
  • Placement
  • FlexTree (with use of new buttons, Version >= 2.82)
-
  • Key
  • Value
  • FlexTree (predefined values for keys, Version < 2.82)


  • Country
  • City
--

-

Google's DFP
  • Ad Unit
  • Placement
  • Team



  • Creative Templates
  • Key
  • Value
  • Audience Segment
  • Audience Segment Value (SHARED)
  • Audience Segment Value (THIRD_PARTY)
  • Audience Segment Value (FIRST_PARTY)
  • Label
  • Device Manufacturer
  • Mobile Device Submodel
  • Mobile Device
  • Browser
  • Browser Language
  • Device Capability
  • Device Category
  • Operating System
  • Operating System Version


  • Bandwidth Group
  • Mobile Carrier
  • Postal Code
  • Country
  • Region
  • City
  • State
  • County
  • Neighborhood
  • Canton
  • Province
  • Territory
  • Autonomous Community
  • Airport
  • Department
  • DMA Region
  • Governorate
  • Municipality 
  • Prefecture
  • Union Territory
  • Tv Region
  • VideoContent
  • Content Bundles
  • Advertiser-Accounts
  • Agency-Accounts
AppNexus
  • Publisher
  • Site*
  • Placement
  • Format
  • Inventory Attribute
  • Media Type
  • Media Subtype
  • Technical Attribute


*Sites are also referred to as Placement Groups in the Appnexus UI

-
  • Key
  • Value
  • Audience Segment
  • Audience Segment Value
-
  • Device Manufacturer
  • Mobile Device
  • Browser
  • Operating System
  • Brand Company
  • Brand
  • Language
  • Operating System Family


  • Mobile Carrier
  • Country
  • Region
  • City
  • DMA Region
--
  • Advertiser-Accounts
FreeWheel
  • Ad Unit
  • Ad Unit Packages
  • Site
  • Site Group
  • Site Section
-no API Support by FreeWheel - learn here how to import 7.3.7 FreeWheel Features -no API Support by FreeWheel - learn here how to import 7.3.7 FreeWheel Features no API - pls import using DataLoader/CSV File. Get your data here: 

https://hub.freewheel.tv/display/
techdocs/Geography+Data
 and learn here how to import 7.3.7 FreeWheel Features 

  • Video
  • Video Group
  • Series
  • Advertiser-Accounts
  • Agency-Accounts
AdsWizz
  • Publisher 
  • Zone
---
  • Browser
  • Language
  • Tag
  • ThirdPartyAdTagType
  • Countries
  • DMA Region
  • ISP
  • MSA Region
  • Region
  • City
---


The import process imports all data, no matter if active or inactive / archived in SMART or DFP. This is mainly because the process might take a while and the system can't make sure that no changes are done while importing. Otherwise this would lead to inconsistencies between your AdServer and ADvendio. For DFP we update the status in the related ADvendio Objects to match the ADServer values.

This is not relevant for ADTECH.


When your imported IDs have longer names than 79 digits we will write the full name into the AdServer ID field AdServer Name (version 2.102 and higher).

2. Error Messages or Warnings

Version 2.101

The following two error messages are known issues:

One thing that could happen after the process is successfully completed is that you could see on the results page after trying to transfer Adserver Login Data that "0 Ad Server Ids to ADvendio transferred successfully" and that "(all) Ad Server Ids to ADvendio transfer failed". This is usually because for the profile of the user trying to transfer the data, you would need to have the (Adserver you're trying to connect) record type for the Adserver ID's. To make sure this is done, go to setup, profiles, (your profile), Object Settings, AdServer ID's and assign the Adserver you're trying to transfer record type to the profile and test again

3. "Status" of active imported Items

When you import AdServer IDs like described in the steps above you will see that the status field in the AdServer ID Object is filled with the imported value from the AdServer (active, inactive or archived).

If you are working with our feature 3.1.8 Active and inactive inventory items you will need to sync the Active checkbox for all IDs with an active status.

To support you with this task we created two workflows (Version 2.97 and higher):

Here are the steps how to activate these workflows:

  1. Go to Setup > Workflows & Actions
  2. There you will find the two workflows called "Synchronize AdServer ID Status (active)" and "Synchronize AdServer ID Status (inactive)"
  3. Activate both Workflows.
  4. Reimport your inventory.
  5. The Checkbox will be set automatically by the workflow according to the status afterwards.

4. First Level Ad Unit AdServer ID (DFP/GAM)

Customers have to delete the first level root manually to avoid seeing it in the tree.