The bcat compliance gate enforces one of the most fundamental OpenRTB rules: if a publisher declares that certain content categories are blocked on their inventory, no bid in the response may carry a creative from those categories. TheDocumentation Index
Fetch the complete documentation index at: https://docs.pecta.ai/llms.txt
Use this file to discover all available pages before exploring further.
bcat field on the bid request is a publisher’s explicit blocklist. Ignoring it exposes the exchange to brand safety incidents and breaches the supply-side contract.
Usage
How it works
The gate reads the top-levelbcat array from ctx.input (the bid request) and builds a set of blocked IAB category strings. It then iterates every bid in the response and checks each entry in bid.cat[] against that set. The first match causes an immediate failure.
Skipping behaviour
The gate returnspassed: true, skipped: true when:
- The request has no
bcatfield, orbcatis an empty array — there is nothing to enforce - The response contains no bids — there is nothing to check
bcat contains IAB content category codes such as IAB25 (non-standard content) or IAB26 (illegal content). The values come from the publisher or SSP configuration and vary per auction. The gate performs exact string matching against whatever values are present in the request.Example: blocked category in bid
A publisher blocks gambling and adult content:IAB9-7 in both the blocked set and the bid’s cat array and returns passed: false.
Options
Override the gate’s name in evaluation results and telemetry.