Binoban Inspector
activeEvery finding the Inspector can report, what the DevTools panel shows, and exactly what the copied report contains.
For installing and running it, see Check a page with the Inspector.
Requirements and footprint
| Browser | Google Chrome 111 or newer. Chrome enforces this from the extension manifest and refuses to load below it. |
| Distribution | Unpacked only, from a build supplied by Binoban. No Chrome Web Store listing (a listing is planned). |
| Chrome permissions | storage and tabs, plus content scripts on all URLs. |
| Network access | None. The Inspector makes no requests of its own and needs no configuration, so it behaves identically in an air-gapped deployment. |
| Stored data | Observations are held in chrome.storage.session, which is in memory and cleared when the browser closes. Nothing observed about a page is written to disk. |
The Chrome 111 floor comes from declaring a content script in the page's own
JavaScript world statically in the manifest. That is what lets the Inspector run
before the page's Binoban code initializes. It is a later Chrome version than the
chrome.scripting.executeScript() world support that landed in Chrome 95; the
static declaration is the one that matters here.
The three finding levels
| Mark | Level | Means |
|---|---|---|
✓ | ok | Checked, and working. |
! | warn | Checked, and something needs attention. Always carries a next step. |
? | unknown | Could not be checked. Not a failure, and never a claim that something is absent or broken. |
The distinction between ! and ? is deliberate and load-bearing: "we were not
watching" is a different fact from "it did not happen," and the Inspector never
reports the first as the second.
Findings — is Binoban working?
When the page was not watched
| Finding | Level | What it means |
|---|---|---|
| Nothing to report yet | ? | The Inspector did not watch this page load, so it has no observations at all. This is the only finding shown in that case — it never appears alongside others. Reload the page. |
Installation and destination
| Finding | Level | What it means |
|---|---|---|
| Binoban is installed | ✓ | The Binoban code on the page started up and the Inspector is watching it. Names the Web SDK version, or says "Version not reported". |
| Sending to your Binoban workspace | ✓ | The page reported which source it sends to. Names the sourceIdentifier, and the API host once that resolves. |
| No destination reported | ! | The page did not say which Binoban source it sends to. Have the setup snippet on the page checked. |
Activity and delivery
| Finding | Level | What it means |
|---|---|---|
| N actions recorded | ✓ | N calls were observed since the page loaded; the detail line says how many were sent successfully. |
| No activity seen yet | ! | Nothing has been sent since the page loaded. Interact with the page as a visitor would and check again. |
| N actions did not reach Binoban | ! | Calls were recorded but could not be delivered. The copied report names them. |
| Part of the setup did not start | ! | One or more integrations failed to initialize. The copied report names them. |
Identity
| Finding | Level | What it means |
|---|---|---|
| Visitor identified | ✓ | An identify was observed, so activity on this page is attached to a known customer. |
| No sign-in seen on this page | ! | No identify was observed, so the visitor's activity stays anonymous. Expected on a public page; worth checking on a page behind a login. |
| No sign-out seen | ! | A sign-in was seen but no sign-out. Only ever shown once a sign-in exists, because with no identified visitor there is nothing to sign out of. If visitors sign out on the site and Binoban is not told, two people sharing a browser can be merged into one customer record. |
Findings — are the ad spaces filling?
These findings appear only on pages where ad spaces were actually found. On a site that sells no ad inventory, the Inspector stays silent about ads rather than carrying a permanent, irrelevant warning.
| Finding | Level | What it means |
|---|---|---|
| N of M ad spaces are showing an ad | ✓ | Of the ad spaces that have received an answer, N are showing an ad. Spaces still waiting on a response are counted separately and never as empty. |
| All ad interactions were counted | ✓ | Every readable impression and click ping on the page was recorded. |
| Cannot check the ads on this page | ? | The page has ad spaces, but the Binoban code running on it has not confirmed it can report on them. Usually an older build; it can also simply mean the code has not finished starting up. See the note below. |
| Ads cannot be requested | ! | The page has ad spaces but no ad server address is set, or it is set under the wrong name, so no ads were ever asked for. |
| The request for ads did not go through | ! | The page asked Binoban for ads and got no answer back. |
| The ad server sent back an error | ! | The request returned an error status, so there is no way to tell whether a campaign is running. Reported as a server problem, not a campaign problem. |
| None of the N ad spaces received an ad | ! | Every ad space answered so far came back empty. Either no campaign is currently running, or the spaces are configured under the wrong IDs. |
| N ad interactions were not counted | ! | Impression or click pings were dropped, so they may be missing from reporting. |
The ad checks need a Binoban Web SDK build that reports on ad spaces. If this finding persists after a few seconds, ask your Binoban contact whether this site's Binoban code is current. It is not a sign that ads are broken — it means the Inspector has not been told it can check them.
An ad space that has been scanned but has not yet received a response is reported
as still pending, never as empty. A 0 or missing response status reads as unknown
and produces no finding at all — only a genuine error status does.
The DevTools panel
Open Chrome DevTools on the page and select the Binoban tab. This is the deeper-inspection surface, and the one place full ad detail appears on screen.
| Tab | Shows |
|---|---|
| Diagnostics | SDK version, API host, source identifier, the integrations that loaded, and any that failed to initialize. |
| Events | One block per observed call: type and name, delivery status, the plugins that enriched it, the time, and a failure reason where there is one. |
| Identity | The current anonymousId and userId, plus a table of identity transitions with their times. |
| Ads | Ad server address, declared space count, request/render outcome and response status; then one row per ad space — fill state, template, impression, click, bid IDs, and whether it painted; then one row per ping with its result. |
Every tab honours the same reload rule as the popup: on a page it did not watch, each tab says so rather than reporting an empty page as a working one.
The copied report
Copy report for support puts a plain-text bundle on your clipboard. Lines are omitted when they have nothing to say.
Binoban Inspector report
page: <page URL>
sdk: <Web SDK version | not reported>
source: <sourceIdentifier | not reported>
host: <API host | not reported>
events: total <n>, delivered <n>, failed <n>
ad spaces: <n> declared, <n> of <n> filled, <n> not answered yet
ad space ids: <slot id>, <slot id>
ad fault: <what> on <slot id> (bid <bid id>)
event names: <name>, <name>
identity: <transition> → <transition>
failed to start: <integration>, <integration>
findings:
- [ok|warn|unknown] <finding title>
next: <next step>
The ads lines appear only when the page has ad spaces the Inspector can report on.
filled is always stated against the number of spaces that have answered, never
against every declared space, so a report copied mid-flight cannot read as
confirmed emptiness.
What the report excludes
The report is built to be pasted into a ticket or chat by someone who will not audit it first, so it deliberately leaves out everything that routinely carries personal data:
- Event properties — never included.
- User traits — never included.
anonymousIdanduserId— never included. Identity transitions are reported (that a sign-in happened, and when), not the identifiers themselves.- Creative image and click-through URLs — never included.
- Bid IDs — included only where something is demonstrably broken and the backend needs a lookup key for it.
All of these are visible on screen in the DevTools panel. Showing something to the person reading it and exporting it into a channel nobody audits are different acts, and the Inspector treats them differently.
If you need to inspect a full event payload, read it in the DevTools panel. The copied report will never contain it.
See also
- Check a page with the Inspector — install it and run it
- Debug mode — verbose SDK logging
- Go-live checklist
- Error codes