Subscriptions: Continuous App Monitoring

Subscriptions is the screen for configuring continuous monitoring.

A subscription runs automatically while it is active. When ASO.dev detects a change, it creates an event. The event appears in Notifications and can also be delivered by push notification or webhook.

100%

Subscriptions: Continuous App Monitoring

100%

Subscriptions: Continuous App Monitoring

One subscription answers one question:

what should ASO.dev monitor, where, and for which app?

Formally, one subscription is:

1 app × 1 country × 1 event

Examples:

• monitor new reviews for your app in the United States
• monitor new reviews for a competitor in Germany
• monitor auction state when that event type is available

Subscription limits are applied per user:

The limit shows how many active monitoring rules a user can create.

Note: plan limits and conditions may change in the future at the discretion of the ASO.dev team.

The event list will expand. The main purpose of Subscriptions is to automatically catch changes you do not want to miss.

The subscription triggers when new reviews appear for the selected app and country.

Use it to track feedback across markets or competitors without manually checking the App Store.

When creating a subscription, choose:

• app
• country
• event type
• delivery channel

If you work with competitors, you can quickly add them from related ASO.dev screens.

For memberships with access to the ASO analysis: Indie, Pro and Marketing

A push notification is sent when a subscription detects a change. The event also remains in Notifications, so you can open it later.

Available only for the Pro and Marketing memberships.

A webhook is triggered on every update and sends the result as CSV.

The CSV file is publicly accessible, does not require authorization, and contains the latest event state.

Webhook features include:

• test button
• stable format for automation
• delivery on every update

Where to get a webhook URL for ASO.dev

In ASO.dev, paste a webhook URL into the webhook field. We will send subscription reports to that URL. Create this URL first in the service where you want to receive reports.

Start with direct integrations: Slack, Discord, Telegram, and Microsoft Teams.
For Telegram, create a bot with BotFather and use a Telegram Bot API URL. For the other services, create the webhook URL in the service settings.
If you need another tool, use Make, Zapier, n8n, or Pipedream as the middle step.

A webhook URL is usually a long HTTPS URL. It works like a secret delivery address for reports, so do not publish it publicly.

After pasting the URL into ASO.dev, click the test button to check that the report reaches the selected service.

Slack

Slack can generate a direct incoming webhook URL for a channel.

Where to get the URL:

1. Open the Slack App settings or create a new Slack app.
2. Enable Incoming Webhooks.
3. Click Add New Webhook to Workspace.
4. Choose the channel where reports should arrive.
5. Copy the URL that starts with https://hooks.slack.com/services/....
6. Paste this URL into ASO.dev and send a test.

If the test does not appear in the channel, use Make, Zapier, n8n, or Pipedream: copy the webhook URL from the automation tool, paste it into ASO.dev, then add a Slack message step.

Discord

Discord can generate a webhook URL for a specific channel.

Where to get the URL:

1. Open the server or channel settings. You need permission to manage webhooks.
2. Go to Integrations -> Webhooks.
3. Create a new webhook.
4. Choose the channel where reports should arrive.
5. Copy the webhook URL.
6. Paste this URL into ASO.dev and send a test.

If the test does not appear in the channel, use Make, Zapier, n8n, or Pipedream and send the report to Discord through a separate step.

Telegram

Telegram does not provide a simple webhook URL that you can copy from a chat or channel. For direct delivery, create a Telegram bot with @BotFather and use the Telegram Bot API URL.

Where to get the URL for ASO.dev:

1. Open @BotFather in Telegram and send /newbot.
2. Set the bot name and username, then copy the bot token.
3. Add the bot to the chat, group, or channel where reports should arrive. For a channel, make the bot an administrator.
4. Send any message in that chat, or press Start in a direct chat with the bot.
5. Open https://api.telegram.org/bot<BOT_TOKEN>/getUpdates and find the chat.id value. For a public channel, you can use @channel_username.
6. Build the Telegram Bot API URL: https://api.telegram.org/bot<BOT_TOKEN>/sendMessage?chat_id=<CHAT_ID>
7. Paste this URL into ASO.dev and send a test.

In ASO.dev, paste the Telegram Bot API URL.
Do not paste a t.me link, a separate bot token, or a URL from an automation service.
The URL contains the bot token, so keep it secret.

Microsoft Teams

For new setups, use Teams Workflows. Avoid choosing old Teams Connectors for new integrations.

Where to get the URL:

1. Open the target channel or chat in Teams.
2. Select More options -> Workflows.
3. Choose a webhook alerts template for a channel or chat.
4. Save the workflow.
5. Copy the webhook URL from the workflow page.
6. Paste this URL into ASO.dev and send a test.

If the report should look like a card or a message in a specific format, add formatting inside the Teams Workflow.

Integrations through Make, Zapier, n8n, or Pipedream

Use this option when the target service does not provide a ready webhook URL or when the report needs to be forwarded to another tool.

Where to get the URL for ASO.dev:

1. Create a new scenario, zap, or workflow in Make, Zapier, n8n, or Pipedream.
2. Choose an incoming webhook as the first step:
   • Make: Webhooks -> Custom webhook
   • Zapier: Webhooks by Zapier -> Catch Hook
   • n8n: Webhook
   • Pipedream: HTTP / Webhook
3. Copy the URL shown by the service.
4. Paste that URL into the subscription webhook channel in ASO.dev.
5. Send a test from ASO.dev.
6. After the test works, add the next step: send a message or save the report in the target service.

For n8n, use the test URL only while setting up the workflow. After enabling the workflow, paste the production URL into ASO.dev.

1. Create a subscription.
2. ASO.dev regularly checks the selected app, country, and event.
3. If the state changes, an event is created.
4. The event appears in Notifications.
5. If push or webhook delivery is enabled, ASO.dev sends the event through the selected channels.

• you need to monitor reviews continuously
• you want to notice competitor activity quickly
• you need events without manual checking
• you want to send events to an external system by webhook

Subscriptions run continuously and create events when something changes.

Tasks run once and create one report or export.