Woosmap
Technographic sources (HTTP Archive, BuiltWith, SimilarWeb) crawl one page per site: the home page. But a platform does not put its map in the shop window, it puts it behind a search field, because the map is the product. Of 12 hand-confirmed payers, zero called a mapping API from their home page. The classic scan over-represents local shops and misses exactly the accounts Woosmap targets.
A two-stage scanner, in Python. Stage 1: one HTTP request per domain, no browser, at 2,000 domains a minute, to spot the provider, the country and the JavaScript bundles. Stage 2: the search or booking page, the source code strings and the linked CSS and JS bundles, where compiled keys hide. Every fix was measured: visiting the search page adds 47% more payers, reading the bundles lifts recall from 37% to 51%, and pure HTTP brings the scan from 60 hours down to 2. Accounts come out with their detected provider, ready for the LinkedIn matched audience and decision-maker enrichment through Airscale.
322K domains scanned to find who already pays for a mapping API
322,000 UK domains processed in 2 hours. 3,805 accounts identified as mapping API payers, with the provider named (Google Maps Platform, Mapbox, HERE, Loqate). 61% recall measured against a set of 13 accounts with verified proof, where the home page approach scored zero. These accounts feed the UK LinkedIn ABM audience and the sequences, with the argument the prospect sees immediately: we know what they pay for.
Location API · B2B SaaS · FR, UK, US
2026
322K
domains scanned to find who already pays for a mapping API
