What's Around is planned to appear on every listing and show providers, restaurants and tours within walking distance, expandable to 5 km.
FeaturesLocal · On every page (planned) In development
What's Around
Planned: everything you need, within 600 meters. Banks, notaries, lawyers, restaurants, tours, hotels — on every listing page, once the marketplace launches.
Planned: everything you need, within 600 meters.
- 600mDefault radius
Anatomy of the feature
How What's Around is meant to work
Providers within walking distance, ratings visible, appointments bookable — planned. Hotels should be able to see attribution.
The nearest providers are meant to come first. Distance should decide the order, not a paid slot.
Appointments, tours and reservations should be bookable right from the listing page — no bouncing to a second site.
Planned: a postback API that would tell providers which hotel or apartment sent the click, so hoteliers can prove ROI. This connection does not exist yet.
Deeper look
A neighbourhood, planned for every listing
What's Around is meant to run on every listing, every category — with visible ratings and appointments bookable in two taps.
- Default 600m walking radius — planned, with automatic adaptation for rural areas.
- The nearest providers should come first, with sponsored placements clearly tagged.
- Direct booking inside the same page is planned — no bouncing to a second site.
- Planned: a postback API that would attribute every booking back to the originating listing.
Attribution is meant to show the provider which listing page a click came from. What comes of it should eventually show up in the listing's own numbers — views, QR scans, booking requests.
Example scenario
A map view (example)
Illustrative notaries, restaurants and tours on real Berlin coordinates — not real providers. Tap a pin to see the example.
One map. Everything within reach (planned).
Apartments, hotels, restaurants, venues, notaries, banks — this map view illustrates how a planned 600-meter radius per listing is meant to look. Every pin is an illustrative example, not a real provider or booking.
Example view
The map, explained honestly…
6Categories
600mWhat's around
600mDefault radius
3Numbers per listing
Once we can turn attribution on, we'll see at a glance which hotel sent which booking — no sales team needed, the API is meant to close the loop.
Example profileExample tour operatorPlaka, Athens
With vs. without
A standalone listing, or a connected one
Two ways to put your business in front of someone who's already nearby — the connected one is meant to keep the booking with you.
WithoutOld way: a profile in isolation
- Hotel guests google what's nearby — and book somewhere else.
- No way to know which listings sent which bookings.
- Your entry is invisible to the guest who never finds you.
With DOMIVENDOMOWith What's Around (planned)
- Nearby providers should show inside the hotel page — the booking stays with you.
- A postback API should eventually name the originating hotel for every reservation.
- Your entry should appear automatically on nearby listings.
Powered by
Maps, attribution and booking — one stack
Mapbox renders the canvas. A postback API is planned to attribute every click. The stack runs on EU servers.
- MapboxTile rendering, every region
- Postback APIProvider attribution (planned)
- Payment providerProvider payouts (none yet)
- GDPR · EU serversEncrypted in transit and at rest
Where it shows up
What's Around is meant to live on every category
Stay, eat, buy, rent, sign — every page should eventually show you what's nearby.
Feature FAQ
Things people ask about What's Around
Ready when you are
What's Around is planned for every page.
Planned for every listing, every category.