Also have a look here 7.8 Error Messages.
[UniqueError.NOT_UNIQUE @ .name; trigger:'...']
There is already an order with the same name existing in GAM.
Change the Media Campaign Name (or AdServer Name of the Media Campaign) in ADvendio.
No Salesperson "XXXX" was found.
The Salesperson you are trying to set for your Order doesn't match to a Google user. ADvendio, as a default, uses the Salesforce user as a Salesperson in Google and if you have no configuration done in ADvendio for this, the warning will be shown. This message is a warning and doesn't affect the results of the submit, your orders and items are still created.
Please read here to set your salesperson or teams. 3.5.10 Manage Teams, Ad Manager, and Trafficker.
[UniqueError.NOT_UNIQUE @ lineItem.name; trigger:'ADvendio_Sport_Leaderboard'
There is already a line item with the same name existing at this Order in GAM
Change the Campaign Item Name in ADvendio or add a unique 7.3.12 Adserver Name for Campaign items.
[ProposalLineItemProgrammaticError.ZERO_COST_PER_UNIT_NOT_SUPPORTED @ .costPerUnit]
Depending on the AdServer Price field selected in GAM connection settings, ADvendio will try to submit that field as price to GAM. If the selected field is empty, then the error message will be displayed when you try to submit a proposal to GAM.
To change which price gets submitted to GAM, see: 220.127.116.11 Submit Prices to the AdServer
ReservationDetailsError.COST_TYPE_NOT_ALLOWED @ costType; trigger:'CPD'
CostType (BillingCategory) CPD is only available for LineItemType (AdType) Sponsorship and Network.
Change BillingCategory or the field AdType on the object AdType.
Forecasts are only available for LineItemTypes Sponsorship and Standard
Change AdType.AdType or CampaignItem.AdType
The operation is not allowed due to a lack of permissions in
Give more permissions to the
Ad server error, fault message: [ForecastingError.EXCEEDED_QUOTA @ ]
The number of requests made per second is too high and has exceeded the allowable limit. The recommended approach to handle this error is to wait about 5 seconds and then retry the request. Note that this does not guarantee the request will succeed. If it fails again, try increasing the wait time.
Another way to mitigate this error is to limit requests to 2 per second. Once again this does not guarantee that every request will succeed, but may help reduce the number of times you receive this error.
A child inventory unit cannot be targeted if its ancestor inventory unit is also targeted.
Remove the children Ad Server IDs of selected Ad Units from the Ad Spec. (Or remove selected content)
Could not upload Creative (CN-0) slot can not be parsed
The selected Slot Size at the Creative does not match with Slot Sizes of the AdServer.
Please make sure the slot sizes you've defined in your system follow this format "300x250"
RequiredNumberError.TOO_SMALL_WITH_DETAILS @ lineItem.primaryGoal.units; trigger:'0']
The primary goal (% of remaining/total impressions) set for Sponsorship, InHouse, or Network items does not fit.
Check the field Goal Percent at the Campaign Item, make sure it is not filled with 0. As default, if the field is empty 100% should be transferred to
When submitting to the adserver: This error happens because you have updated fields that affect delivery (i.e. targetings fields) for an Item, that is already active and delivering. There are fields like "notes" which don't affect the delivery numbers and you are be able to update those in your the line item without pausing.
To be sure not to create problems, it is safer to always pause the line item (CampaignItem > AdServer Status), make the update and then activate the line item again.
Similar to the error above this is returned, when trying to submit changes to a Campaign Item, that has already started running. In this particular case ADvendio tries to change the starting time of the item, which is not possible.
Please check if the fields from(hour) and from(minute) match the starting time of you line item in Google AdManager. In some rare cases there can be a mismatch in those. If that is the case, please change the values in ADvendio to match the values in Google, and then the submit should work.
Could not login to DFP: no Network Code set and more than one Network
GAM user name is connected to more than one network in
Please enter the according network ID into the AdServer Login record in ADvendio, to make sure the correct network is used.
Report data is only available for the last 3 years. Older Delivery Data will not be updated. (Message key: WARNING_START_DATE_TOO_LONG_AGO )
Your Campaign Item / Line Item has a runtime longer than three years. Due to limitations in the reporting API we can only import delivery data from the last three years into ADvendio.
To ensure the reporting numbers are still correct in total, please split your Campaign Item into separate items not running longer than three years.
Error: No key in KeyLine
There is a problem in the Keys and Values assigned to the Campaign Item (within ADvendio), resulting in incomplete information being transferred to the AdServer. This only affects the old Key Values not the new Lightning Key Value selection.
Remove all Key Values from the Campaign Item and assign them again. Try to submit the Campaign Item again.
[NotNullError.NULL @ 0.probabilityOfClose]
Your Order is missing the probability of close.
This is only relevant for Proposal Orders/Line Items in the Ad Manager Sales module, but the field is part of the old DSM module of Google (already deprecated). DSM will be deactivated in July 2019, if you want to test our Google Ad Manager integration of proposals and programmatic guaranteed, please use a newly created test network, where the DSM functionality is already deactivated.
Sponsorship: [FeatureError.MISSING_FEATURE @ lineItem.lineItemType; trigger:'LINE_ITEM_MINIMUM_QUANTITY']
Standard: [FeatureError.MISSING_FEATURE @ lineItem.lineItemType; trigger:'LINE_ITEM_CONTRACTED_QUANTITY']
For both fields in GAM (Minimum Quantity and Contracted Quantity) the feature needs to be activated within GAM. If the field is set for a Sponsorship or Standard item but not activated in the network the user will receive the following error message:
For an explanation of the GAM function have a look here at contracted Units Bought (which is the API name for the two fields in GAM):
GAM API Docu
[PrecisionError.WRONG_PRECISION @ .netCost; trigger:'19999929000']
This error can appear if the amount you are pushing to
GAM is either too small for the
GAM calculation. Please try to submit other values within the campaign item.
If you navigate to AdServer login, under Price Information, AdServer Price field, you can choose other value e.g Adserver Price. After selecting this option, Adserver Price under Campaign item must be set. Navigate to Campaign item, under Pricing Information, Adserver Price, enter the price value.(more info follow the link).
NullPointer (a value is missing)
An ID you are using for your Item (for example as targeting criteria) is not found in Google Ad Manager and thus the item could not be submitted.
Unfortunately, this error comes directly from the AdServer and leaves no indication where the problem is.
Please check the following things:
You have an agreement with Google to not submit those ads.
This warning from
GAM can be suppressed if you like to avoid the cross selling warning from
GAM. Mark the checkbox "skipCrossSellingRuleWarningChecks" on the line item to true to skip these warnings. These rules are applied to line items targeting inventory shared by a distributor partner for cross selling when performing any action on this line item. The default is false.
(No Ad Server Specified or it is inactive: null)
Our Gateway can not find which AdServer it needs to communicate with. The Item you're using is maybe not connected to an AdServer.
Check two things:
For your campaign item, has the connected AdType an AdServer Login entered?
If that is true, is the AdServer Login in ADvendio set to active? If inactive it will be ignored from our Gateway.
Relation between Billing Categories and Line Item Types (AdTypes)
These types are defined in the field AdType of the AdType referenced in your line item. For further reference read 3.1.5 Ad Type.