Skip to main content
operations

Check a Page with the Inspector

active
Audience: developerUpdated 2026-08-17

Install the Binoban Inspector browser extension and check whether a live page's integration is working.

The Inspector answers one question about a page: is this page's Binoban integration actually working? It reads what the Binoban code on the page is doing and states findings in plain language, plus a report you can paste into a ticket. It needs no DevTools knowledge to read, so it also works as the thing you hand to a marketing or e-commerce team who need to know whether to escalate.

For what each finding means, the full report format, and the privacy boundary, see the Inspector reference.

Before you start​

  • Google Chrome 111 or newer. Chrome refuses to load the extension below that version, so a too-old browser fails at the install step rather than installing and quietly seeing nothing.
  • The extension build. Ask your Binoban contact for the current Inspector build — a .zip you unpack yourself.
Why it isn't in the Chrome Web Store yet

Today the Inspector installs unpacked, which is also what lets it run in on-prem and air-gapped deployments where a Web Store install is blocked by policy or unreachable outright. A Chrome Web Store listing is planned.

Install it​

  1. Unzip the build somewhere you can leave it — Chrome loads it from that folder every time it starts, so don't unpack it into a temporary directory.
  2. Open chrome://extensions.
  3. Turn on Developer mode (top right).
  4. Click Load unpacked and select the unzipped folder.

Binoban Inspector now appears in your extensions list and its icon in the toolbar. To upgrade later, replace the folder's contents and click Reload on the extension's card.

Reload the page you want to check​

This step is not optional. The Inspector can only report on a page it watched load from the very start — it hooks into the Binoban code on the page before that code initializes, and there is no way to catch up afterwards.

So on any tab that was already open when you installed or enabled the extension, reload the page before you open the Inspector.

"Nothing to report yet" means reload, not broken

If the Inspector says Nothing to report yet, it is telling you that it never watched the page load. It is not a claim that Binoban is missing, misconfigured, or broken — the Inspector simply has no observations to report. Reload the page and open it again.

Read the findings​

Click the Inspector's toolbar icon. The popup lists the page URL and one finding per line, each marked:

MarkMeaning
✓Checked, and working.
!Something needs attention. The line tells you what to do next.
?The Inspector could not check this. Never a failure — see the reference.

Every ! and ? finding carries its own next step, so you can act without looking anything up.

Some findings only appear once you give the page something to observe. No activity seen yet means nothing has been sent since the page loaded — click around the page as a visitor would, then open the popup again. Likewise, sign in to check identification, and sign out to check that the sign-out is reported.

Copy the report for support​

Click Copy report for support at the bottom of the popup. That puts a plain-text support bundle on your clipboard: SDK version, destination, event counts and names, identity transitions, ad-space counts and faults, and every finding with its next step. Paste it into your ticket or chat.

The report is deliberately not a full data capture

It excludes event properties and user traits, which routinely carry personal data. See what the report excludes before you rely on it for a payload-level question.

Inspect the detail in DevTools​

For per-event and per-ad-space detail, open Chrome DevTools on the page and select the Binoban tab. It has four tabs of its own — Diagnostics, Events, Identity, and Ads — and it is where full event payloads and creative URLs are visible. The same reload rule applies: the panel reports on the load it watched.

The DevTools panel is the surface for you or the customer's technical team, once the popup's report has been handed over. See the DevTools panel for what each tab shows.

Next steps​