Why do I keep getting Meta leads from outside my service area?
Usually the location setting. Meta lets you target people living in a place, recently in it, or traveling in it, and the default is broader than most local advertisers assume. Anyone who passed through your radius can qualify. Radius circles also spill across service boundaries that matter to dispatch but mean nothing to Meta. Set the mode explicitly, target by postal code where your boundaries are irregular, and validate the address on the form or the first call.
The setting most people never open
Under the location field there is a choice of who counts as being in that location: people who live there, people recently there, people traveling there, or everyone in the location. The broadest option includes anyone whose device reported being inside your radius, which sweeps in commuters, visitors and people who drove through on the interstate.
For a home services business, only residents can buy. Setting the mode to people living in the location is a one-click change that removes an entire class of junk lead, and it is the first thing to check when out-of-area leads appear.
Circles do not match service areas
Dispatch boundaries are shaped by drive time, river crossings, mountain passes, licensing jurisdictions and where your techs actually live. A radius is a circle. The mismatch shows up as leads that are technically nearby and operationally unservable, which is worse than a lead from another state because someone wastes time on it.
Postal code targeting is clumsy but honest: it lets you encode the real boundary. For multi-branch operators it also prevents two branches bidding into the same overlap, which quietly inflates cost for both. That coordination problem is the same one you face in search campaigns, and it should be solved once with a shared service area definition.
Validate at the point of capture
- Ask for the service address, not just the city. A postal code field on the form is the cheapest filter available and it costs one line of typing.
- Check it before dispatch. Route the postal code against your coverage table automatically so an out-of-area lead is flagged the moment it arrives, not after a callback.
- Tag it, do not delete it. Out-of-area leads should be recorded and counted so you can measure how much of your spend produces them. Deleting them hides the problem and corrupts your source-level reporting.
Measure the leakage rate as a metric
Out-of-area percentage by campaign is a legitimate performance metric and almost nobody tracks it. It tells you which campaigns are burning budget on people you cannot serve, and it changes when someone edits a radius, which makes it a useful canary.
Getting there requires the lead record, the coverage map and the spend data in one place. That is a small piece of systems integration that pays for itself quickly, and it feeds directly into the source-quality view in marketing intelligence.
Topics: geo targeting · service area · lead quality · dispatch
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.