Hi Hans,
In case others who are staying on v201409 a bit longer encounter this issue, we have added
forwardCompatibilityMap entries to
AdGroupCriterion and
CampaignCriterion.
For example, using v201409 to retrieve a campaign's
ProductScope criterion, you'll get something like this if the scope includes the new
ProductChannelExclusivity dimension type (this example is for
Channel Exclusivity = Multi channel):
<campaignId>123456</campaignId>
<isNegative>false</isNegative>
<id>78901234</id>
<type>PRODUCT_SCOPE</type>
<Criterion.Type>ProductScope</Criterion.Type>
</criterion>
<forwardCompatibilityMap>
<key>ProductScope.channel</key>
<value/>
</forwardCompatibilityMap>
<forwardCompatibilityMap>
<key>ProductScope.exclusivity</key>
<value>MULTI_CHANNEL</value>
</forwardCompatibilityMap>
<CampaignCriterion.Type>CampaignCriterion</CampaignCriterion.Type>
Similarly, when retrieving product partitions of an ad group using v201409, you'll get the following if a partition uses one of the new
ProductDimension types introduced in v201502:
<criterionUse>BIDDABLE</criterionUse>
<criterion xsi:type="ProductPartition">
<id>123456789</id>
<type>PRODUCT_PARTITION</type>
<Criterion.Type>ProductPartition</Criterion.Type>
<partitionType>UNIT</partitionType>
<parentCriterionId>60408125302</parentCriterionId>
</criterion>
<forwardCompatibilityMap>
<key>ProductPartition.exclusivity</key>
<value>NULL</value>
</forwardCompatibilityMap>
<forwardCompatibilityMap>
<key>ProductPartition.channel</key>
<value>LOCAL</value>
</forwardCompatibilityMap>
In both cases, the returned forwardCompatibilityMap.value will be one of LOCAL, ONLINE, or ALL.
Cheers,
Josh Radcliff, AdWords API Team