ConstantDataService AgeRange Value Missing and Invalid as Criterion ID

[Mark Rogoyski]

Using ConstantDataService to get AgeRangeCriterion, you get the following list:

    <getAgeRangeCriterionResponse xmlns="https://adwords.google.com/api/adwords/cm/v201509">
      <rval>
        <id>503999</id>
        <Criterion.Type>AgeRange</Criterion.Type>
        <ageRangeType>AGE_RANGE_UNDETERMINED</ageRangeType>
      </rval>
      <rval>
        <id>503006</id>
        <Criterion.Type>AgeRange</Criterion.Type>
        <ageRangeType>AGE_RANGE_65_UP</ageRangeType>
      </rval>
      <rval>
        <id>503005</id>
        <Criterion.Type>AgeRange</Criterion.Type>
        <ageRangeType>AGE_RANGE_55_64</ageRangeType>
      </rval>
      <rval>
        <id>503004</id>
        <Criterion.Type>AgeRange</Criterion.Type>
        <ageRangeType>AGE_RANGE_45_54</ageRangeType>
      </rval>
      <rval>
        <id>503003</id>
        <Criterion.Type>AgeRange</Criterion.Type>
        <ageRangeType>AGE_RANGE_35_44</ageRangeType>
      </rval>
      <rval>
        <id>503002</id>
        <Criterion.Type>AgeRange</Criterion.Type>
        <ageRangeType>AGE_RANGE_25_34</ageRangeType>
      </rval>
      <rval>
        <id>503001</id>
        <Criterion.Type>AgeRange</Criterion.Type>
        <ageRangeType>AGE_RANGE_18_24</ageRangeType>
      </rval>
      <rval>
        <id>503000</id>
        <Criterion.Type>AgeRange</Criterion.Type>
      </rval>
    </getAgeRangeCriterionResponse>

The last value, ID 503000, does not contain an ageRangeType element. What age range does this correspond to? Unknown?

Also, when trying to use that AgeRange as a NegativeAdGroupCriterion, the following errors occurs:

[CriterionError.INVALID_CRITERION_ID @ operations[8].operand.criterion; trigger:'503000']

Is this the expected behavior? Using API v201509.

Thanks.

Mark

[Anthony Madrigal]

Hi Mark,

The ID 503000 refers to the age range "under 18", which was deprecated but is still available in reports. You cannot target this age range which may explain why you are getting that error.

Regards,

Anthony

AdWords API Team