use AdGroupCriterionService set Gender and agerang and so on is sucessful but no effect? why? version:201802

[jia zheng]

I use AdGroupCriterionService set Gender and agerang and  so on is sucessful but no effect with 201802 API .So, I going to compare to sucessful and  effect ads data with my fail ads data. then I foud that different settings in the entity AdGroupService 。in the success ads ,the settings in AdGroupService is use ExplorerAutoOptimizerSetting ,and in the fail ads ,the settings in AdGroupService is default use  TargetingSetting with all  details criterionTypeGroup is true! So,I thougth is that the reson to fail.and then,I updata the setting make to the same with sucess ads setting .but fail with TARGETING_SETTING_CANNOT_CHANGE_TARGET_ALL_TO_FALSE_FOR_DEMOGRAPHIC_CRITERION_TYPE_GROUP.SO,I set false at ADD opreration,but it agein with fail TARGETING_SETTING_DEMOGRAPHIC_CRITERION_TYPE_GROUPS_MUST_BE_SET_TO_TARGET_ALL....emmm.So,I don't konw how to do.I is only want to public ads whit gender!Can't you help me?

[Bharani Cherukuri (AdWords API Team)]

Hello, 

The TARGETING_SETTING_CANNOT_CHANGE_TARGET_ALL_TO_FALSE_FOR_DEMOGRAPHIC_CRITERION_TYPE_GROUP error is seen when you're trying to change the Demographic criteria groups like Age, Gender, Parent, Income Range from true to false. Starting from v201802, you will not be able to set the TargetAll from true to false. 

As for the second error: TARGETING_SETTING_DEMOGRAPHIC_CRITERION_TYPE_GROUPS_MUST_BE_SET_TO_TARGET_ALL error is seen when you're explicitly setting the Targeting setting for the Demographic criteria (Age, Gender, Parent, Income Range) to false. For all the demographic criteria, you will need to set the TargetAll setting to true. 

Let me know if you have any other questions. 

Regards,

Bharani, AdWords API Team

[jia zheng]

i see what you mean.but why my adsgroup is Cannot show based on gender？what can i do? i was use adgroupcriterionserver  to set gender is id is "10".But all genders are running！

[Dannison Yao (AdWords API Team)]

Hi,

I am a colleague of Bharani, allow me to assist you with your concern as she is OOO today. Could you confirm if you are setting the gender properly? If you think you have set it properly, kindly provide us a UI screenshot or your SOAP request and response logs via Reply privately to author for further investigation.

If what you wish to do is to retrieve the gender object you created, you could do this by using this link as your guide, but instead of using the Keyword criterion, you should instead use the Gender criterion and modify the fields that would cater the Gender criterion. 

You could also use reports, specifically the Gender Performance Report to get the statistics for simplicity.. Hope this helps.

Regards,

Dannison

AdWords API Team

[jia zheng]

Hi,dear Dannison Yao.In the AdGroup ,I was only set name,status.In the AdGroupCriterionService,I send soap is that:

"<x:Envelope xmlns:x="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v="https://adwords.google.com/api/adwords/cm/v201802" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><x:Header><v:RequestHeader><v:clientCustomerId>********</v:clientCustomerId><v:developerToken>*********</v:developerToken><v:userAgent>test</v:userAgent><v:validateOnly>false</v:validateOnly><v:partialFailure>false</v:partialFailure></v:RequestHeader></x:Header><x:Body> <v:mutate> <v:operations> <v:operator>ADD</v:operator> <v:operand xmlns:ns1="https://adwords.google.com/api/adwords/cm/v201802" xsi:type="ns1:BiddableAdGroupCriterion"> <v:adGroupId>55997138856</v:adGroupId> <v:criterion xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201802" xsi:type="ns2:Gender"> <v:id>10</v:id> </v:criterion> </v:operand> </v:operations> </v:mutate></x:Body></x:Envelope>"

there is response for my request:

