reach_estimate always returns count = 0



recently (last few days) it looks like the reach_estimate endpoint always returns count = 0.
We have tried with various parameter values for bit_type and bid_amount_local_micro but the results are the same, count is always 0.
BTW - the infinite bid count does change for example when we change the similar_to_followers_of_users value.


twurl -H “/0/accounts/xxxxxxxx/reach_estimate?product_type=PROMOTED_TWEETS&similar_to_followers_of_users=zzzzzzzz” | jq .
“request”: {
“params”: {
“account_id”: “xxxxxxxxx”,
“similar_to_followers_of_users”: [
“followers_of_users”: null,
“product_type”: “PROMOTED_TWEETS”
“data”: {
“infinite_bid_count”: 9370,
“count”: 0
“data_type”: “reach_estimate”



Thanks for bringing this up - this is a known issue that we are working on resolving internally! There is no timeline in particular as of now, but we are hoping to have some more information soon.


Got it @andrs. We will wait for updates on this one. Thanks.


@andrs It looks like this is resolved now. Our application is able to retrieve count for the reach_estimate end point.

Reach Estimate Question
Reach Estimate Question

I can confirm that this issue has now been resolved.

A bit of extra information in the context of using the GET accounts/:account_id/reach_estimate endpoint:

  • There are two fields in the response, count and infinite_bid_count. count is bid sensitive, so if the request does not specify bid_amount_local_micro, count in the response is always 0. infinite_bid_count is not bid sensitive, so it is like saying how much is your potential reach (regardless how much you bid).
  • Setting a specific objective, to anything other than CUSTOM, makes the reach estimation a lot more accurate. If objective is not set, reach estimation can only use historical data (last 30 days of activity) of the account to estimate the reach. If the account has been inactive for more than 30 days, reach estimation will return 0.


Great. Thanks!

closed #7