Mark a finding as reviewed
Clear a finding from your queue by telling nebty what it is.
Before you start
Section titled “Before you start”You need an account with at least one brand set up, and a finding to review, for example a domain in Domain Monitoring, a result in Search, a profile in Social Media, or an ad in Ads. If you have not looked at a finding yet, start with Review your first finding to see how the Risk Score and AI Verdict work together.
- Open a finding. Go to the relevant tab for your brand, Domain Monitoring, Search, Social Media, or Ads, and open the finding you want to deal with.
- Read the signals that channel shows. In Domain Monitoring, that is the Risk Score and the AI Verdict. In Search, it is the AI Insights write-up. In Social Media and Ads, it is the AI relevance badge on each card. They tell you how likely the finding is to be impersonation and how much attention it deserves.
- Pick the outcome that fits:
- This is us: the domain, profile, or ad belongs to you. nebty stops flagging it.
- Not relevant: it is not impersonation and not worth pursuing.
- Threat: it is genuine impersonation. This is the starting point for a Takedown.
- Repeat for the next finding. Working through your queue this way keeps the dashboard focused on what actually matters.
This same vocabulary, trusted, not relevant, or genuine threat, applies to findings across all four monitored channels, Domain Monitoring, Search, Social Media, and Ads. The exact control looks a little different per channel; Domain Monitoring and Search also offer a direct Request Takedown action, but once you know what each outcome means, it carries over everywhere.
What happens next
Section titled “What happens next”Once you triage a finding, it moves out of your active review queue. “This is us” and “Not relevant” close the finding out. Marking a finding “Threat,” or using Request Takedown directly in Domain Monitoring and Search, opens a takedown request that you can follow from the Takedowns area. How quickly a takedown resolves depends on the case, so treat triage as the start of the process, not the end of it.
Try triage in the demo(opens the public demo with sample data)Related: Domain Monitoring