Account not Whitelisted for age targeting through the API, but is through UI

[citizennet]

Hello,

We are running into a rather strange scenario - when we try to upload targeting containing age targeting to account 18ce548eg8o we are getting a permissions error.

Url: ( Urlencoded)

https://ads-api.twitter.com/1/accounts/18ce548eg8o/targeting_criteria?line_item_id=5u250&age_buckets=AGE_18_TO_24%2CAGE_25_TO_34&similar_to_followers_of_users=3161634606%2C49717874%2C16638685%2C2855922708%2C156132825%2C38802447%2C210921551%2C238319766%2C229943617%2C112747576%2C138600717%2C96846955%2C262799542%2C63302020%2C442237496%2C23151437%2C317522823%2C80700514&locations=96683cc9126741d1&tv_shows=10034591837%2C10031660235%2C10000268995%2C10037601822%2C10000289880%2C10000491439%2C10014230596%2C10000614447%2C10020966526%2C10032318912

and we get this error: {“errors”: [{“message”: “Age Targeting is not allowed on this account”, “code”: “AGE_TARGETING_NOT_ALLOWED”}], “request”: {“params”: {}}}

but we were able to make the same campaign in the same account through the Twitter UI without issues:

https://ads.twitter.com/accounts/18ce548eg8o/campaigns_dashboard?campaign=9432029&start=1470169320

Any help would be appreciated.

Thanks!

[juanshishido]

Hi, @citizennet. Thanks for the question.

Have you taken a look at the GET accounts/:account_id/features endpoint? Do you see AGE_TARGETING listed for 18ce548eg8o? If so, do you still get the same error with your original request?

[carmenjyuen]

Hi @citizennet ,

You should be able to ask the account manager of your client to whitelist for this feature.

I went ahead and submitted an internal ticket to get that account whitelisted. Will update once I hear more!
Carmen

[msbukkuri]

I’m having the same problem here. The API endpoint is showing us that the account does not have access to age targeting. But the Twitter Ads UI has it. The account manager has already whitelisted the feature.

Here is the Twurl:
twurl -X "GET" -H "ads-api.twitter.com" "/1/accounts/v7lr2/features" | python -m json.tool

Here are the results:

    "data": [
        "ALLOW_SKIPPABLE_VIDEOS_FOR_VIDEO_VIEWS_PREROLL_OBJECTIVE",
        "CPI_CHARGING",
        "ENGAGER_RETARGETING",
        "EVENT_TARGETING",
        "INSTALLED_APP_CATEGORY_TARGETING",
        "MOBILE_CONVERSION_TRANSACTION_VALUE",
        "OPTIMIZED_ACTION_BIDDING",
        "VIDEO_APP_DOWNLOAD_CARD"
    ],
    "data_type": "features",
    "request": {
        "params": {
            "account_id": "v7lr2"
        }
    }

Notice that there is no ‘AGE_TARGETING’?

Now, observe the Twitter Ads UI for the same account:

It looks like it only happens on certain accounts, such as the the one show above. Please advise.

[juanshishido]

Really appreciate the detailed information, @msbukkuri!

Could you please list all of this accounts this is affecting? We’ll work to get this resolved for all of them. Thanks.

[citizennet]

Hey Juan,

Similar to what msbukkuri is saying we did check the GET accounts/:account_id/features endpoint and verified that the account does not show as whitelisted, but we can add age targeting through the UI. We spoke with a Twitter account manager and they verified through the system that they used that we are verified, so to the best of our knowledge right now there is some discrepancy in whitelisting between the UI and API.

Thanks!

[msbukkuri]

@juanshishido
Account IDs: “18ce53xpwcy”, “59law”, “18ce53ynyeg”, “g5m3dv”, “qfd9fa”, “18ce548nbn1”, “18ce54ai5ks”, “18ce54748xn”, “dhojf”, “18ce54astbf”, “40y8z7”, “v7lr2”, “18ce54d59c9”

Here are all of the accounts that we see don’t have AGE_TARGETING. Please let me know if you need any additional details.

[carmenjyuen]

HI @citizennet,

I got confirmation at 11:01 AM PST that you were whitelisted.

Can you try again and let us know if you are still seeing the error?

Thanks,
Carmen

[juanshishido]

Thanks, @msbukkuri! We’ll work on fixing the ones that have been whitelisted for age targeting. Will update you once this is done.

[msbukkuri]

Thanks for jumping on this, appreciate it.

[juanshishido]

@msbukkuri: Age targeting via the API should now be enabled for v7lr2 and 18ce54d59c9. Could you please confirm whether you are able to add age-based targeting criteria to line items associated with those accounts?

It looks like the other accounts you listed do not have any age targeting whitelisted—no age targeting via UI or API. If you need this, please contact your account manager(s).

[msbukkuri]

18ce54d59c9

I can confirm that this is fixed now, thanks. Here is the confirmation:

twurl -X "GET" -H "ads-api.twitter.com" "/1/accounts/v7lr2/features" | python -m json.tool                                                                                                        
{
    "data": [
        "AGE_TARGETING",
        "ALLOW_SKIPPABLE_VIDEOS_FOR_VIDEO_VIEWS_PREROLL_OBJECTIVE",
        "CPI_CHARGING",
        "ENGAGER_RETARGETING",
        "EVENT_TARGETING",
        "INSTALLED_APP_CATEGORY_TARGETING",
        "MOBILE_CONVERSION_TRANSACTION_VALUE",
        "OPTIMIZED_ACTION_BIDDING",
        "VIDEO_APP_DOWNLOAD_CARD"
    ],
    "data_type": "features",
    "request": {
        "params": {
            "account_id": "v7lr2"
        }
    }


twurl -X "GET" -H "ads-api.twitter.com" "/1/accounts/18ce54d59c9/features" | python -m json.tool                                                                                                   
    "data": [
        "AGE_TARGETING",
        "ALLOW_SKIPPABLE_VIDEOS_FOR_VIDEO_VIEWS_PREROLL_OBJECTIVE",
        "CPI_CHARGING",
        "ENGAGER_RETARGETING",
        "EVENT_TARGETING",
        "INSTALLED_APP_CATEGORY_TARGETING",
        "MOBILE_CONVERSION_TRANSACTION_VALUE",
        "OPTIMIZED_ACTION_BIDDING",
        "VIDEO_APP_DOWNLOAD_CARD"
    ],
    "data_type": "features",
    "request": {
        "params": {
            "account_id": "18ce54d59c9"
        }

[citizennet]

Verified that there is now age targeting on 18ce548eg8o - thank you for the help!

Is there anything we can do on our side to prevent this from happening moving forward?

[juanshishido]

Great to hear, @citizennet!

Nothing to do on your end. Thanks!

[msbukkuri]

@citizennet Tag @juanshishido’s answer as the solution!

[imit8me]