7.3.12.22 [Set up connection] of Burt in ADvendio

7.3.12.22 [Set up connection] of Burt in ADvendio

Challenge:

I want to establish a connection between ADvendio and Burt, as well as connect ADvendio to my additional storage.

Important: How the Integration Works

ADvendio does not connect directly to Burt. Instead, ADvendio reads data from an Amazon S3 bucket that the customer provides. Burt (or any compatible data warehouse) exports CSV data files to this S3 bucket, and ADvendio retrieves the data from there.

Customer Responsibility:

  • The setup, configuration, and maintenance of the S3 bucket is solely the responsibility of the customer.

  • The customer is responsible for ensuring that the S3 bucket is properly configured, accessible, and that valid AWS credentials (Access Key and Secret Key) are available for ADvendio to connect.

  • The customer is responsible for ensuring that Burt (or their data provider) correctly exports data to the S3 bucket in the expected format and folder structure.

  • ADvendio is not responsible for any issues related to S3 bucket availability, permissions, credential rotation, or data delivery from Burt to the S3 bucket.

This integration can be used with any data warehouse as long as the data can be exported in the required format to an AWS S3 bucket.

Solution:

Before starting, you need:

  • AWS S3 bucket credentials provided and managed by the customer (Access Key, Secret Key, Region, and Bucket Name/Path). These are the credentials to the S3 bucket where Burt (or your data provider) exports the CSV data files.

  • A Programmatic license: For programmatic data import, a separate license is needed.

  • ADvendio Storage credentials: To use ADvendio Storage, a separate license is needed.

Note:

For further information on licenses needed for programmatic data import, as well as on the setup of ADvendio storage, please contact your technical account manager, or open a case via the Support Portal at https://support.advendio.com.

Once the requirements from above are met, you can start configuring the connection in ADvendio:

  1. In the App Launcher search for 'Connection'

  2. Create a new Connection

  3. Select BURT as the Record Type.

  4. Enter your S3 bucket credentials (these are your own AWS credentials for the S3 bucket where Burt exports data — not credentials provided

    1. User Name: <Access Key>

      1. Provided by BURT account

    2. Password: <Your Secret Key>

      1. Provided by BURT account

    3. Network ID: <Region>

      1. Here goes your current AWS Region

      2. Here is the documentation to see the format of your region https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html

    4. Login URL: <Bucket Name/Link>

      EXAMPLE of how does it look
      s3://burt-customer-export-us-east-1/production/CBCOF5RR65WW/third_party/2026/03/17/third_party-2026-03-17.csv"

      1. s3://[S3_Bucket&Path]/third_party/[YEAR(YYYY)]/[MONTH]/[DAY]/third_party-[DATE-YYYY-MM-DD].csv → This part in GREEN is completed automatically filled by ADvendio since its dynamic and changes accordingly day by day

      2. Examples of how the URL is constructed and how the complete URL should look like when you enter it:

        1. S3 Bucket: burt-customer-export-us-east-1

        2. S3 Path: production/ABCOF5RR00EE

          i.e.: s3://burt-customer-export-us-east-1/production/ABCOF5RR00EE


  5. The integration will need to store parts of the data in between to generate Media Campaigns. For the Burt integration, the data is stored in the ADvendio Storage. Alternatively, look for the Additional Login object and make sure you select the correct related connection when typing in the ADvendio storage credentials in the next step.

Setting up the Additional Login (ADvendio Storage)

  • To access the storage, in the Connection go to the "Related" Tab and look for the object Additional Logins.

  • Add 'new'

  • Enter the credentials* you received from ADvendio accordingly:

    *These credentials need to be solicited directly from the support team.

You would need to ask for new credentials or a reset in case you lost your credentials, to add to your additional Login for the BURT connection.

  • The credentials are:

    • Record Type = PROGRAMMATICDATA

    • Username = The username you received from ADvendio

    • Endpoint = The name of your endpoint. You will also receive this information from ADvendio, usually identical to the username

    • Password = The password you received from ADvendio

    • Save

Warning:

Please use one Username/Endpoint per org.

If you want to test in Sandboxes please use a different username and endpoint from your productive environment. If you use the import with the same endpoint in different orgs, this may lead to inconsistencies in your data.

Expected Data Format and Folder Structure

ADvendio expects the CSV data files in a specific folder structure within your S3 bucket. Burt (or your data provider) must export data following this convention:

Folder Structure:

The Login URL you configured is the base directory. Under it, the CSV files must be organized as follows:

  • Fixed folder: /third_party/

  • Date folders: /Year/Month/Day/

  • Daily file: third_party-YYYY-MM-DD.csv

Example of the full path for a file:

s3://burt-customer-export-eu-west-1/production/XXXXXXXXXX/third_party/2022/04/01/third_party-2022-04-01.csv

ADvendio automatically constructs this date-based path (/third_party/[YEAR]/[MONTH]/[DAY]/third_party-[DATE].csv) from the base Login URL, so you only need to configure the base path.

CSV Data Structure:

Each data record inside the CSV file must have at least the date, mapped_advertiser, and partner columns to be loaded. All other values are set by default if they are not present.

The currently supported columns are:

date

creative_size

mapped_advertiser

partner

site

transaction_type

impressions

net_revenue_eur

date

creative_size

mapped_advertiser

partner

site

transaction_type

impressions

net_revenue_eur

Example data:

date

creative_size

mapped_advertiser

partner

site

transaction_type

impressions

net_revenue_eur

date

creative_size

mapped_advertiser

partner

site

transaction_type

impressions

net_revenue_eur

202201

300x250

Test Advertiser

Google

http://testsite.nl

open_auction

3055

2.667

202201

300x600

Advertiser One

Google

http://advertisingsite.de

open_auction

152568

306.136

202202

320x50

Advertiser Two

Pubmatic

http://advertisingsite2.cl

open_auction

599

4.300

References: