Page Comparison

Challenge:

The ADvendio delivery report features automatically bring the most important information for Campaign Items back into ADvendio. Key metrics such as Impressions, Clicks, and all information needed to be used in our finance module.

...

• judging the performance of Campaign Items by obtaining more detailed delivery information such as conversions

• modifying the billing process, by relying on other metrics such as video views instead of regular Impressions

Solution:

With version 2.139, ADvendio offers a new configuration for integrated external systems such as Adservers. This allows to access additional metrics and numbers from the reporting, and map them to ADvendio fields or even custom Salesforce fields of choice.

...

• Label: Give the setting a name, in order to recognize it in the future. The label given is only relevant for managing the settings. It has no influence on the actual delivery import.

• DeliverDataMetric Name: A technical identifier for the setting. Will be generated automatically once a label is entered. It has no influence on the actual delivery import.

• Source: The API name of the metric to be imported from the connected system. For examples, see the system specific sections below.

• Report Header Name: How the column will be named in the report ADvendio receives. This information is relevant for the right data matching and is system specific. More information below.

• Connection Type: For which type of system the metric shall be used. Attention: Currently, only Google AdManager, Display & Video 360, and Xandr are supported.

• Target: The target field where the information will be saved. This can be either an ADvendio field or a Custom Salesforce field. Please make sure that the field type is fitting for the desired metric (e.g., a percentage field for a conversion rate in % ). The API name of the field is required. For ADvendio fields, the fields include the prefix: ADvendio__FIELDNAME__c).

• Operation Type: Which general import process will be used. Possible values are Delivery Import Enhanced Delivery Report (for Campaign Items) or Buying Delivery Report (for the buyside integration).

• Import Type: Which specific type of import should be performed. E.g., for the total delivery data (on Campaign Item level) or for monthly, daily or sitebased breakdown. For adserver-specific details, please check below.

• Connection ID (optional): If this setting should be used only for a specific connection in the Salesforce Org. Simply paste the record ID of that connection here.

• Calculation Method: In certain cases ADvendio needs to calculate using the values it receives from external systems. Please select if it is expected to simply add the values (e.g., for number of impressions or the total revenue) or if the average needs to be taken (e.g. for average prices like eCPM or conversion rates).

• Expected Value Type (optional): Some systems may require an additional transformation of the imported values. By choosing the desired picklist value, you tell ADvendio which kind of values are to be expected to be entered in the Salesforce Org. E.g., the Google AdManager Reporting API delivers all currencies as cent values (so 10.05$ is 1005). In order to display them correctly in ADvendio, we have to further transform them to the desired outcome. More details can be found in the system specific sections below.

Importing Rates or Average Prices into ADvendio

If you are planning to import certain rates or pricing information into ADvendio, please be cautious. The structure of the ADvendio delivery import can cause mismatches in the values that are imported and saved in ADvendio. For example, when using total reports on Campaign Item object, rounding differences can appear.

...

For more information on how to handle this see: 7.3.19 17 How to bring rates and pricing information like eCPM or CTR into ADvendio from external systems?.

Which import processes and types target which ADvendio objects?

As described above, for the metrics settings an operation type and an import type need to be specified. This is due to the different kinds of imports we have and the different relevant objects, in order to make sure you can configure the right settings here and do the right mapping.

...

...

Specific Settings for Google AdManager

Source: To access the right metric, you need to use the api name of the metric from the Google reporting API. The list of relevant values can be found here: https://developers.google.com/ad-manager/api/reference/v202102/ReportService.Column

...

Expected Value Type: For AdManager it’s needed to set the expected value type because currency and percentage values are delivered in a very specific format that needs to be further transformed by ADvendio. If nothing is set in the configuration, ADvendio will use the number logic as default.

Specific Settings for Google Display & Video 360

Source: To access the right metric, you need to use the api name of the metric from the Google reporting API. The list of relevant values can be found here https://developers.google.com/bid-manager/v1.1/filters-metrics#metrics

...

Now open the csv and copy how the metrics are named there, to add this information to ADvendio. These steps need to be performed as right now it looks like sometimes the name of metrics as listed in DV360 documentation above, differs a bit from the column title in the report.

Specific Settings for Xandr

Source: To access the right metric, you need to use the API name of the metric from the Xandr reporting API. The list of relevant values can be found here: https://docs.xandr.com/bundle/xandr-api/page/network-analytics.html.

...

Report Header Name: Please use the same technical name, as saved in the source field.

...

Setup:

In order to use the additional metrics, you will need to follow the sets outlined in the description. There is no additional specific setup needed.

...