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.
Open the POI workspace
From the application dashboard, open POI. Existing lists are badged Account or Shared 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 |
|---|---|---|
| Generate with AI | Describing a location set in natural language, then refining the proposal in a conversation. | Completeness and factual verification before Save list…. |
| 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 given to every pin. |
| Import CSV / XLSX | Operational lists maintained in a spreadsheet or system export. | Column mapping, coordinate format, types, and rejected rows. |
Generate and refine with AI
- Choose Generate with AI and describe the location set in ordinary language, including the place and category you need.
- Review the proposed locations and continue the conversation to narrow, add to, or correct the list.
- Check names and positions against your own source of truth. An AI proposal is a draft, not a verified business directory.
- Choose Save list… only after the proposed members are suitable for the campaign.
Create with Pin on map
- Choose Pin on map. The Pin your locations dialog opens.
- Click the exact position for the first POI. The pin is added at once and listed under Pinned locations.
- Type a clear, speakable name in its row.
- Repeat for the remaining locations.
- Drag a pin to move it, or remove its row, before confirming.
- Choose Use these locations, review the list, and choose Save list.
Import CSV or XLSX
Choose Import CSV / XLSX and pick the file. Review how name, latitude, and longitude were read; additional columns can become typed properties of the list.
- 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. A column you add to the list is a property every location carries: right-click a column heading for Rename and Column settings…, where Data type is chosen. Speak supported value types from the script; use every suitable type, including Yes / No, in Delivery rules. A Yes / No property is a decision input, not a spoken token.
| Type | Use it for | Example |
|---|---|---|
| Text | Labels and categories. | store_type = flagship |
| Number | Scores, capacity, price, priority, or thresholds. | priority = 20 |
| Yes / No | A yes/no eligibility property. | open_late = true |
| Date, Time, Temperature, Distance, Speed, Duration, Percent, Direction | Values that should be spoken and compared as what they are. | opens_at = 09:00 |
Marine conditions and Coastal exposure
Every place in a list carries its weather. For coastal locations, open the editor's Actions menu, choose List settings…, and turn on the data the campaign needs:
- Marine conditions — waves, swell, sea temperature, wave period and direction.
- Coastal exposure — adds Wind exposure (onshore / offshore) and Swell exposure (direct / partial / sheltered), based on which way the local coastline faces.
Coastline orientation is worked out automatically when needed. To set it yourself for one place, open the place on the map and use Faces the sea towards. Lists with these options are badged Marine and Exposure.
Ownership and sharing
A normal saved list belongs to the account. Shared lists are available to every account and can be changed only by 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 {.
- Under POI, select the saved list.
- Select a field such as Location name, City, a weather or marine value, or a typed property.
- For a location, choose how much to say and whether to use the ad's language.
- 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. To hear another place in the editor, open Criteria, point at the list, and choose one of its first five records. This preview choice does not set the place listeners will hear; configure that in Delivery → Which record.
A composite POI location can say just the place, include its region, or use the full known location. A localized phrase is used only when every requested part has a verified name; otherwise the whole phrase falls back to its original names.
Use the list in Delivery
A list whose fields the script speaks gets its own panel in Which record, titled POI · list name. Define which places the campaign may use under Include and Exclude, choose how one is selected, and decide what plays when no place is left.
For the nearest location, limit the places with Distance to listener and choose the Nearest card. Use Test to place a listener on the map and check the selected place before publishing.
POI QA checklist
- Coordinates and names are correct.
- Property types match their real values.
- Each token's spoken form fits its sentence.
- Places with a missing value are covered by another creative or a deliberate No ad.
- Marine conditions and Coastal exposure are on only where the campaign needs them.
- The list contains only records eligible for the campaign scope.
- Typical, no-record, and boundary listeners were checked in Test.