User Guide · Personalize

Turn locations into a reusable campaign dataset.

A POI list holds named locations, coordinates, and typed business properties. Create it in the POI workspace, insert its fields into a script, then let Delivery choose the right location per request.

Geo personalizationAccount asset

Open the POI workspace

From the application dashboard, open POI. Existing lists show their ownership and can be opened for review or editing when your role allows it.

Open the dashboard, then choose POI from the navigation.

Choose a creation method

Method	Best for	Review focus
New list	Searching/geocoding locations and editing them individually or together on a map.	Correct result, coordinates, and duplicate names.
Pin on Map	A small curated set of locations known visually.	Pin accuracy and the name entered for every click.
Import CSV/XLSX	Operational lists maintained in a spreadsheet or system export.	Column mapping, coordinate format, types, and rejected rows.
Generate with AI	Drafting a list from a natural-language region/category request.	Completeness and factual verification before Save.

Create with Pin on Map

Choose Pin on Map.
Click the exact position for the first POI.
Enter a clear, speakable name.
Repeat for the remaining locations.
Move or remove incorrect pins before confirming.
Review the resulting entities and save the list.

Map accuracy matters twice.Coordinates affect both the selected record and any spoken distance. Zoom in far enough to avoid placing the POI on the wrong road, entrance, or coastline.

Import CSV or XLSX

Map the source columns for name, latitude, and longitude. Additional columns can become typed properties in the list schema.

Use decimal latitude and longitude consistently.
Give every row a stable, human-readable name.
Remove duplicates and incomplete coordinates before import.
Choose the correct type for each additional property.
Review a sample of mapped rows on the map.

Add typed properties

Properties carry campaign-specific data such as priority, store type, inventory class, region, or an approved spoken label. They become fields such as prop.<key> in Delivery.

Type	Use it for	Example
String	Labels and categories.	store_type = flagship
Integer/float	Scores, capacity, price, priority, or thresholds.	priority = 20
Boolean	A yes/no eligibility property.	open_late = true

Coastal and marine lists

Mark a list Coastal only when marine or surf enrichment is relevant. This can enable additional fields and background calculation such as shoreline-facing information. Review enriched values before using them for a live rule.

Ownership and sharing

A normal saved list belongs to the account. Shared lists are available only to authorized platform administrators. Treat list editing as a campaign-impacting operation: projects can continue to reference the list after it changes.

Insert a POI field in Studio

Open the target project and creative.
Place the caret in the script and type {.
Choose POI.
Select the saved list.
Select a field such as City, Name, or a typed property.
Confirm the token in the script and Dynamic Properties.

The list is referenced by its identity; it is not copied into the creative. Keep the list available for preview and Delivery.

Use the list in Delivery

Delivery scans project bindings and creates a subject panel for the POI list. In Which record, define eligibility, filters, score, computed fields, and pick mode.

A common nearest-location strategy scores candidates with the negative distance between listener and POI coordinates, then chooses the largest score. Use Pick on Map to simulate listener coordinates before publishing.

POI QA checklist

Coordinates and names are correct.
Property types match their real values.
Every spoken field has an acceptable fallback.
Coastal/marine classification is intentional.
The list contains only records eligible for the campaign scope.
Best, no-match, and tie scenarios were simulated.