Accounts Whitelisted in Twitter UI Are Not Whitelisted in API

whitelisting
api

#1

Hello,

We have noticed that 2 accounts are displayed as whitelisted for the website conversion objective in the native Twitter UI, but are not showing as whitelisted in the API. Please see the twurl and response below for details. Could we please whitelist these accounts for the website conversions objective in the API?

twurl -H ‘ads-api.twitter.com’ ‘/1/accounts/18ce53yaj83/features’ | jq
{
“request”: {
“params”: {
“account_id”: “18ce53yaj83”
}
},
“data_type”: “features”,
“data”: [
“AGE_TARGETING”,
“ALLOW_SKIPPABLE_VIDEOS_FOR_VIDEO_VIEWS_PREROLL_OBJECTIVE”,
“AWARENESS_OBJECTIVE”,
“CPI_CHARGING”,
“EVENT_TARGETING”,
“INSTALLED_APP_CATEGORY_TARGETING”,
“MOBILE_CONVERSION_TRANSACTION_VALUE”,
“OPTIMIZED_ACTION_BIDDING”,
“REACH_AND_FREQUENCY_ANALYTICS”,
“VALIDATED_AGE_TARGETING”,
“VIDEO_APP_DOWNLOAD_CARD”
]
}

twurl -H ‘ads-api.twitter.com’ ‘/1/accounts/azg6y/features’ | jq

{
“request”: {
“params”: {
“account_id”: “azg6y”
}
},
“data_type”: “features”,
“data”: [
“AGE_TARGETING”,
“ALLOW_SKIPPABLE_VIDEOS_FOR_VIDEO_VIEWS_PREROLL_OBJECTIVE”,
“AWARENESS_OBJECTIVE”,
“CPI_CHARGING”,
“EVENT_TARGETING”,
“INSTALLED_APP_CATEGORY_TARGETING”,
“MOBILE_CONVERSION_TRANSACTION_VALUE”,
“OPTIMIZED_ACTION_BIDDING”,
“REACH_AND_FREQUENCY_ANALYTICS”,
“VALIDATED_AGE_TARGETING”,
“VIDEO_APP_DOWNLOAD_CARD”
]
}


#2

Hi Allison,

I believe there’s a bug where some accounts are having access to this feature even when they are not supposed to, so this could be the same issue. To create the least amount of trouble for the advertiser do you mind trying to escalate about this via the partner manager or program manager you have contact with? I do not believe there is an issue with the API per se because based on settings it shouldn’t have access in the UI either.

Thanks,

John


#3

@allisonhyfn: You should be able to create a website conversions campaign for both of these accounts, even if you don’t see it in the response for the GET accounts/:account_id/features endpoint.


#4

Thanks for following up! Do you know if this is going to be added back into the /features endpoint in the future? We rely on this end point to dynamically enable/disable workflows in our app. Having to manually whitelist brands for website conversions on our side isn’t optimal.

Thanks,

Kevin


#5

Thanks for the follow-up, @hyfn, and for letting us know how you use the GET accounts/:account_id/features endpoint. The Website Conversions objective is available to all U.S.-based advertisers, without the need to be whitelisted. Does this information help alleviate some of the manual work on your side?


#6

Hi Juan,

Thank you, this helps! We’ll just look up the account location in the account details then.

Best,

Kevin