SENSOR_DEMOGRAPHICS
seg requires a device with the SENSOR_DEMOGRAPHICS sensor — the sensor that detects the live audience in front of the screen. On a device without it, seg is rejected (400).
seg format
Section titled “seg format”seg=<segmentId>[.<segmentId>…][:<count>][;<profile>…]- Each
<segmentId>is an IAB Audience Taxonomy 1.1 segment id. Today, send gender and age segments; look ids up in the taxonomy list (e.g.49female,50male,5= 25-29). .joins segments of different types into one profile, matched as AND:49.5means “female and aged 25-29.”;separates profiles, matched as OR.:<count>is the number of shoppers detected for that profile; default1.- One value per type per profile. For two values of the same type, use two profiles:
49:3;50:2(3 female, 2 male), not49.50.
Validation
Section titled “Validation”seg is validated in full before selection runs. Any of these returns 400: a malformed value, a bad or negative count, an unsupported or unknown segment id (send only the supported types, today gender and age), or seg on a device with no demographic sensor. The server rejects rather than partially honoring a request, so fix the value instead of relying on a best-effort match.
Example
Section titled “Example”An online request from a SENSOR_DEMOGRAPHICS device: 3 women aged 25-29 detected, shopper holding 2× sku-123 and 1× sku-456, with a sensor activation id.
GET /v1alpha2/ads?playerid=screen-01&key=retailer-acme&limit=1&seg=49.5:3&products=sku-123:2;sku-456&dvactid=act-7XK HTTP/1.1Accept: application/xmlAs sent on the wire (; → %3B, : → %3A; . is URL-safe):
GET /v1alpha2/ads?playerid=screen-01&key=retailer-acme&limit=1&seg=49.5%3A3&products=sku-123%3A2%3Bsku-456&dvactid=act-7XK