Error : "All partner audiences must have a country that matches the country targeted"

[TheoMMR]

Hello,

A client is wondering why he’s encountering this error when creating his campaign

Input

{
    "url": "https:\/\/ads-api.twitter.com\/2\/accounts\/18ce54lfwc1\/targeting_criteria",
    "method": "POST",
    "parameters": {
        "account_id": "18ce54lfwc1",
        "line_item_id": "blaqg",
        "targeting_type": "BEHAVIOR",
        "targeting_value": "pqgs"
    }
}

Output

{
    "errors": [
        {
            "code": "INVALID",
            "message": "All partner audiences must have a country that matches the country targeted: GB",
            "attribute": "targeting_type"
        }
    ],
    "request": {
        "params": {
            "line_item_id": "blaqg",
            "targeting_type": "BEHAVIOR",
            "targeting_value": "pqgs",
            "account_id": "18ce54lfwc1"
        }
    }
}

It looks like a targeting error, but we don’t understand what it occurs as everything is targeting GB.

Can you help us?

Thank you,

Theo

[TheoMMR]

Hello,

No answer since 11 days.

Can you update us?

Thank you,
Theo

[juanshishido]

Thanks for the question, @TheoMMR.

The behavior you are trying to target is US-based ("country_code": "US"):

$ twurl -H ads-api.twitter.com "/3/targeting_criteria/behaviors?behavior_ids=pqgs"
{
  "data": [
    {
      "name": "Walt Disney",
      "targetable_types": [
        "BEHAVIOR",
        "NEGATIVE_BEHAVIOR",
        "BEHAVIOR_LOOKALIKE_EXPANDED"
      ],
      "country_code": "US",
      "id": "pqgs",
      "partner_source": "Datalogix",
      "behavior_taxonomy_id": "2b",
      "audience_size": 2494710
    }
  ],
  "next_cursor": null,
  "request": {
    "params": {
      "behavior_ids": [
        "pqgs"
      ]
    }
  }
}

In January, we announced a few validation changes.

It looks like the line item is targeting locations in Great Britain while the behavior is for the US, which is why you see the error.

---

No answer since 11 days.

This was originally posted in the wrong category, so we didn’t get a notification. Thanks for following up!