Geo Search: drawing a polygon or setting a radius

Administrative boundaries are drawn for government, not for sales territories. Geo Search lets you ignore them and describe the area you actually work in.

Both modes are on every plan at any size, including the free trial. There is no radius you have to upgrade to reach and no tier that unlocks the polygon tool. Geography is not what the tiers differ by — pay for volume, never for access.

Radius

Drop a pin, set a distance, done. Use it when your constraint is travel time from a fixed point: your own office, a depot, a client's site, a trade show venue.

• The smallest radius is 100 m. There is no upper limit — set it to a thousand kilometres if that is your territory.
• The distance is measured to each business's exact latitude and longitude, not to its city centre — so a business 300 m outside the line is genuinely outside it.
• The match count updates as you drag the handle, and it costs nothing to drag.

Polygon

Click points on the map to draw a closed shape. Use it when the area has a real shape: one side of a river, a ring road, three neighbourhoods but not the fourth, a coastline.

• Click the map to place a point. The outline closes itself — there is no "finish" button.
• Drag a point to move it; the area and the count update as you drag. Click a point to delete it.
• Three points minimum, 100 maximum. Under three you get "A polygon needs at least 3 points"; over a hundred, "A polygon may have at most 100 points".
• The shape may be concave. It may not cross itself — a bow-tie is refused with "The outline crosses itself. Move a point so the edges do not overlap" rather than silently producing nonsense.
• The panel shows the area in km² as you draw. It is computed in your browser with the spherical-excess formula, so it is live; the server recomputes it when the query runs and the two can differ in the last decimal.
• There is no ceiling on the enclosed area. Draw a shape the size of a continent if that is what you mean. The point-count limit is a drawing constraint, not a commercial one.

How Geo Search interacts with the location cascade

They are mutually exclusive. Drawing a shape replaces the Country → Level 1 → Level 2 → City selection for that search; you cannot say "inside this polygon and in Oslo municipality". If you need both, draw the intersection.

Activities and filters still apply exactly as normal. A Geo Search is a different way of saying where, nothing else changes.

Precision, and one honest caveat

Matching is exact against each business's stored coordinates. The caveat is upstream: a map pin is only as accurate as whoever placed it. Businesses in large complexes — airports, hospitals, malls — are sometimes pinned to the complex's centroid rather than to their own unit. Near a boundary, that is the main source of surprise.

Saving and reusing an area

Save the search and the shape is stored with it, so a weekly re-run covers the same ground rather than an approximation of it. Re-running inside 30 days only bills the businesses that are genuinely new to you — how lead credits work.

Over the API

POST /api/v1/search takes either polygon (a GeoJSON Polygon) or radius ({ lat, lon, metres }), and they are mutually exclusive with the admin1_id/admin2_id/city_id fields — exactly as in the UI. See the search endpoint.