Kaminari Ad

Recipe: bidder block-list automation

Wire Kaminari Ad findings into your SSP/DSP bidder block-list via webhooks, with idempotency and a latency budget.

A common integration for ad networks: when Kaminari Ad flags a creative, stop it serving by pushing it to your bidder's block-list — within minutes, not days.

Architecture

  1. Pipe inbound RTB creatives into Kaminari Ad — single scans for hot domains, bulk across countries for broader coverage.
  2. Subscribe a webhook to scanning.tags.detected (and/or alerting.alert.created).
  3. When a high-severity tag fires — or a tag slug on your block list — add the creative's identifier to your bidder's block-list.

Practical guidance

  • Idempotency — dedupe on the webhook event id; the same event may arrive twice.
  • Latency budget — keep your handler fast (ack quickly, do the block-list write asynchronously) so retries don't pile up.
  • Threshold — start conservative (block only high severity or a specific tag-slug allow-list) and loosen as you trust the signal.
  • Fetch detail when needed — the webhook carries scan_id and tag_slugs; call GET /api/v1/scans/{id} for the classification, redirect chain, and screenshots.
  • Re-checks — schedule periodic campaign re-scans so a creative that turns bad later is caught.

Verifying

Use the webhook test and replay tools to exercise your block- list write path end to end before pointing production traffic at it.

← All documentation