Skip to content
Pinokio Documentation

Ad Verification Overview

Ad Verification is a sophisticated scanning system which ensures that creatives are malvertising free and ad placements are brand-safe. Additionally you can use it to gather more data on what kind of ads (per IAB taxonomy categories) perform best on what traffic, check if advertisers report correct categories and etc.

The integration model is project-based. You create a project for each creative you want monitored — a tag URL or an HTML payload, plus how often you want it scanned and from where. Pinokio scans the creative on the schedule you configured and stores the results against the project. You read those results back through the API, or you can have Pinokio fire an alert pixel the moment something is wrong.

What you can do

Section titled “What you can do”
Schedule recurring scans

A project keeps scanning on your schedule — once a day, several times a day, or on demand. Useful for catching creatives that go bad over time.

Scan from real geos

Specify the location the scan runs from. Different markets see different ads, and that affects what malvertising surfaces.

Get pushed alerts

Configure an alert pixel and Pinokio will hit it the moment a scan finds something. Acts as a webhook for real-time response.

Read scan history

Pull the full scan history for any project, filtered by date range, and drill into individual sessions for detail.

How the API is organized

Section titled “How the API is organized”

The Ad Verification API has two parts:

  • Public endpoints — /login and /refresh_token. Used to obtain a Bearer token. See Authentication.
  • Client endpoints — everything under /v1/project/. All require a Bearer token in the Authorization header.

Project lifecycle

Section titled “Project lifecycle”

A typical integration flow:

  1. Authenticate. Log in to obtain an access token.
  2. Create a project. POST a project for the creative you want monitored.
  3. Read results. Poll scan results for the project, or wait for the alert pixel to fire.
  4. Drill in. For a specific scan, fetch session data for the network trace, screenshots, and detection detail.
  5. Tear down. When you no longer care about a creative, delete the project.