What are Alerts?
Alerts are notifications triggered by events or conditions in your project:- Coverage regressions - Material drops in overall AI visibility, share of voice, or top-of-answer performance
- Docs / source regressions - Your docs or source pages are showing up less often on prompts your team can improve
- Competitor threats - A competitor is gaining enough momentum to warrant attention
- Scheduled digests - Weekly summaries and actions digests
Alert Types
Immediate Alerts
Immediate alerts are for events that may need prompt attention.Coverage Regression
Use when you want an immediate alert for meaningful drops in core visibility signals.Docs / Source Regression
Use when you want a narrower alert focused on documentation and source coverage your team can directly improve.Competitor Threat
Use when you want to know that a competitor has crossed or escalated beyond a chosen threat level.Scheduled Reports & Digests
Scheduled notifications are useful to review, but not worth an interruption.Weekly Summary
A broader account and project summary delivered on a schedule.Actions Digest
A summary of waiting suggestions and accepted work across your projects. This can be delivered daily or weekly.Notification Channels
DevTune supports two notification channels:In-App Notifications
Alerts appear within DevTune:- Notification icon in the header
- In-app digest entries
Email Notifications
Receive alerts via email:- Configure delivery in your notification settings
- Choose which alert families should email you
- Set digest frequency where supported
Configuring Alerts
Notification Settings
Alert preferences are configured in your personal settings inside the team workspace:- Open the user menu
- Go to User
- Select the Notifications tab
- Configure your preferences across these sections:
- Notification Presets - Quick starting points for docs, growth / devrel, or founder-style notification bundles
- Notification Scope - Account-wide defaults or project-specific overrides
- Immediate Alerts - Coverage regression, docs / source regression, and competitor threat
- Reports & Digests - Weekly summary and actions digest
Per-Project Overrides
You can configure notification overrides on a per-project basis. This is useful when you want tighter monitoring on one project and lower-noise defaults everywhere else.Sensitivity and thresholds
Some alert families have extra controls:- Coverage regression and Docs / source regression use a sensitivity setting to control how aggressively incidents open
- Competitor threat uses a minimum threat level so you only hear about meaningful competitor movement
- Actions digest lets you choose a daily or weekly cadence
Managing Alert Volume
Avoiding Alert Fatigue
Too many alerts become noise:- Focus on the events that truly require your attention
- Set sensitivity and threat levels that filter out minor movement
- Disable alert types that you consistently ignore
Recommended Setup
Start with:- Coverage regression enabled
- Competitor threat enabled at a meaningful threshold
- Weekly actions digest enabled
Alert Tuning
Adjust over time:- If receiving too many alerts, lower sensitivity or raise the competitor threat threshold
- If missing important changes, enable more immediate alerts or add a daily digest
- Review alert effectiveness periodically
Reviewing activity and results
Alerts arrive under Notifications in the top bar. Open Results › Measured actions to review a live action’s result, then open the action for its lifecycle, comparison windows and change evidence.Best Practices
Start Simple
Begin with essential alerts only:- Coverage regressions
- Competitor threats
- Weekly or daily actions digests
Focus on Actionable
Only alert on things you will act on:- Ensure clear next steps exist for each alert type
- Alerts should prompt investigation or action, not just awareness
Regular Review
Periodically assess your alert configuration:- Are the alerts you receive useful?
- Are you missing important events?
- Do sensitivity or threat values need adjustment?
Team Coordination
If multiple team members are on the same team:- Coordinate who receives which alert types
- Avoid duplicate effort by assigning alert response ownership
- Use Actions to track responses to alerts
Troubleshooting
Not Receiving Alerts
If alerts are not arriving:- Check that the alert type is enabled in your notification settings
- Verify your email address is correct (for email notifications)
- Check spam/junk folders for email alerts
- Confirm the project is using the expected account-wide or project-specific settings
Too Many Alerts
If you are overwhelmed:- Lower sensitivity
- Raise the competitor threat threshold
- Disable low-value alert families
- Rely more on scheduled digests
Next Steps
- Actions queue - Respond to alerts with tracked work
- Personal Settings & Notifications - Open the Notifications tab to configure alert preferences