reach-estimation
Reach estimate with keywords not working
[
Advertiser Tools and APIs
]
(2)
Inconsistency between age buckets OVER_18 and OVER_21 in reach estimation
[
Advertiser Tools and APIs
]
(4)
Reach estimate for TV targeting
[
Advertiser Tools and APIs
]
(2)
Reach estimate is inconsistent
[
Advertiser Tools and APIs
]
(4)
Tailored Audience Reach Estimate is 0
[
Advertiser Tools and APIs
]
(3)
Reach & frequency calls return authentication error despite our REACH_AND_FREQUENCY_ANALYTICS whitelist
[
Advertiser Tools and APIs
]
(4)
Reach - New Campaign Objective
[
Advertiser Tools and APIs
]
(14)
Reach Estimation using Keywords resulting in NOT_FOUND
[
Advertiser Tools and APIs
]
(6)
Reach estimate returns error with a valid geo location id
[
Advertiser Tools and APIs
]
(13)
Geo Location id, related to getting a reach estimate
[
Advertiser Tools and APIs
]
(3)
Dev Suggestions for Keywords
[
Advertiser Tools and APIs
]
(3)
New targeting options for reach estimation
[
Advertiser Tools and APIs
]
(2)
Reach estimate v0-v1 result differences
[
Advertiser Tools and APIs
]
(1)
How to get twitter impressions via API for single tweet?
[
REST API
]
(2)
Reach Estimate endpoint requiring for 2 Countries. Is this valid?
[
Advertiser Tools and APIs
]
(3)
How to get reach of a tweet using API?
[
REST API
]
(2)
reach_estimate always returns count = 0
[
Advertiser Tools and APIs
]
(7)
Estimated Audience Size (TwitterAds Campaign)
[
Advertiser Tools and APIs
]
(4)
next page →
Developers
Documentation
Forums
Events
Blog
Forums
