Customer Aggregation Overview
The customer view aggregates your abuse events to customers using a customer ID. This type of aggreagation provides a quick way to learn what’s happening in your network with the smallest amount of configuration necessary. If an event can be matched to an existing customer ID, it will be appended; otherwise, a new customer object will be created. Customer aggregates do not yet support automation like cases do. Therefore, please use cases for that until further notice! You can access the customers view at: https://app.abusix.com/guardian/ops/customersRequirements
Required: Inbound Flow with API Resolver or IP Resolver The minimal requirement for customer aggregation is having a customer resolver in inbound processing. This can be as simple as having an IP resolver that resolves the event IP as a customer ID.Default View and Sorting
By default, the customer view is sorted by the amount of events each customer received so far, displaying customers with the highest volume of events at the top. You can sort the list by every column shown. Below you find two examples of the customer’s view:- The first one is configured with an IP resolver where you see the customer IDs being the IPs coming out of the events
- The second one shows where the customer ID is provided by an API resolver (metadata from the event such as IP and date is sent to an API that then responds with the customer identifier)
Customer View with IP Resolver: Basic customer aggregation using IP addresses as customer identifiers.
Customer View with API Resolver: Enhanced customer aggregation with enriched customer data from external API integration.
Filtering Options
Guardian Ops supports filtering to help you find specific information:- Customer IDs - Filter for specific customer identifiers
- Event types - Filter by particular types of abuse events
- Time intervals - Filter for specific time periods
Customer Details
When you click on a specific customer ID, you’ll be taken to the customer details interface. This page displays comprehensive information about that customer. This section displays key metadata about each customer, including:- Tenant ID - If a company has subsidiaries with non-unique customer IDs, the tenant ID can be used to distinguish between them
- Customer ID - ID to identify customers; it depends on how you set up your customer resolving in inbound processing
- Total Events - Count is dependent on retention settings. Therefore, only events that were not deleted by retention settings are counted
- Internal Comments - Can be added for context or collaboration
Comments
You can add internal comments to any customer for team collaboration and context sharing. These comments are visible only to your team members and help provide additional context about specific customers, ongoing issues, or resolution notes. Comments are particularly useful for:- Documenting customer communication history
- Sharing context between team members
- Recording resolution steps or escalation notes
- Tracking customer-specific handling procedures
Tabs and Navigation
The customer detail page includes the following tabs, with content varying based on your configuration:- Overview – Displays top event types and top reporters associated with this customer
- Cases – Shows linked cases when case groups are configured in your inbound processing
- Contracts – Displays contract information when provided by your API resolver
- Events – Lists all abuse events related to the customer
Overview Section
The Overview summarizes key insights at a glance:- Top Event Types - Shows the most common types of abuse events for this customer
- Top Reporters - Shows which entities have reported events most frequently for this customer
Customer Overview: Dashboard showing abuse pattern insights and top reporters for strategic response planning.
Cases Tab
The Cases tab displays all cases associated with this customer, providing a centralized view of ongoing and resolved cases.
Customer Cases: Centralized case management view enabling efficient tracking of abuse incidents and resolution progress.
Contracts Tab
The Contracts tab shows detailed contract information when provided by your customer resolver, helping you understand the customer’s service agreements and resources.
Customer Contracts: Service agreement details and resource allocation information for comprehensive customer context.
Events Tab
The Events tab lists all abuse events related to the customer, providing detailed event history and patterns for thorough analysis.
Customer Events: Comprehensive event history enabling detailed analysis of abuse patterns and incident trends.