Creating and managing territories

Create a durable territory that can be referenced by research, Stores, campaigns and performance reporting. A territory is a scoped business geography, not a request to ingest or repair the national map.

Choose the boundary

Use a supported canonical area or a reviewed custom boundary, with account/workspace ownership and a clear name. Preserve the geometry revision and source identity so later work knows exactly which area was selected.

Addresses, streets, places and administrative areas have different evidence and coverage. A public geography cell is not the same privacy class as a person's device location.

Save the territory outcome

The intended artifact includes the territory identity, immutable boundary revision, source references, supported coverage and any missing prerequisites. Downstream work should bind that revision rather than a mutable map viewport.

For example, a saved campaign territory can remain an inert draft while its address membership is unavailable. Saving it must not automatically start discovery, funding or dispatch.

Reuse with explicit scope

A Store assortment, rank scan or campaign target snapshot can reference the territory only under the relevant grants and readiness checks. Updating a boundary creates a new versioned decision; it does not rewrite earlier observations.

Availability

Business APIs are planned. Supported geometry queries do not imply nationwide source completeness. Canonical ingest, backfill and repair controls remain internal, and precise private location evidence remains restricted.