Skip to content
AppDues
Log in
Contact salesSign up

Send in-app purchase events to a Discord channel

Route subscription and purchase activity from your iOS or Android app into a Discord channel so the team sees changes as they happen, rather than checking a separate dashboard.

Deciding which events to send

Choose the events that matter to the channel. Sending every event can create noise, so a useful starting set is usually new purchases, trial conversions, renewals, cancellations and billing issues. Add expirations and product changes when support or retention teams need earlier warning.

Checklist before enabling:

  • Decide which channel should receive messages and who should be able to see purchase data there.
  • Select events by team need, not by default for all events.
  • Confirm how billing issues should be handled, because a failed charge does not necessarily mean access has ended.
  • Review product-change messages carefully, because a changed product is not always effective immediately.

Events you can connect

Initial Purchase: the first purchase of an auto-renewing subscription product that has no free trial.

Trial Started: a free trial for an auto-renewing subscription product begins.

Trial Converted: a free trial moves into its normal paid period.

Trial Cancelled: renewals are turned off during a free trial.

Renewal: an auto-renewing subscription renews, or is repurchased after a lapse.

Cancellation: renewals are turned off during the normal paid period.

Uncancellation: auto-renew status is turned back on for a subscription.

Non Subscription Purchase: any product that is not an auto-renewing subscription is purchased.

Billing Issues: a charge attempt for a subscriber fails. This alone does not mean the subscription has expired, especially where a grace period is enabled.

Expiration: a subscription has expired and access should be removed.

Product Change: the product attached to a subscription changes. The new subscription may not take effect immediately, so check subscription-management guidance for updates, downgrades and crossgrades.

Example: separating growth and retention signals

A common setup is to separate signal from noise. For example, send Initial Purchase, Trial Converted and Renewal to a growth channel, and send Billing Issues, Cancellation and Expiration to a retention or support channel. That way, a billing message prompts investigation while access may still be active, whereas an expiration message signals that access should be removed.

Related integrations

The integration is part of a wider no-code setup that connects real-time events and revenue data to other tools. Related integrations include Adjust, Apple Search Ads, Singular, Branch, SplitMetrics Acquire, Meta Ads, Tenjin and AppsFlyer. Use the documentation link to check the current setup steps before connecting a channel.

ConfigureTargetTest