Announcement: Available Age Targeting Buckets

announcements
targeting

#1

Today we are announcing two changes to age targeting that will allow our advertisers to more accurately target users, giving campaigns additional reach and scale.

We will be:

  1. Introducing a new set of age buckets with higher validated quality and
  2. Deprecating some of the existing age buckets that had disproportionately low coverage.

The new set of age buckets include 16 options, which expand upon the four already supported (for a total of 20), and will be available via the API immediately. The complete set of age targeting enums are shown below:

  • AGE_13_TO_24
  • AGE_13_TO_34
  • AGE_13_TO_49
  • AGE_13_TO_54
  • AGE_OVER_13
  • AGE_18_TO_34 (existing)
  • AGE_18_TO_49 (existing)
  • AGE_18_TO_54
  • AGE_OVER_18
  • AGE_21_TO_34
  • AGE_21_TO_49
  • AGE_21_TO_54
  • AGE_OVER_21 (existing)
  • AGE_25_TO_49
  • AGE_25_TO_54 (existing)
  • AGE_OVER_25
  • AGE_35_TO_49
  • AGE_35_TO_54
  • AGE_OVER_35
  • AGE_OVER_50

To check whether you have access to these age targeting options, make a request to the GET accounts/:account_id/features endpoint. The VALIDATED_AGE_TARGETING feature indicates access to these 20 age buckets.

We will be deprecating the following, less accurate age buckets:

  • AGE_13_TO_17
  • AGE_18_TO_24
  • AGE_25_TO_34
  • AGE_35_TO_44
  • AGE_45_TO_54
  • AGE_55_TO_64
  • AGE_OVER_65

These correspond to the AGE_TARGETING account feature.

This will take effect on 2016-12-31. Until this date, existing line items targeting these age groups will continue to serve. However, once these buckets reach their end of life, this will no longer be the case.

The Ads Enumeration page has been updated to reflect these changes.


Age targeting not working for an account
Announcement: Age targeting GA
Does analytics segmentation by AGE require AGE_TARGETING account feature?
Age targeting
AGE Targeting Support in the future
Age Targeting
AGE_BUCKET Targeting criterion with value 'AGE_21_TO_34' is not allowed for account
AGE_BUCKET Targeting criterion with value 'AGE_21_TO_34' is not allowed for account
#2

#3

#4

It is no longer possible to create targeting criteria using the less accurate age buckets. Trying to do so will result in the following error:

$ twurl -X POST -H ads-api.twitter.com "/1/accounts/18ce54d4x5t/targeting_criteria?line_item_id=6ynlo&targeting_type=AGE&targeting_value=AGE_13_TO_17" | jq
{
  "errors": [
    {
      "code": "INVALID_PARAMETER",
      "message": "Expected a value in AGE_13_TO_24, AGE_13_TO_34, AGE_13_TO_49, AGE_13_TO_54, AGE_18_TO_34, AGE_18_TO_49, AGE_18_TO_54, AGE_21_TO_34, AGE_21_TO_49, AGE_21_TO_54, AGE_25_TO_49, AGE_25_TO_54, AGE_35_TO_49, AGE_35_TO_54, AGE_OVER_13, AGE_OVER_18, AGE_OVER_21, AGE_OVER_25, AGE_OVER_35, AGE_OVER_50, got \"AGE_13_TO_17\" for targeting_value",
      "parameter": "targeting_value"
    }
  ],
  "request": {
    "params": {
      "line_item_id": "6ynlo",
      "targeting_type": "AGE",
      "account_id": "18ce54d4x5t"
    }
  }
}

#5

Please also note that the VALIDATED_AGE_TARGETING account feature is required to retrieve stats segmented by age via the API. Otherwise, you’ll see the following error message: "Segmentation by AGE is not allowed on this account".