An estimated audience describes accounts that may fit selected controls and signals; actual reach is the number of people who were served an ad. They answer different questions. Delivery also depends on budget, schedule, bid strategy, objective, creative quality, competition, predicted action rate, placements, and eligibility. This lesson turns an attractive planning number into a documented test instead of a forecast presented as certainty.
VISUAL LESSON
What you will learn
- 01Distinguish audience estimate, impressions, and reach.
- 02Build a transparent planning range.
- 03Diagnose why delivered reach differs from the plan.
ILLUSTRATIVE WORKED EXAMPLE
Turn one planning estimate into three scenarios
PRACTICAL INTERFACE MAP
Move from audience controls to a measured result
Save geography, age, audience inputs, exclusions, objective, placements, budget, schedule, and timestamp.
Approve a spend and observation period; log material edits that can change delivery.
Read unique reach, impressions, frequency, spend, outcomes, and auction or policy warnings together.
STEP-BY-STEP LESSON
Eligible audience → auction conditions → delivered reach → business result
THE LEAD ATLAS METHOD
Lead Atlas Data can build a done-for-you contact list around the exact industries, locations, and campaign market you want to reach, giving the plan a direct prospecting lane that does not depend on an estimated Facebook audience.See how custom list research works ↗Name each number correctly
Document the estimated audience shown during setup as a point-in-time planning signal, not a list of guaranteed recipients. Define reach as unique people served, impressions as total times ads were served, and frequency as impressions divided by reach for the selected reporting window.
Attach the estimate to its exact configuration and timestamp. A changed location, age control, exclusion, audience suggestion, placement, objective, schedule, or account setting creates a different estimate, so do not compare unlabeled screenshots.
Write the auction assumptions
Record the outcome being optimized, conversion location, budget, bid strategy, schedule, placements, creative inventory, landing experience, tracking readiness, and known seasonal competition. Meta's auction considers bid, estimated action rate, and ad quality; audience size alone does not determine delivery.
Mark the assumptions you control and those you only observe. A wider audience cannot fix an ineligible ad, weak destination, missing conversion signal, exhausted budget, or offer that does not earn action.
Build a range instead of a promise
Create conservative, working, and upper scenarios using the same approved campaign setup. Show spend, assumed cost per thousand impressions, estimated impressions, assumed frequency, and calculated reach. Label every assumption and avoid presenting the midpoint as a platform commitment.
Use the scenarios to answer operational questions: whether creative coverage is sufficient, whether the market is too narrow for the schedule, and what result would trigger a budget, creative, placement, or audience review.
Launch a clean observation window
Publish only after previews, destination, tracking, audience controls, budget, and policy status pass review. Avoid unrelated edits during the comparison window. Log every change with time, reason, owner, and expected effect so later movement is interpretable.
Review delivery alongside spend, unique reach, impressions, frequency, primary outcomes, qualified outcomes, and breakdowns that remain statistically useful. Check rejected or limited assets, learning status, schedule, and account-level constraints before concluding that the audience estimate was wrong.
Reconcile plan and reality
Calculate the gap between each scenario and actual reach, then identify whether budget use, auction cost, frequency, eligibility, creative response, placements, or targeting controls explain it. Update the next planning range with observed data from the same business and market rather than copying a generic benchmark.
Deliverable: timestamped audience estimate, configuration record, three-scenario worksheet, assumption owner list, launch QA, edit log, actual reach and frequency report, qualified-outcome comparison, diagnosis, and next-test decision.
THE TAKEAWAY
Use the estimate to compare configurations, not promise delivery; approve a range, preserve the setup, and reconcile actual unique reach and business outcomes after launch.OFFICIAL REFERENCES