Resellers can use audience segment targeting. However, the availability of audience segments depends on how the Data Management Platform (DMP) integration is implemented.
When Triton's ad server receives an ad request through a Reach Extension reseller, it enriches the listener profile with DMPs integrated with Triton. It also attempts to enrich the listener profile using audience data from the reseller’s DMPs.
DMP Integrations That Support Enrichment
Triton can enrich profiles with the reseller’s audience segments when its DMP identifies listeners independently of the media player:
File-based audience imports
IP matching
Other server-side identity matching mechanisms
DMP Integrations That Do Not Support Enrichment
Some DMP integrations rely on the player or SDK to pass audience segments directly in the ad request. These integrations typically require player-generated data such as segment identifiers, cohort codes, headers, or partner tokens.
In Reach Extension, the owner controls the player and stream. Since the reseller does not control the player experience, it cannot inject its own audience segment information into the ad request.
As a result, Triton does not receive the reseller's player-generated audience data and cannot enrich listener profiles using those reseller-side audience segments.