Alerts
TrustData automatically monitors your tracking health and alerts you when something needs attention. Critical alerts are enabled by default—no setup required.
Default alerts
When you create an attribution ID, these alerts are enabled automatically:
| Alert | Trigger | Severity |
|---|---|---|
| Tracking Error | SDK errors or failed event ingestion | Critical |
| Sync Failure | Data source sync fails | Critical |
| Data Freshness | No new data for 24+ hours | Warning |
You'll be notified immediately when any of these issues occur.
Alert tiers
Tier 1: Real-time alerts
Event-driven alerts that trigger immediately when issues are detected.
| Alert Type | Trigger |
|---|---|
| Tracking Error | SDK errors or failed event ingestion |
| Consent Blocked | Events blocked due to consent issues |
| Sync Failure | Data source sync fails |
| Rate Limit | Event volume exceeds limits |
These alerts use a rolling window (default 24 hours) and include cooldown periods to prevent alert spam.
Tier 2: Analytics alerts
Scheduled alerts based on analytics thresholds.
| Alert Type | Trigger | Default Threshold |
|---|---|---|
| Conversion Drop | Conversions decline vs. baseline | 15% drop |
| Revenue Variance | Revenue differs from expected | 15% variance |
| Data Freshness | No new data received | 24h warning, 48h critical |
| Attribution Drift | Attribution results shift unexpectedly | Configurable |
| Consent Rate Drop | Consent acceptance rate declines | Configurable |
Viewing alerts
Overview page
The main overview shows health status for all your properties. Each attribution ID displays:
- Health status indicator (Healthy, Warning, Critical)
- Number of active alerts by severity
- Click on the health status to access the alerting deep dive for that attribution ID
Alerting deep dive
When you click on an attribution ID's health status, you access the alerting deep dive page. This page contains:
Active Alerts
- List of currently active alerts for this attribution ID
- Alert type, severity, and when it started
- Actions to acknowledge or resolve each alert
- Direct links to fix issues (e.g., reconnect a data source)
Tracking Health Metrics
- Event volume (last 24 hours) with trend vs. average
- Time since last event received
- Current consent rate with trend
- Current adblock rate with trend
Data Source Status
- Status of each connected data source (SDK, Google Ads, Meta Ads, Shopify, etc.)
- Last successful sync time for each source
- Error details for any failed syncs
Alert History
- Past alerts for this attribution ID (last 30 days)
- When each alert triggered and resolved
- Duration of each incident
Alert Settings
- Customize thresholds for this specific attribution ID
- Configure notification preferences
- Add optional alerts (Conversion Drop, Revenue Variance, Consent Rate Drop)
Alert status
Alerts have three statuses:
- Active: Alert triggered and needs attention
- Acknowledged: Someone is investigating
- Resolved: Issue fixed, alert cleared
Severity levels
| Severity | Meaning | Action |
|---|---|---|
| Critical | Data loss or tracking failure | Immediate investigation |
| Warning | Potential issue, degraded performance | Review within 24 hours |
| Info | Notable change, no action needed | Review at convenience |
Adding custom alerts
Beyond the default alerts, you can add custom alerts for specific metrics:
- Go to the alerting deep dive for an attribution ID
- Navigate to Alert Settings
- Enable additional alert types and configure thresholds
- Save changes
Recommended additional alerts
| Alert | Type | Threshold | Use Case |
|---|---|---|---|
| Consent Drop | Consent Rate Drop | >10% decline | Detect broken consent banners |
| Conversion Drop | Conversion Drop | 15% | Catch performance or tracking issues |
| Revenue Variance | Revenue Variance | 20% | Investigate unusual patterns |
Best practices
1. Check health status regularly
Make it a habit to check the overview page. Green across the board means your data is flowing correctly.
2. Act on critical alerts immediately
Critical alerts mean data loss is occurring. Prioritize fixing these before anything else.
3. Review alert history monthly
Look for patterns:
- Which alerts trigger frequently?
- Are there recurring issues with specific data sources?
- What's your average time to resolution?
4. Tune thresholds based on your data
If you're getting too many false positives, adjust thresholds. If you're missing issues, tighten them.