Discover audiences from a segment catalog

Third-party audiences on Adprime Zero come from a real catalog of 43,175 segment rows across 13 provider ids. You search, you pick returned ids, and unknown keys are rejected.

The catalog was expanded on June 25, 2026 from a 50-row activation seed by a live refresh. Provider-filter checks passed for provider 272 (Tru Optik) and 611 (Experian). This is not a guessed list of friendly names.

How to search

Dashboard targeting, GET /targeting/reference/segments, MCP discover_segments, and ztdsp targeting discover-segments all read third_party_segment_catalog. Query by the words you mean, set a limit, and read JSON.

Use the returned id as the segment key. Do not type the display name into create_targeting. Show estimated data CPM and reach before you create the targeting set. Data CPM is part of the buy. Hiding it until the first invoice is how a "cheap" remnant test stops being cheap.

POST /targeting, MCP create_targeting, and ztdsp targeting create resolve every submitted segment key into audit rows with data CPM, reach, and policy tier. An unknown key fails the request. It is not dropped. Dropping was the failure mode we refused, because an agent that sends a typo would launch a broader or empty audience and call it targeted.

Policy and activation

Sensitive audience tiers require a human to review and acknowledge. Chat-originated segment writes stay behind that review. An agent may discover and propose. It should not attach a sensitive segment to a live campaign because a prompt said "find me buyers."

Activation still needs prepaid balance and the rest of the campaign checks. A segment-targeted campaign must not activate broader than requested. The inactive write probe that proved the path created a targeting expression with user.segment set and active=false, with no line-item attachment. Live targeting is on for the product as of the June 25, 2026 API Worker that shipped LIVERAMP_SEGMENT_TARGETING_ENABLED=1.

Geography is still a country list on the targeting object. Segments do not replace "USA only" if that is what you meant.

What this is not

It is not a promise that a named segment will convert. It is not a replacement for reading remnant quality after launch. A precise audience on a clicky domain is still a clicky domain. Read performance without fooling yourself still applies.

The Lab writeup of the same catalog is Segment targeting from a real catalog. This guide is the buyer job: search, pick ids, show CPM, refuse unknown keys.

Example CLI shape from the public quickstart:

ztdsp targeting discover-segments --query automotive --limit 5 --json
ztdsp targeting create --name "US auto intenders" --countries USA --include-segments alliant-167430 --json

Use a key you actually received from discover. The alliant-167430 example is a documented quickstart id, not a recommendation for your product.