- INSIGHT_COUNT: how many places of the chosen types exist in a circle, a drawn polygon or a region
- INSIGHT_PLACES: the place ids themselves when a filter matches at most 100 places
- Iris prospecting splits dense areas into tiles automatically so every place is returned, then turns results into prospect lists
- Filters on place types (included and excluded), minimum rating, price level and operating status
- Single read-only route; your key, your project, every call logged in your tenant
Google Places Aggregate (Area Insights) Connector
Google's Places Aggregate API — count places or list place ids inside an area filtered by type, rating and operating status — powers prospecting in Apivom Iris with your own Maps Platform key: draw an area, pick the business types you sell to, and get a prospect list, with dense areas tiled automatically.
What you can do
Use cases
- Build a territory prospect list in minutes — Draw the district you want to work, select “restaurant” and “cafe”, and get every matching business as a prospect list in Iris instead of scrolling a map by hand.
- Size a market before committing a rep — Use counts by type and area to compare regions — how many dental clinics in each city — before deciding where to hire or focus.
- Qualify by rating and status — Filter to operational businesses above a minimum rating so the list excludes closed or low-quality locations from the start.
Places Aggregate — Google calls it Area Insights — answers one question very well: within this area, how many businesses of these types are there, and which are they? Its single Compute Insights route takes a location filter (a circle, a custom polygon or a Google region), a type filter with included and excluded place types, optional rating, price and operating-status filters, and returns either a count or the place ids that match. Google returns ids only for 100 matches or fewer, with no pagination, which makes dense city centres awkward to cover by hand. Apivom Iris's prospecting feature handles that for you: you draw a circle or polygon on the map, choose the business types you want to reach, and Iris subdivides the area into a quadtree of tiles — each clipped to your shape — until every tile is under the limit, so the full set of places comes back. The resulting ids become a prospect list you turn into companies and leads. The call runs through Apivom Atlas with your own Maps Platform key, and each request is logged in your tenant.
Your own Google Cloud API key (Maps Platform) with this API enabled on the project; the Apivom product sends it as the x-goog-api-key header on each call. Google bills the project that owns the key. The key is encrypted in your Iris tenant; Apivom Atlas stores nothing.
Frequently asked questions
Why does Iris split my area into tiles?
Google returns place ids only when a filter matches 100 places or fewer, with no paging. Iris subdivides the area into smaller tiles clipped to your shape until each tile is under that limit, so a dense city centre still yields the complete list — at the cost of more calls, which you see in the log.
What do I get per place?
Places Aggregate returns place ids (or a count). Iris enriches the ids with details — name, address, rating, status — through the Places API (New) connector before you convert them into companies or leads.
Which Google Cloud project pays for the calls?
The project that owns the API key you connect. Enable this specific API on that project, restrict the key to the APIs you actually use, and Google's Maps Platform pricing and monthly credit apply to it directly — Apivom adds no charge and shows every call in your tenant's integration log.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.