Create a geo segment from circles
direct_audience_segmentsCreate Yandex Audience geo segments from circle points with a radius in meters. Preview confirms before creation; afterwards, find the segment under a different ID in retargeting lists.
Instructions
Create ONE geo segment in Yandex Audience from CIRCLES — the one create path measured live. Polygons are recorded as knowledge only (knowledge://audience) and deliberately not implemented: their shape was never probed against the live service.
Radius is METERS, 500..10000 — the unit is proven by a two-sided probe; kilometers here would draw 500 km circles. A segment holds up to 1000 points, a 'condition' segment up to 100 (a limit bought by a live refusal), and 'condition' requires both period_length and times_quantity. Everything checkable is checked BEFORE the network, because the service's wrapper refusal masks every other complaint.
Called without a confirmation it answers a preview. After creating, the list is read back with the status — Direct sees the segment only after processed, and under a DIFFERENT number: verify by reading retargetinglists.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | the segment's name — it appears in the confirmation phrase and on the card | |
| points | Yes | circle centers: objects with latitude, longitude and an optional description. At most 1000; for geo_segment_type='condition' at most 100 | |
| radius | Yes | circle radius in METERS, 500..10000 — one radius for the whole segment | |
| confirmation | No | the exact phrase the preview asks for | |
| period_length | No | days, 1..90. condition only, required there | |
| times_quantity | No | days the person was inside, <= period_length. condition only, required there | |
| geo_segment_type | Yes | measured list — no page names it. regular: regularly visits, lives or works (45 days); condition: was there N days over a period; last: is there now; work and home are legacy |