Multi-Site Proximity Matcher — Places to Stores & Branches

Match one place list to many stores, branches or properties

Turn an existing geocoded place list into a table of which places are near each of your sites. Match restaurants to retail locations, competitors to stores, or amenities to a property shortlist. Keep every overlapping match or assign each place to its nearest site.

Paste two lists and run. The Actor accepts Compass Google Maps coordinates directly and needs no mapping API key, geocoding call or new scrape. Each output match preserves the place ID, your site ID, distance and rank so it can be joined back to your original data.

Why a multi-site matcher?

Combining multiple geographic searches can produce a useful set of places while losing the relationship between each result and the original search sites. Separate overlapping searches can also return the same place repeatedly. This Actor reconstructs the many-to-many relationship from the supplied coordinates in one bounded batch.

It is designed for site portfolios rather than a single rectangular territory filter. A place within range of three stores can produce three matches. In nearest mode, it produces one match. Every site appears in the separate site summary, including sites with zero matches.

Quick start

1. Paste existing place rows into Places with coordinates. Supported shapes include Compass location.lat / location.lng, top-level lat / lng, or latitude / longitude.
2. Supply each site with a unique string id, coordinates and an optional title.
3. Set a radius in meters. The default is 5,000 meters.
4. Choose all nearby sites or nearest site only, then run.

The prefilled example is explicitly synthetic. It demonstrates one place assigned to two nearby sites in Oslo; it does not discover businesses. Replace both lists for your own analysis.

Example input

{
  "places": [{"placeId":"demo-place","title":"Synthetic venue","location":{"lat":59.9139,"lng":10.7522}}],
  "sites": [
    {"id":"site-a","title":"Synthetic site A","lat":59.91,"lng":10.75},
    {"id":"site-b","title":"Synthetic site B","lat":59.92,"lng":10.76}
  ],
  "radiusMeters": 5000,
  "mode": "all"
}

Output

The dataset contains placeId, placeTitle, inputIndex, siteId, siteTitle, distanceMeters, rank, status and reason. Export to JSON, CSV or Excel. SITES contains per-site match counts. OUTPUT contains the complete report and summary.

Status is matched, unmatched, review or duplicate. Missing or invalid coordinates are explicitly held for review. Repeated place IDs with identical coordinates are counted once; conflicting coordinates for the same ID are held for review. Rows without IDs remain independent input rows. Invalid or duplicate site IDs fail the run before matching.

Ranks are based on unrounded distance. Exact distance ties are ordered by site ID for reproducibility. Input rows are preserved by inputIndex; a matched place may have multiple output rows in all-sites mode.

Pricing and limits

$0.05 per delivered matching report, including up to 10,000 places and 200 sites. Platform usage is included under the published pay-per-event model. No separate charge per overlapping match or third-party API charge. The input limit is 12 MB and the output ceiling is 100,000 rows. If the complete output would exceed that ceiling, the run fails without the matching event; reduce the radius or choose nearest mode.

Invalid top-level input does not generate the billing event. An entirely unmatched report is still a completed report and costs $0.05.

Distance and coverage

Distances are approximate great-circle distances using the mean Earth radius. They are straight-line distances, not driving distance, journey time, administrative borders, service areas or proof of market coverage. Dateline crossing is supported. The radius includes its boundary before display rounding. Source coordinate accuracy may dominate distance precision.

The Actor evaluates only the data supplied. It neither finds missing venues nor guarantees that your source dataset is complete. No user data is sent to another service, and the original catalog is never changed. Use the Apify API, saved tasks or integrations to connect the matching step to your existing workflow. Report reproducible issues through the Issues tab.