Usage
How child-directed inventory is detected
The gate inspects the request (ctx.input) for any of the following signals:
regs.coppa === 1— the request explicitly declares COPPA applicabilityapp.catcontainsIAB13— the app’s content category is children’s contentsite.catcontainsIAB13— the site’s content category is children’s contentapp.bundlecontains any of the keywords:kids,child,children,toddler,preschool,baby
skipped: true immediately. No bids are inspected and the remaining pipeline continues normally.
Unsafe categories
When inventory is flagged as child-directed, the gate checks everybid.cat[] entry against the following default unsafe categories:
| IAB category | Content type |
|---|---|
IAB7-39 | Substance abuse |
IAB8-5 | Beer |
IAB8-18 | Wine |
IAB14-1 | Dating |
IAB25 | Non-standard content |
IAB25-1 through IAB25-7 | Non-standard content subtypes |
IAB26 | Illegal content |
IAB26-1 through IAB26-4 | Illegal content subtypes |
Options
Replace the default unsafe category set entirely. When provided, only the categories you list are considered unsafe. Pass an empty array to effectively disable the category check while keeping the COPPA detection logic.
Additional substrings to match against
app.bundle when detecting child-directed inventory. Matched case-insensitively. For example, ["junior", "playground"] would flag bundles like com.example.junior-app.Override the gate’s name in evaluation results and telemetry.
Example: COPPA request with unsafe bid
regs.coppa = 1, finds IAB8-5 in the bid’s cat array, and fails.