Store monitoring
Set rules for supported listing, rating, keyword and review signals. Get an alert when a collected observation matches a rule, then inspect what changed.
Both App Store & Google Play · 5 alert channels · Compare plans for monitoring access
How it works
Setup is explicit. Check your app’s available data and configure delivery before relying on an alert.
Select an app and review the data available for it. Monitoring observes changes; it does not modify your store listing.
your app, your rulesPick what matters: metadata diffs, rating drops below a threshold, rank regressions, review spikes. Rules route independently.
Choose in-app, email, Slack, Discord, Teams or webhook delivery. Review the recorded change and decide whether to act.
Features
Rules help you find changes worth reviewing; coverage depends on collected data.
Compare supported fields in stored observations of your listing. Review the recorded difference and timestamp; the comparison does not establish who caused it.
Check available screenshot-change observations alongside your listing history. Use the store page to confirm which artwork is currently public.
Set thresholds for supported rating and keyword-rank changes. Review the data and tune rules for the changes you care about.
Use review-spike rules to flag changes in the available review stream. Open the reviews to investigate what people are reporting.
Inspect supported listing-availability signals. A failed collection is not a verified takedown; confirm the store status before deciding how to respond.
Choose a delivery destination for each rule and test the connection. Available channels include in-app, email and supported webhooks.
FAQ
Set rules for supported listing metadata and screenshot changes, rating drops, tracked-keyword regressions, review spikes and listing availability. Alerts depend on the data AppDrift can collect for the selected app.
Rules are evaluated when the relevant checks run and new data is available. Review the timestamp on each observation and alert. Monitoring does not provide continuous surveillance or guarantee an alert before users see a change.
Rules support in-app delivery, email, Slack, Discord, Microsoft Teams and a generic webhook. Configure a destination for each rule and use the available test action to check delivery.
The history shows available stored observations and differences between them. Collection gaps and unavailable fields remain possible; a comparison is not a complete audit of every store action.
Store monitoring focuses on your own app. Use Competitor analysis for available rival listing, rating and screenshot observations; competitor keyword rank tracking has its own plan requirements.
Create an account, select your app and open Monitoring → Store monitoring. Compare plans for the intended monitoring allowance, choose a rule and configure its delivery. Starting setup does not send a store update.
Create an account to select your app and review setup. See pricing for monitoring access and plan allowances.
A monitoring alert identifies a recorded change that matched your rule. Open the app history, check when the information was collected and confirm the current store listing. Missing or delayed data can affect the picture.
After a listing update, use available store reports and observations to add context. An accepted API write, an alert and a visible public listing are different pieces of evidence.
Use Competitor analysis for rival listing observations, Review management to work through feedback and the weekly Action Plan to find the next task. Compare plans for access and allowances.