Skip to content
AppDues
Log in
Contact salesSign up

Catch subscription issues before they cost you revenue

Revenue problems rarely announce themselves.

A renewal failure spike, a sudden revenue dip, or a wave of cancellations can sit unnoticed in a dashboard until the month closes. The alerting and app health features described here push those signals to your team the moment they happen — through email, Slack, Discord, or a custom webhook — so someone can investigate while there is still time to act.

Subscription event alerts

Beyond revenue totals, you can be alerted to specific subscription events: failed renewals, subscriber cancellations, billing issues, and more. These are the leading indicators that a revenue problem is forming. A renewal failure alert lets your support or billing team reach out before a paying customer churns silently. A cancellation alert tells your growth team where retention is slipping. Routing each event type to the right person is the difference between an alert that gets acted on and one that gets ignored.

Delivery to the tools your team already uses

Alerts are only useful if they reach someone. The platform connects to Slack, Discord, or any custom endpoint via webhooks, so events land in the channels your team already watches. Map events to channels deliberately:

  • Engineering — webhook endpoint for billing or infrastructure anomalies that need a technical response.
  • Support — Slack or Discord channel for renewal failures and billing issues that require customer outreach.
  • Growth / product — channel for cancellation spikes and revenue anomalies that inform retention work.

Email remains the delivery path for anomaly detection alerts. Messaging channels and webhooks carry the event-based alerts. Keeping those paths distinct prevents noisy overlap.

Refund Control for Apple refund requests

Refund Control is an upstream capability that automatically handles Apple refund requests using usage data and your refund preferences. It is designed to prevent auto-approved refunds and reduce refund fraud without manual review of every request. Note the scope: this feature addresses Apple refund requests specifically, and it works from the usage signals and preferences you configure. It is a complement to alerting, not a replacement — alerts tell you something happened; Refund Control acts on a defined class of refund events. Whether Refund Control is available to you depends on your own setup; confirm availability before relying on it.

A setup checklist

  1. Decide your anomaly mode. If you know your normal revenue band, start with a custom threshold. If not, enable auto detection first and add thresholds once you have a baseline.
  2. Pick the events that matter. Renewal failures and billing issues usually warrant immediate routing; cancellation alerts may be batched to a daily channel.
  3. Assign an owner per channel. An alert with no named responder is just noise.
  4. Connect your channels. Add Slack, Discord, or a webhook endpoint, and test that a sample event arrives where you expect it.
  5. Review Refund Control settings if you sell through Apple and want refund requests evaluated against usage data rather than auto-approved.
  6. Revisit after two weeks. Disable alerts nobody acted on and tighten thresholds that fired too often.

ConfigureTargetTest

Frequently asked questions

What is the difference between Custom Threshold Alerts and Auto Detection Alerts?

Custom Threshold Alerts notify you when revenue crosses a limit you define. Auto Detection Alerts surface unexpected revenue changes without you setting a number first. Both are delivered by email and both monitor your projects for potential revenue anomalies.

Which channels can receive alerts?

Anomaly detection alerts arrive by email. Subscription event alerts can be delivered to Slack, Discord, or any custom endpoint via webhooks, so your team sees them in the tools it already uses.

What kinds of subscription events can trigger an alert?

Renewal failures, subscriber cancellations, billing issues, and similar events. The goal is to notify your team before a problem compounds into lost revenue.

Does Refund Control replace alerting?

No. Refund Control is an upstream capability that acts on Apple refund requests using usage data and your refund preferences to prevent auto-approved refunds. Alerts notify your team about anomalies and subscription events. They serve different purposes and work together.