{"id":428715,"date":"2026-09-21T17:20:00","date_gmt":"2026-09-21T17:20:00","guid":{"rendered":"https:\/\/dailybanglanewspapers.com\/news\/pixalate-launches-openepg-db-1-0-and-pre-bid-api-for-ctv-open-programmatic-advertising-mapping-580000-shows-across-13900-channels-including-tubi-samsung-tv-plus-and-the-roku-channel-w\/"},"modified":"2026-09-21T17:20:00","modified_gmt":"2026-09-21T17:20:00","slug":"pixalate-launches-openepg-db-1-0-and-pre-bid-api-for-ctv-open-programmatic-advertising-mapping-580000-shows-across-13900-channels-including-tubi-samsung-tv-plus-and-the-roku-channel-w","status":"publish","type":"post","link":"https:\/\/dailybanglanewspapers.com\/news\/pixalate-launches-openepg-db-1-0-and-pre-bid-api-for-ctv-open-programmatic-advertising-mapping-580000-shows-across-13900-channels-including-tubi-samsung-tv-plus-and-the-roku-channel-w\/","title":{"rendered":"Pixalate Launches OpenEPG DB\u2122 1.0 and Pre-Bid API for CTV Open Programmatic Advertising: Mapping 580,000+ Shows Across 13,900+ Channels, Including Tubi, Samsung TV Plus and The Roku Channel, With Zero Publisher Opt-In Required"},"content":{"rendered":"

<\/p>\n

Pre\u2011Bid API Enriches Open Programmatic CTV Bid Requests With a Standard Content Object in Real Time Across 6,192 U.S. Apps on Roku, Samsung Tizen, Amazon Fire TV, LG webOS, Vizio SmartCast, Apple tvOS, Android TV, Android and iOS, Eliminating Show Name and Genre Blind Spots, Built to IAB Tech Lab’s OpenRTB 2.6 Specification\u00a0<\/em><\/p>\n

LONDON, Sept. 21, 2026 (GLOBE NEWSWIRE)<\/a> — Pixalate<\/u><\/a>, a global ad fraud and privacy compliance platform, today released OpenEPG DB\u2122 1.0 and its Pre-Bid API<\/u><\/strong><\/a>. The system maps 375,000+ Bundle ID variations to 580,000+ shows across 13,900+ FAST and linear streaming channels. It operates across 6,192 U.S. streaming apps on Roku, Samsung Tizen, Amazon Fire TV, LG webOS, Vizio SmartCast, Apple tvOS, Android TV, Android and iOS. The API requires zero publisher opt\u2011in and no publisher\u2011side SDK or integration.<\/p>\n

Today, show-level data for streaming TV comes from two places: program schedules that content owners submit to metadata providers, or automatic content recognition (ACR). Neither appears in most open programmatic bid requests, and the gap is widest on multi-channel FAST aggregators, where a single Bundle ID can carry hundreds of channels.<\/p>\n

OpenEPG DB\u2122 1.0 covers the FAST channels distributed through aggregators such as Tubi, Samsung TV Plus and The Roku Channel, and Pixalate’s API resolves them at the bid request level using only the fields already in the request.<\/p>\n

“Open programmatic CTV has been blind to streaming TV show names: the publisher doesn’t pass the show name, so the buyer prices the app and guesses the rest. For the first time, that bid request can be resolved to the actual show in real time,\u201d said Jalal Nasir, CEO of Pixalate. \u201cOpenEPG DB\u2122 1.0 unlocks content\u2011level intelligence for the open ecosystem and FAST inventory.\u201d<\/p>\n

How It Works<\/strong><\/p>\n

    \n
  1. Input:<\/strong> A standard OpenRTB 2.6 bid request arrives carrying two fields standard in every CTV bid request: app.bundle and device.ua.<\/li>\n
  2. Resolution:<\/strong> Pixalate’s pre-bid engine matches those fields, plus any channel identifier or channel name carried in the request, against OpenEPG DB\u2122 1.0 in real time.<\/li>\n
  3. Output:<\/strong> The API returns the same bid request with the resolved program spliced into app.content as standard OpenRTB 2.6 Content fields.<\/li>\n<\/ol>\n

    Example response:<\/strong><\/p>\n\n\n
    {
    “app”: {
    “bundle”: “com.pluto.tv”,
    “content”: {
    “id”: “ec-4Fq0X2”,
    “title”: “SportsCenter”,
    “genre”: “Sports”,
    “contentrating”: “TV-PG”,
    “channel”: { “id”: “eg-Tj5r8w”, “name”: “ESPN” },
    “ext”: { “openepg”: { “attribution”: “pixalate-openepg\/v1” } }
    }
    },
    “device”: { “ua”: “Roku\/DVP-13.0.0” }
    }<\/td>\n<\/tr>\n<\/table>\n

    Protocol-Level Mechanics<\/strong><\/p>\n

    The API parses incoming OpenRTB 2.6 bid requests using two required fields: app.bundle and device.ua. When bid streams contain platform channel identifiers or channel names, the resolution engine incorporates these signals to calculate match confidence.<\/p>\n

    The API returns a native OpenRTB 2.6 Content object that can include:<\/p>\n