Reach Estimation using Keywords resulting in NOT_FOUND

reach-estimation

#1

I’ve noticed that reach_estimate seems to throw NOT_FOUND for seemingly normal keywords. This is particularly troublesome because it occurs on keywords that are given as suggestions. Below is a simple example. I’ve run into this issue a lot when adding lots of suggested keywords. Is there some way to avoid this or to identify problem strings?



twurl -H 'ads-api.twitter.com' '/1/accounts/4no6av/reach_estimate?product_type=PROMOTED_TWEETS&bid_amount_local_micro=150000&currency=USD&campaign_daily_budget_amount_local_micro=550000&objective=TWEET_ENGAGEMENTS&broad_keywords=hehez' | python -m json.tool
{
    "errors": [
        {
            "code": "NOT_FOUND",
            "message": "Keyword(s) hehez was not found"
        }
    ],
    "request": {
        "params": {}
    }
}

#2

Hi, @BrianGathright. Thanks for your question. Where are you finding these suggested keywords? What other keywords are you receiving the NOT_FOUND error for?


#3

Hi @juanshishido. The suggestions are coming from https://ads-api.twitter.com/1/accounts/:account_id/targeting_suggestions.

I’m receiving it for various keywords.

Here’s an example:

This is the suggestions I get

{"responses": [{"data": {"data": [{"suggestion_type": "KEYWORD", "suggestion_value": "macdailynews macdailynews"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#imagazine #apple"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#wwdc2016"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#teknodigie"}, {"suggestion_type": "KEYWORD", "suggestion_value": "apple's"}, {"suggestion_type": "KEYWORD", "suggestion_value": "appl"}, {"suggestion_type": "KEYWORD", "suggestion_value": "wwdc"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#appleevent #applelive"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#webjobbing"}, {"suggestion_type": "KEYWORD", "suggestion_value": "comapple"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#buyapplewatch"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#appleinvestor"}, {"suggestion_type": "KEYWORD", "suggestion_value": "appleinsider"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#applenews"}, {"suggestion_type": "KEYWORD", "suggestion_value": "applenws"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#applekeynote"}, {"suggestion_type": "KEYWORD", "suggestion_value": "apples"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#macrumours"}, {"suggestion_type": "KEYWORD", "suggestion_value": "ipad"}, {"suggestion_type": "KEYWORD", "suggestion_value": "insider #yummyapple"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#appleinc"}, {"suggestion_type": "KEYWORD", "suggestion_value": "nasdaq aapl"}, {"suggestion_type": "KEYWORD", "suggestion_value": "waxeditorial"}, {"suggestion_type": "KEYWORD", "suggestion_value": "@apple"}, {"suggestion_type": "KEYWORD", "suggestion_value": "rsgnl"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#aapl_company"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#iphonedownloadblog"}, {"suggestion_type": "KEYWORD", "suggestion_value": "aapl"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#newiphone"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#apple_watch"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#appleiphone"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#aapl"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#appleevent"}, {"suggestion_type": "KEYWORD", "suggestion_value": "discontinues thunderbolt"}, {"suggestion_type": "KEYWORD", "suggestion_value": "julipuli"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#macumors #mac"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#modmyi"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#sienco"}, {"suggestion_type": "KEYWORD", "suggestion_value": "@appleinsider"}, {"suggestion_type": "KEYWORD", "suggestion_value": "iphones"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#appleinsider"}, {"suggestion_type": "KEYWORD", "suggestion_value": "@kylesethgray"}, {"suggestion_type": "KEYWORD", "suggestion_value": "iphone"}, {"suggestion_type": "KEYWORD", "suggestion_value": "appdevelopmenttrends"}, {"suggestion_type": "KEYWORD", "suggestion_value": "startup"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#iphone"}, {"suggestion_type": "KEYWORD", "suggestion_value": "ios"}, {"suggestion_type": "KEYWORD", "suggestion_value": "family"}, {"suggestion_type": "KEYWORD", "suggestion_value": "sports"}, {"suggestion_type": "KEYWORD", "suggestion_value": "#apple #thedab"}]}, "status_code": 200}]}

And this is what I get when I try to use all those suggestions for reach_estimate

{"responses": [{"data": {"errors": [{"code": "NOT_FOUND", "message": "Keyword(s) julipuli,discontinues thunderbolt,#apple #thedab,waxeditorial,#webjobbing,comapple,nasdaq aapl,@kylesethgray was not found"}], "request": {"params": {}}}, "status_code": 404}]}

If you do a twurl with any of the keywords that it says are not found, you get the same error. But they were given as suggestions in the first place.

For example with ‘nasdaq aapl’ which was given as a suggestion above,

twurl -H 'ads-api.twitter.com' '/1/accounts/4no6av/reach_estimate?product_type=PROMOTED_TWEETS&bid_amount_local_micro=150000&currency=USD&campaign_daily_budget_amount_local_micro=550000&objective=TWEET_ENGAGEMENTS&broad_keywords=nasdaq aapl' | python -m json.tool
{
    "errors": [
        {
            "code": "NOT_FOUND",
            "message": "Keyword(s) nasdaq aapl was not found"
        }
    ],
    "request": {
        "params": {}
    }
}

#5

Thanks, @BrianGathright. This is helpful. We’ll look into this issue.


#6

@BrianGathright: Thanks again for bringing this to our attention. We’re investigating this as a bug and will let you know as soon as we have an update. Apologies for the inconvenience with this.