locatorstudio.Plan your locator
BRING IT ALL TOGETHER

Your data. Your site.
A good connection.

Connect your location data and customer website.
Choose a reviewed setup for each connection.

01 / A PLACE ON YOUR WEBSITE

A considered
addition.

Use the locator’s embed workflow or shared experience. Match your design and review the setup for your website.

Plan your locator
YOUR BRANDShop   Our story   Find us
NEAR YOUSomewhere
worth finding.
Your LocatorStudio experience
An embed on your page. A useful next step for your customers.
02 / START WITH WHAT YOU HAVE

Give your data
a clear direction.

Review a spreadsheet import, or configure a supported connection. Each source has its own setup and access requirements.

Connected source

HTTPS JSON feed

Use an exact server-allowlisted feed. Review the mapped snapshot before applying changes.

Setup required
Spreadsheet import

CSV & XLSX

Start with the file you already have. Review columns and changes before applying a supported spreadsheet.

Review & import
Connected source

Google Sheets

A read adapter for location data, with separate credentials and reviewed source updates.

Setup required
Connected source

Airtable

Use a read adapter after access, mapping and update behavior are configured.

Setup required
Connected source

HubSpot

Connect a supported data source with workspace-scoped setup and a reviewed import workflow.

Setup required

Adapters require configured credentials, mappings and an observed runner for scheduled work. These examples do not connect to your accounts.

Refresh and notification delivery

Optional refresh operations record runs and failures. The webhook notification gateway uses durable requests and explicit provider receipts; an HTTP 200 alone does not prove delivery. Configure the endpoint, credentials, operating owner and authenticated runner, then verify actual delivery.

Source updates save to the shared draft. Customer publication remains a separate reviewed action.

03 / WHEN YOU NEED A LITTLE MORE CONTROL

Build around
your workflow.

Scoped customer reads, versioned API responses and a typed client give developers a clear place to start.

Review resources, access, limits and publication behavior for your intended setup. Backend integration secrets stay out of browsers and URLs.

Plan your locator
A SMALL EXAMPLE
// Current authorized customer view
GET /api/v1/locators/:releaseId/results

// Select the page and public filters
?limit=24&sort=name

// Credentials travel in headers.
Authorization: Bearer <short-lived-token>

Illustrative API shape. Use the current reference and an authorized runtime credential for a real integration.

A FEW THINGS TO PLAN TOGETHER

Clear expectations.
Better connections.

Your website

Which page hosts the locator, what the brand needs and how the experience is embedded.

Your source

Who owns location updates, which fields are authoritative and what needs review.

Your operating setup

Provider access, scheduling, limits and the responsibilities behind an ongoing connection.

MAKE YOURSELF EASY TO FIND

Let’s find your
right connection.

Let’s work out what the right locator looks like for you.

Plan your locator