criteria_payload | object or string | Yes | - | Native Microsoft request body as an object or JSON string; nested fields are forwarded unchanged. Use CriterionType=Audience for audience associations, Targets for location/demographic/schedule criteria, or the appropriate native type. Up to 1,000 criteria per request. Add a custom segment: {“CriterionType”:“Audience”,“AdGroupCriterions”:[{“Type”:“BiddableAdGroupCriterion”,“AdGroupId”:123,“Status”:“Paused”,“Criterion”:{“Type”:“AudienceCriterion”,“AudienceId”:456},“CriterionBid”:{“Type”:“BidMultiplier”,“Multiplier”:0}}]}. Update: same shape with the association Id and only fields to change, e.g. Status=“Active”. Remove: {“AdGroupId”:123,“AdGroupCriterionIds”:[789],“CriterionType”:“Audience”}. Custom segments support biddable ad-group associations. Use update_ad_group Settings to configure TargetAndBid; adding an association does not change targeting mode. For product partitions always use microsoft_ads_update_product_partitions instead. Microsoft validates nested fields. |