Hello!

I have a question regarding targeting criteria.
We don’t get TV_MARKET in response for targeting criteria for line item (GET /3/accounts/18ce54lkcqp/targeting_criteria?line_item_id=c67f0).
Also, you don’t accept TV_MARKET for create option (POST).
But we have to show TV_MARKET for creating option because it’s required for TV_SHOWS search.

So here is our problem:
We are importing your line items and targeting into our system. If a user wants to edit targeting, we don’t know how to show for which TV_MARKET TV_SHOW it is.

Regards, Aleksander

Sorry for the delay in replying here. You can retrieve list of possible tv markets by hitting this endpoint:

twurl -H ads-api.twitter.com '/3/targeting_criteria/tv_markets' | jsonpretty

This is documented on this page

Does that solve your issue?

Sorry for the late reply…

That doesn’t solve our problem.
We have no problems with the line item targeting creation.

We need TW_MARKET when we request line item targeting (GET /3/accounts/18ce54lkcqp/targeting_criteria?line_item_id=c67f0).
We can only get TW_SHOW.

We need this data for edit options.

Regards

Any news on this?

Regards, Aleksander

Some more info:

We cannot say that the MARKET is equal LOCATION

MARKET = United States - Hispanic
LOCATION = United States

REQUEST:
https://ads-api.twitter.com/3/accounts/18ce54lkcqp/targeting_criteria?line_item_id=c6gpc

RESPONSE:

array(3) {
  'request' =>
  array(1) {
    'params' =>
    array(2) {
      'account_id' =>
      string(11) "18ce54lkcqp"
      'line_item_id' =>
      string(5) "c6gpc"
    }
  }
  'next_cursor' =>
  NULL
  'data' =>
  array(8) {
    [0] =>
    array(10) {
      'line_item_id' =>
      string(5) "c6gpc"
      'name' =>
      string(28) "Desktop and laptop computers"
      'id' =>
      string(6) "jgipqv"
      'account_id' =>
      string(11) "18ce54lkcqp"
      'operator_type' =>
      string(2) "EQ"
      'created_at' =>
      string(20) "2018-07-31T13:18:33Z"
      'targeting_value' =>
      int(4)
      'updated_at' =>
      string(20) "2018-07-31T13:18:33Z"
      'deleted' =>
      bool(false)
      'targeting_type' =>
      string(8) "PLATFORM"
    }
    [1] =>
    array(10) {
      'line_item_id' =>
      string(5) "c6gpc"
      'name' =>
      string(3) "iOS"
      'id' =>
      string(6) "jgipqw"
      'account_id' =>
      string(11) "18ce54lkcqp"
      'operator_type' =>
      string(2) "EQ"
      'created_at' =>
      string(20) "2018-07-31T13:18:33Z"
      'targeting_value' =>
      int(0)
      'updated_at' =>
      string(20) "2018-07-31T13:18:33Z"
      'deleted' =>
      bool(false)
      'targeting_type' =>
      string(8) "PLATFORM"
    }
    [2] =>
    array(10) {
      'line_item_id' =>
      string(5) "c6gpc"
      'name' =>
      string(7) "Android"
      'id' =>
      string(6) "jgipqx"
      'account_id' =>
      string(11) "18ce54lkcqp"
      'operator_type' =>
      string(2) "EQ"
      'created_at' =>
      string(20) "2018-07-31T13:18:33Z"
      'targeting_value' =>
      int(1)
      'updated_at' =>
      string(20) "2018-07-31T13:18:33Z"
      'deleted' =>
      bool(false)
      'targeting_type' =>
      string(8) "PLATFORM"
    }
    [3] =>
    array(10) {
      'line_item_id' =>
      string(5) "c6gpc"
      'name' =>
      string(29) "BlackBerry phones and tablets"
      'id' =>
      string(6) "jgipqy"
      'account_id' =>
      string(11) "18ce54lkcqp"
      'operator_type' =>
      string(2) "EQ"
      'created_at' =>
      string(20) "2018-07-31T13:18:33Z"
      'targeting_value' =>
      int(2)
      'updated_at' =>
      string(20) "2018-07-31T13:18:33Z"
      'deleted' =>
      bool(false)
      'targeting_type' =>
      string(8) "PLATFORM"
    }
    [4] =>
    array(10) {
      'line_item_id' =>
      string(5) "c6gpc"
      'name' =>
      string(27) "Mobile web on other devices"
      'id' =>
      string(6) "jgipqz"
      'account_id' =>
      string(11) "18ce54lkcqp"
      'operator_type' =>
      string(2) "EQ"
      'created_at' =>
      string(20) "2018-07-31T13:18:33Z"
      'targeting_value' =>
      int(3)
      'updated_at' =>
      string(20) "2018-07-31T13:18:33Z"
      'deleted' =>
      bool(false)
      'targeting_type' =>
      string(8) "PLATFORM"
    }
    [5] =>
    array(11) {
      'line_item_id' =>
      string(5) "c6gpc"
      'name' =>
      string(13) "United States"
      'id' =>
      string(6) "kyl1ln"
      'account_id' =>
      string(11) "18ce54lkcqp"
      'location_type' =>
      string(9) "COUNTRIES"
      'operator_type' =>
      string(2) "EQ"
      'created_at' =>
      string(20) "2018-12-17T15:15:17Z"
      'targeting_value' =>
      string(16) "96683cc9126741d1"
      'updated_at' =>
      string(20) "2018-12-17T15:15:17Z"
      'deleted' =>
      bool(false)
      'targeting_type' =>
      string(8) "LOCATION"
    }
    [6] =>
    array(10) {
      'line_item_id' =>
      string(5) "c6gpc"
      'name' =>
      string(28) "Hispanic Heritage Month 2016"
      'id' =>
      string(6) "kyl1lo"
      'account_id' =>
      string(11) "18ce54lkcqp"
      'operator_type' =>
      string(2) "EQ"
      'created_at' =>
      string(20) "2018-12-17T15:15:17Z"
      'targeting_value' =>
      int(10045499011)
      'updated_at' =>
      string(20) "2018-12-17T15:15:17Z"
      'deleted' =>
      bool(false)
      'targeting_type' =>
      string(7) "TV_SHOW"
    }
    [7] =>
    array(10) {
      'line_item_id' =>
      string(5) "c6gpc"
      'name' =>
      string(24) "Mi Historia de Fantasmas"
      'id' =>
      string(6) "kyl1lp"
      'account_id' =>
      string(11) "18ce54lkcqp"
      'operator_type' =>
      string(2) "EQ"
      'created_at' =>
      string(20) "2018-12-17T15:15:17Z"
      'targeting_value' =>
      int(10028138971)
      'updated_at' =>
      string(20) "2018-12-17T15:15:17Z"
      'deleted' =>
      bool(false)
      'targeting_type' =>
      string(7) "TV_SHOW"
    }
  }
}

What we are missing is TV_MARKET targeting.

Is there any other way to get TV_MARKET value?

Hey @JBabichJapan any news on this?

Regards, Aleksander

OK, we found a solution.

No need for help anymore.

Regards, Aleksander

Hi @jancic_A - Extremely sorry for this post dropping off our radar!

The location values being a bit confusing to deal with is a known issue on our side.

Feel free to post details about the solution you found if you think it will be beneficial to others here.