Signals

Signals provide detailed counts of analyzed verification data across different data sources. While API Usage shows raw request counts, Signals reveals what types of verifications are happening across your account.

What Are Signals?

Signals represent the verification data analyzed by the Autheona Intelligence API. Each signal category corresponds to a specific data type that the API examines during verification requests.

A single API request can generate multiple signals based on your policy configuration. For example, if your policy checks both email validity and domain reputation, a single verification request increments counts across multiple signal categories.

Analyzing Signals by Date Range

Signals can be filtered by date using the date range picker. This allows you to:

• Compare verification patterns across different time periods
• Identify trends in your verification activity
• Investigate specific incidents or anomalies

Use the date picker controls on the Signals page to adjust the time range for your analysis.

Signal Categories

Signals are organized into three categories, each with a different availability status:

Email-Based Signals

Email-based signals show verification counts derived from email address analysis. This category provides comprehensive data on email verification activity, including:

• Email format and syntax validation results
• Domain reputation and deliverability signals
• Mailbox existence and validation status
• Risk assessment and fraud indicators

The email signals page displays extensive data about your email verification activity. Navigate to the email signals page to view detailed breakdowns of each verification type.

IP-Based Signals (Beta)

Fingerprint-Based Signals (Pending)

What Signal Counts Represent

Each signal count represents the number of verifications performed for that specific verification type. For example:

• If your policy checks email syntax validation, each request increments the email syntax signal count
• If your policy checks IP reputation, each request increments the IP reputation signal count
• A single API request can increment multiple signals based on your policy rules

Use Cases for Signals

Use Signals data to:

• Understand verification distribution - See which data sources are most commonly used in your verifications
• Detect anomalies - Identify unusual patterns that might indicate fraud or configuration issues
• Plan integrations - Understand what data your application sends to Autheona
• Compare time periods - Use the date range picker to analyze trends over time

Relationships Between Metrics