<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

  <soap:Header>

    <ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201802">

      <requestId>00056d4e06840bb90aa784cd460295c9</requestId>

      <serviceName>AdGroupCriterionService</serviceName>

      <methodName>mutate</methodName>

      <operations>1</operations>

      <responseTime>262</responseTime>

    </ResponseHeader>

  </soap:Header>

  <soap:Body>

    <mutateResponse xmlns="https://adwords.google.com/api/adwords/cm/v201802">

      <rval>

        <ListReturnValue.Type>AdGroupCriterionReturnValue</ListReturnValue.Type>

        <value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="BiddableAdGroupCriterion">

          <adGroupId>55997138856</adGroupId>

          <criterion xsi:type="Gender">

            <id>10</id>

            <type>GENDER</type>

            <Criterion.Type>Gender</Criterion.Type>

            <genderType>GENDER_MALE</genderType>

          </criterion>

          <AdGroupCriterion.Type>BiddableAdGroupCriterion</AdGroupCriterion.Type>

          <userStatus>ENABLED</userStatus>

          <systemServingStatus>ELIGIBLE</systemServingStatus>

          <approvalStatus>APPROVED</approvalStatus>

          <biddingStrategyConfiguration>

            <biddingStrategyType>MANUAL_CPC</biddingStrategyType>

            <biddingStrategySource>CAMPAIGN</biddingStrategySource>

            <biddingScheme xsi:type="ManualCpcBiddingScheme">

              <BiddingScheme.Type>ManualCpcBiddingScheme</BiddingScheme.Type>

              <enhancedCpcEnabled>false</enhancedCpcEnabled>

            </biddingScheme>

            <bids xsi:type="CpcBid">

              <Bids.Type>CpcBid</Bids.Type>

              <bid>

                <ComparableValue.Type>Money</ComparableValue.Type>

                <microAmount>10000</microAmount>

              </bid>

              <cpcBidSource>ADGROUP</cpcBidSource>

            </bids>

            <bids xsi:type="CpmBid">

              <Bids.Type>CpmBid</Bids.Type>

              <bid>

                <ComparableValue.Type>Money</ComparableValue.Type>

                <microAmount>10000</microAmount>

              </bid>

              <cpmBidSource>ADGROUP</cpmBidSource>

            </bids>

          </biddingStrategyConfiguration>

        </value>

      </rval>

    </mutateResponse>

  </soap:Body>

</soap:Envelope>

I get the adGroupCriterion like this:

[

  {

    "$": {

      "xmlns:xsi": "http://www.w3.org/2001/XMLSchema-instance",

      "xsi:type": "BiddableAdGroupCriterion"

    },

    "adGroupId": [

      "*********"

    ],

    "criterionUse": [

      "BIDDABLE"

    ],

    "criterion": [

      {

        "$": {

          "xsi:type": "Gender"

        },

        "id": [

          "11"

        ],

        "type": [

          "GENDER"

        ],

        "Criterion.Type": [

          "Gender"

        ],

        "genderType": [

          "GENDER_MALE"

        ]

      }

    ],

    "baseCampaignId": [

      "********"

    ],

    "baseAdGroupId": [

      "*********"

    ],

    "AdGroupCriterion.Type": [

      "BiddableAdGroupCriterion"

    ],

    "userStatus": [

      "ENABLED"

    ],

    "biddingStrategyConfiguration": [

      {

        "biddingStrategyType": [

          "TARGET_CPA"

        ],

        "bids": [

          {

            "$": {

              "xsi:type": "CpcBid"

            },

            "Bids.Type": [

              "CpcBid"

            ],

            "bid": [

              {

                "ComparableValue.Type": [

                  "Money"

                ],

                "microAmount": [

                  "10000"

                ]

              }

            ],

            "cpcBidSource": [

              "ADGROUP"

            ]

          }

        ]

      }

    ]

  }

]

it look like sucessful but why does not work?

[Dannison Yao (AdWords API Team)]

Hi,

My apologies for the delayed response as I discussed this issue with the rest of the team. The targeting types seem to be a factor in this issue. Upon investigation, if you create an ad group via AdWords API, the gender demographic/s TargettingSettingDetail.targetAll is set to TRUE by default as stated in the migration notes. However, when you create the ad group via AdWords UI, there is no targetAll value being set for the gender demographic. This could be the factor why the Gender is not reflected on the UI after it is set to specifically target only Males using the Adwords API. Allow us to further investigate on this issue for now and will update you about this.

[jia zheng]

Ok, waiting for your good news,thank you very much！

[Dannison Yao (AdWords API Team)]

Hi,

My apologies for the late response. The team has discussed a workaround solution for this via API. Instead of using the BiddableAdGroupCriterion object and making MALE to be the only target, you can use NegativeAdGroupCriterion to remove the rest of the genders (FEMALE, UNKNOWN) as target to make MALE the only positive target. 

Let me know if you have further clarifications.

[jia zheng]

Hello, what do you mean is that if you choose a partial gender, the alternative is to use exclusion? It is an effective alternative to use. I can think of the following priorities: NegativeAdGroupCriterion>adGroups.setting>BiddableAdGroupCriterion? But because GENDER, AGE_RANGE, PARENT, INCOME_RANGE are all set by default to modify adGroups.setting to targetAll=true. To use the above demographics, I have to use NegativeAdGroupCriterion Delete features I don't need?

[Dannison Yao (AdWords API Team)]

Hi,

This has nothing to do with the targetAll setting, if you want to exclude a criterion, just use NegativeAdGroupCriterion object to exclude the criterion you don't need. You can use this sample as a reference in using NegativeAdGroupCriterion. 

This also applies to the other demographics like AgeRange, Parent and Keyword. You can check other targeting types that are applicable to NegativeAdGroupCriterion in here.