7.7.8.6.1 How to use our generic Programmatic Import to generate Media Campaigns from any Programmatic System, via CSV files.
Available with Version: | 2.159 and up |
|---|---|
Role | System Administrator |
ADvendio Edition | Programmatic Add-On |
Challenge
You are planning to use ADvendios Programmatic features to streamline your incoming programmatic revenue from many different platforms and utilize Media Campaigns for a 360 overview about your ad business in ADvendio, but our support Integrations do not include all your SSPs and Systems in place.
Is there a way ADvendio can support handling the Programmatic Revenue from any external system, for example by a generic file upload, so that you can use the data in the same format as when receiving it from our direct integrations?
How would such an import work, how far can you automize the process and what are the current limitations?
Solution
This article will guide you through Programmatic CSV import and Connection Record creation steps.
NOTE: Please ensure
The option ‘Programmatic CSV import' is activated on the ‘Administration Settings' page (instructions below):
Steps:
Type for 'Administration Settings’ in the main ADvendio menu, and open the 'Administration Settings’ tab.
You need to activate the setting for the ‘Programmatic CSV import'. It is part of the ADvendio Admin settings page:
Create a Custom Connection Record, which represents the external data being imported into ADvendio. This is used to clearly differentiate between Campaigns booked directly in ADvendio and those imported from external sources. Use any ‘Record Type’ to create this Connection or use a Custom Record Type.
It does not require any actual or working user credentials
Now you will need to upload the CSV with your Programmatic Data into ADvendio. You can either:
To communicate with our Programmatic Import API endpoint and upload your files programmatically, please see the following documentation: Programmatic Data Import API - Documentation
Or you can use a button on the Connection record, to manually upload your CSV file (available with 2.159 and up):
You need to make sure this file is structured the right way and does contain the right columns as listed here: 7.7.8.6.1 How to structure CSV for generic Programmatic Revenue upload and how mapping is defined
The upload creates Programmatic Advertiser and Programmatic Price records, which you will need to map using our Programmatic Mapping Tools 7.7.8.3 How to connect and match the data from SSPs / DSPs / Exchanges to your Salesforce Data
Once all these steps are finished, you can run our Programmatic Media Campaign Generation and turn your data into Media Campaigns and Campaign Items. You can perform this via a button on the connection record or as a scheduled process
Current Limitations
Please note with the first version of this feature, there are some limitations that still apply:
Programmatic Partners are not yet supported for generated Media Campaigns:
With version 2.159, Programmatic Partners are not fully supported yet. This means Programmatic Partners will be imported to ADvendio and can also be mapped to Accounts, but during Media Campaign Generation, they will be ignored at the moment. We’re working on enabling this as soon as possible
Uploaded CSV file limitations:
With version 2.159, Programmatic Partners are not fully supported yet. This means Programmatic Partners will be imported to ADvendio and can also be mapped to Accounts, but during Media Campaign Generation, they will be ignored at the moment. We are working on enabling this as soon as possible.
An uploaded CSV file for the programmatic features is only allowed to have 4.000 rows. If files are larger than 4.000 rows, our process can’t handle them. So make sure if you are handling more data, please split your file accordingly.
Setup
Ensure to:
Activate the ‘Programmatic CSV import' tickbox on the Administration Settings page.
We recommend ensuring that the user who is performing the Import has a ‘System Administrator profile' and has access to all ADvendio objects and features. We are working on a dedicated list of permissions required to use this feature.