Proteside Docs

Dashboard

See at a glance whether the checkout is protected, what to do first, and the store's numbers, activity, payments and alerts.

The Dashboard is the first screen after you sign in. It summarizes the protection of the selected store and tells you where to start: the state of the checkout, pending items in order of urgency, the store's numbers, the activity of the last 30 days, the payment methods and the recent alerts.

The screen title greets you by name ("Good morning", "Good afternoon" or "Good evening", based on the store's time), and the subtitle shows Protection summary for followed by the store name.

The Dashboard only shows data. To act, follow the buttons on the cards or the View all shortcuts.

Dashboard with the protection summary (percentage of scripts reviewed, checkout status and checks), the What to do now section and the In numbers section
The protection summary (1), pending items in order of urgency (2) and the store's numbers (3).

Protection summary

The panel at the top (1) answers whether the checkout is protected.

On the left, the ring shows the percentage of scripts reviewed: authorized or blocked, out of the whole inventory.

In the middle you see Monitoring since with the date the SDK was first seen in the store, or SDK not detected yet. Below it comes the checkout status, followed by a sentence summarizing the monitored pages, the scripts detected and the pending alerts:

StatusWhen it shows
Your checkout is not being monitoredThe SDK hasn't received real visits from the store in the last 24 hours.
Your checkout needs attentionThere's at least one open critical alert.
Your checkout is protected, with N pending itemsScripts are waiting for review or alerts are open, none of them critical.
Your checkout is protectedNothing pending.

On the right there are three checks:

  • SDK active · Monitor mode (or Block), or SDK inactive in the last 24 hours;
  • X of Y scripts reviewed;
  • N open critical alerts or No critical alerts.

During a trial without a confirmed subscription, a banner with the days remaining and the Upgrade button appears right below. The button takes you to Billing.

What to do now

The What to do now section (2) shows up to three cards, In order of urgency. Each card says what to do and has a button that takes you straight to the right screen:

CardWhen it showsButton
Critical, with the alert titleThere's an open critical alert. The card shows the most recent one, with the page and how long ago it was detected.View and block opens the alert in Alerts.
N pending, Confirm your store's scriptsScripts are waiting for review. When some of them come from the store's own domain, the card says they can be approved together.Review scripts opens Scripts filtered to the pending ones.
Recommended, Register the store's Pix keyThe SDK is active and there's no Pix key among the trusted recipients.Register key opens Payment protection.
Required, Install the SDK on your payment pagesThe SDK hasn't received real visits in the last 24 hours.See installation opens Pages & Domains.

With nothing pending, the section shows Nothing pending here.

In numbers

The In numbers section (3) has four indicators:

IndicatorWhat it counts
Monitored pages (30 d)Distinct checkout pages where the SDK ran in the last 30 days, with real customer visits. Addresses on different domains count separately: checkout.mystore.com/ and www.mystore.com/ are two pages. Proteside's automated checks aren't counted.
Scripts in inventoryEvery script the SDK has seen in the store, in any status. The line below shows how many are approved and how many are pending (Needs review and Suspicious).
Active alertsOpen alerts, broken down by severity (Critical, High, Medium, Low). The number turns red when there's a critical alert.
Avg. detection timeAverage time, in milliseconds, the SDK took to detect the threats in alerts from the last 30 days. Shows No data when no alert in the period has this measurement.

Active alerts includes snoozed ones

Snoozed alerts are still open and count toward Active alerts. To see only the ones that need action, use the Open tab in Alerts.

Activity, payment methods and recent alerts

Lower part of the Dashboard with the Activity in the last 30 days chart, the Payment methods panel and the Recent alerts list
Activity in the last 30 days (1), payment methods (2) and recent alerts (3).

Activity in the last 30 days

The Activity in the last 30 days chart (1) has two parts, each with its own scale:

  • At the top, the green Customer sessions bars show how many times per day customers opened pages with the SDK.
  • Below, the areas show, per day, the New scripts (in blue), seen for the first time that day, and the Alerts (in red), created that day.

Days follow the store's time zone, set in Store. Hover over the chart to see the values for a day.

How to read it:

  • Green bars disappearing from one day to the next: the checkout may have lost the snippet. Check SDK Health.
  • Spike in new scripts: someone published a change to the site or a vendor changed its files. Review the new scripts in Scripts.
  • Spike in alerts with no known change to the site: investigate in Alerts first.

Payment methods

The Payment methods panel (2) shows the state of up to six of the store's payment methods, such as Credit card, Pix and Clipboard. You don't pick the methods: the SDK recognizes on its own the ones that show up at checkout.

StatusMeaning
IntactThe SDK checked a recent payment with this method and there's no open tampering alert. Clipboard becomes intact as soon as the SDK is active.
TamperedThere's an open tampering alert for this method. Open the details immediately. The status goes back to normal when you resolve the alert.
WaitingThe SDK is active, but hasn't checked any payment with this method yet.
Not configuredThe store hasn't received any event from the SDK yet.

View all opens Payment integrity.

Recent alerts

Recent alerts (3) shows up to five open alerts that happened in the last 7 days, from newest to oldest, with the severity and how long ago they were seen. Click an alert to open it in Alerts. View all opens the full list.

Store with no data

Right after installation, the Dashboard shows Your checkout is not being monitored and SDK not detected yet, and What to do now brings the Required card with Install the SDK on your payment pages. Recent alerts says "No active alerts — your checkout is clean.".

Publish the snippet, open the store's checkout in your browser and reload the Dashboard. If nothing changes, follow Verify the installation.

Next steps

On this page