Verify the installation

After publishing the snippet, open your store's checkout page in a browser. Within a few seconds the SDK starts reporting. Use the three checks below to confirm everything is working.

In the dashboardCopy Anchor Link

Top indicatorCopy Anchor Link

At the top of the dashboard (on the desktop version) there's an SDK status indicator:

• Proteside Active (green): the store has recent real traffic from the SDK.
• Proteside not detected (red): no recent real traffic.

The indicator links to Settings → Pages & Domains. There, the Detected pages section lists every page that has already sent events, grouped by domain, with the SDK active badge (activity in the last 24 hours) or Not detected.

SDK HealthCopy Anchor Link

The SDK Health page shows whether the SDK is reporting real customer traffic, separate from synthetic checks.

The page also shows Domains with real traffic, the totals for the last 48 hours, the Events per hour chart, the SDK versions seen in the last 7 days and the current configuration (channel, developer mode and protection mode). Data is aggregated by hour: reload the page to refresh it.

More details in SDK Health.

In the browserCopy Anchor Link

Open the checkout, open the developer tools (F12) and go to the Console tab.

SDK statusCopy Anchor Link

Proteside.getStatus()

Expected response, a few seconds after the page loads:

{
  initialized: true,          // the SDK finished starting up
  mode: 'monitor',            // or 'block'
  paused: false,              // true = developer mode, inactive subscription or local pause
  channel: 'stable',
  calibrating: true,          // true during the first 30 s (calibration)
  activeThreats: 0,
  paymentMethodsMonitored: ['pix', 'card'],
  version: '1.1.1',
  installationOrderValid: true, // false = there's a script before the bootstrapper
  overlayCheckIntervalMs: 2000,
  rulesApplied: false,
  recipientsPinned: 1,        // number of trusted recipients received
  cardCheckoutOpen: false,
  cardCheckoutProvider: null
}

Bootstrapper presentCopy Anchor Link

The status doesn't tell you whether the bootstrapper is on the page. If only shield.js was pasted, the SDK works with reduced coverage and installationOrderValid stays true. To check:

typeof window.__PROTE_BOOT_TS__ === 'number' // true = the bootstrapper ran

Network requestsCopy Anchor Link

In the Network tab, filter by proteside:

A 401 on /config or /events means the key is invalid or was rotated more than 24 hours ago. In that case the SDK keeps running with its local defaults, but no events reach the dashboard.

What to expect in the first few minutesCopy Anchor Link

1. First few seconds: initialized: true in the console and the first POST /events.
2. Within 30 seconds: reload the dashboard. The top indicator switches to Proteside Active, and the page shows up in Detected pages.
3. First few minutes: the page's scripts show up in Scripts with the Needs review status. Review them and authorize the legitimate ones; see Scripts.
4. When a customer pays: the Payment Integrity cards move from WAITING to INTACT as each method is validated. See Payment integrity and Pix.

Next stepsCopy Anchor Link

• Configuration
• Troubleshooting