From SDK event to a clear dashboard
AdProof collects ad visibility events, connects them to each customer project, and shows where impressions are lost, where overlays trigger, and which pages need attention.
Strict protection workflow
One clear setup: the SDK captures visibility signals, the backend verifies protected access, and dashboards show project-level impact.
What the dashboard answers
- Which pages lose the most visible ad blocks?
- Which domains or paths have setup issues?
- How often is protected content unlocked?
- Which trigger reasons repeat across customers?
Strict access path
- Public SDK key identifies the project.
- Events are tied to domain, path, session, and reason.
- Secret verification stays on the customer backend.
- Admin dashboards keep owner and customer analytics separate.
Platform flow
One public snippet can power customer dashboards, owner analytics, visibility explanations, and server verification.
Client SDK
The script is added to the customer page and loads project settings by public key.
Event stream
Events are sent in batches: visit, ad visibility, overlay, unlock, restore, and verify.
Server verify
The customer backend verifies protected access with a secret key.
Dashboards
The SaaS owner sees global data; customers see only their projects, domains, pages, and reasons.
For SaaS owners
Global load, customers, projects, health status, quotas, and integration failures.
For customers
Simple metrics: visits, affected visitors, overlay rate, unlock rate, restored blocks, top pages.
For developers
Events, reasons, payload, domain, path, page URL, session, and a clear install snippet.