We understand that the shift to ranges may be challenging for some to implement by October 27, 2021. As such, through November 15, we will continue to make available a single-point estimate as an additional endpoint.
The following changes apply to potential reach for all versions:
The name of potential reach is changing to estimated audience size . Estimated audience size generally estimates how many people meet the targeting and ad placement criteria that advertisers select while creating an ad. Learn more about reach estimate .
The definition of the reachestimate
API
has changed from Get an estimated number of individuals for your targeting and what bids to make to reach that target group with the /reachestimate API
to Get a range of individuals for your targeting and what bids to make to reach that target group with the /reachestimate API
.
The GET /{act_ad-account-id}/reachestimate
endpoint has two new fields: users_lower_bound
and users_upper_bound
.
On October 27, 2021, the users
field will be deprecated.
The following changes apply to delivery estimate for all versions:
The GET /{adset-id}/delivery_estimate
endpoint has two new fields: estimate_mau_lower_bound
and estimate_mau_upper_bound
.
The GET /{ad-account-id}/delivery_estimate
endpoint has two new fields: estimate_mau_lower_bound
and estimate_mau_upper_bound
.
The GET /{ad-account-id}/adsets
endpoint has two new fields: estimate_mau_lower_bound
and estimate_mau_upper_bound
.
On October 27, 2021, the estimate_mau
field will be deprecated.
The following changes apply to reach & frequency for all versions and only applied for predictions created after October 29, 2021 onward. Old predictions won't show any size after November 15, 2021.
The GET /{act_ad-account-id}/reachfrequencypredictions
endpoint has two new fields: audience_size_lower_bound
and audience_size_upper_bound
.
The GET /{act_ad-account-id}/ReachFrequencyPrediction
endpoint has two new fields: audience_size_lower_bound
and audience_size_upper_bound
.
On October 27, 2021, the target_audience_size
field will be deprecated.
The following changes apply to detailed targeting for all versions:
The GET /{act_ad-account-id}/targetingsearch
endpoint has two new fields: audience_size_lower_bound
and audience_size_upper_bound
.
The GET /{act_ad-account-id}/targetingbrowse
endpoint has two new fields: audience_size_lower_bound
and audience_size_upper_bound
.
The GET /{act_ad-account-id}/targetingsuggestions
has two new fields: audience_size_lower_bound
and audience_size_upper_bound
.
The GET /{act_ad-account-id}/targetingvalidation
has two new fields: audience_size_lower_bound
and audience_size_upper_bound
.
On October 27, 2021, the audience_size
field will be deprecated.
The following changes apply to custom broad category targeting for all versions:
The GET /{act_ad-account-id}/broadtargetingcategories
endpoint has two new fields: size_lower_bound
and size_upper_bound
. See also Custom Broad Category Targeting, example
.
On October 27, 2021, the size
field will be deprecated.
The following changes apply to custom audience for all versions:
GET /search/customaudience
endpoint has two new fields: approximate_count_lower_bound
and `approximate_count_upper_bound.The GET /{act_ad-account-id}/customaudiences
endpoint has two new fields: approximate_count_lower_bound
and approximate_count_upper_bound
.
The GET /savedaudience
endpoint has two new fields: approximate_count_lower_bound
and approximate_count_upper_bound
.
On October 27, 2021, the approximate_count
field will be deprecated.
The following change applies to search for all versions:
The GET /search/adinterest
endpoint has two new fields: audience_size_lower_bound
and audience_size_upper_bound
.
On October 27, 2021, the audience_size
field will be deprecated.
For more details, see the Facebook for Business blog and the About Estimated Audience Size, Business Help Center .