<soapenv:Body>
<mutate xmlns="https://adwords.google.com/api/adwords/cm/v201809">
<operations>
<operator>ADD</operator>
<operand xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201809" xsi:type="ns2:BiddableAdGroupCriterion">
<adGroupId>102693046935</adGroupId>
<criterion xsi:type="ns2:ProductPartition">
<id>-1</id>
<partitionType>SUBDIVISION</partitionType>
</criterion>
</operand>
</operations>
<operations>
<operator>ADD</operator>
<operand xmlns:ns3="https://adwords.google.com/api/adwords/cm/v201809" xsi:type="ns3:BiddableAdGroupCriterion">
<adGroupId>102693046935</adGroupId>
<criterion xsi:type="ns3:ProductPartition">
<id>-2147483648</id>
<partitionType>UNIT</partitionType>
<parentCriterionId>-1</parentCriterionId>
<caseValue xsi:type="ns3:ProductCustomAttribute">
<type>CUSTOM_ATTRIBUTE_0</type>
</caseValue>
</criterion>
<biddingStrategyConfiguration>
<bids xsi:type="ns3:CpcBid">
<bid>
<microAmount>10000</microAmount>
</bid>
</bids>
</biddingStrategyConfiguration>
</operand>
</operations>
</mutate>
</soapenv:Body>
Hi Mitchell,
Thanks for the information. We tried that approach and the outcome does not quite line up with the “All products” setting when running through that flow on the Google Ads UI.
First screenshot below is the Google Ads UI end result, second screenshot is via the Adwords API. Any reason they are not consistent?


Google Ads API Team
ref:_00D1U1174p._5004Q20Xs1I:ref