@juanshishido thanks for the replay!
I read the article you provided and now understand what this feature is about, but it still doesn’t completely answer the question asked.
If I request account features through “GET accounts/:account_id/features” endpoint for our test account(id: 18ce54xoaww), I only receive account feature “UNIVERSAL_LOOKALIKE”.
TWURL request:
doment@llama:~$ twurl -H "https://ads-api.twitter.com" -X GET "/5/accounts/18ce54lkcqp/features" |json
{
"request": {
"params": {
"account_id": "18ce54lkcqp"
}
},
"data": [
"UNIVERSAL_LOOKALIKE"
]
}
When only a couple of weeks ago response features for this exact account were:
{
"data": [
"ALLOW_SKIPPABLE_VIDEOS_FOR_VIDEO_VIEWS_PREROLL_OBJECTIVE",
"CPI_CHARGING",
"INSTALLED_APP_CATEGORY_TARGETING",
"MOBILE_CONVERSION_TRANSACTION_VALUE",
"OPTIMIZED_ACTION_BIDDING",
"UNIVERSAL_LOOKALIKE",
"VIDEO_APP_DOWNLOAD_CARD"
]
}
I know that the account features didn’t change in the meantime, the only thing that has changed is the response.
We are using this endpoint constantly to keep track of features that accounts connected to our platform have, in order to determine which card/media types can be created whit this accounts. So we are having quite a few problems, whit this kind of response not providing features like “VIDEO_APP_DOWNLOAD_CARD”, “CONVERSATION_CARD”, etc.
The request/response I provided was for one of our accounts, but the response whit only “UNIVERSAL_LOOKALIKE” feature is appearing for almost every account connected to our platform.
Now my question is, why has the response changed. Is this a possible bug or is this a planned change?
Best regards,
Domen