At a glance
Save-Rate / Follower / Rating Threshold Crossed is the account-health alert that fires the moment any one of three core Depop signals breaches its safe band: save rate falls under roughly 2 per 1,000 views, follower growth turns net-negative, or average rating drops below about 4.7. Each of these on its own is an early warning that the algorithm is about to reduce your reach. Bundled into one alert, they give the owner a single place to catch account-health erosion before it shows up in sales.
| What it counts | The number of live breaches across three thresholds: save rate, net follower growth and average rating. Listed as individual alert items. |
| Sample type | Backend API data from Depop, refreshed on the standard data refresh, evaluated in real time. |
| Why it matters | These three signals are the inputs Depop’s discovery leans on. When any crosses its line, reach and ranking are at risk, and revenue follows with a lag. The alert buys you time to act before the slide compounds. |
| Reading the value | Zero is the healthy state. Any item on the list names which signal breached and by how much, so you know whether to fix content, cadence or service. |
| Currency | count (open breaches) |
| Time window | RT (real-time) |
| Alert trigger | save-rate < 2 per 1,000 OR follower growth net-negative OR rating < 4.7 |
| Sentiment key | dep_alert_account_health_drop |
| Roles | owner, operations, finance |
Calculation
The card evaluates three thresholds in real time and lists each breach as an alert item. Save rate, net follower growth and average rating are read from the Depop integration; each threshold is configurable in the Sensitivity tab. The illustrative defaults are 2 saves per 1,000 views, net-negative follower growth, and a 4.7 rating floor.Worked example
A representative reading of Save-Rate / Follower / Rating Threshold Crossed for a typical resale shop on Depop. On 14 Jun 26 the alert surfaced two items: save rate had fallen to 1.6 per 1,000 and follower growth had turned net-negative for the week, while rating held at 4.8. Vortex Mind linked both to a stretch of listings shot in poor light plus a pause in daily relisting. Because rating was still safe, the owner knew this was a content-and-cadence problem, not a service problem, and acted accordingly. Reshooting lead photos and resuming relists cleared both breaches inside two weeks. To see the full breach history, ask Ask Viq when account-health thresholds were crossed this quarter.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
dep_save_rate | Source signal: the save-rate threshold in this alert. |
dep_follower_count | Source signal: the follower-growth threshold in this alert. |
dep_rating_average | Source signal: the rating threshold in this alert. |
dep_marketplace_health_score | Composite sibling: rolls the same signals into one score. |
dep_revenue_at_risk | Outcome sibling: quantifies what these breaches put at stake. |
Reconciling against Depop
Where to look in Depop’s own dashboard: Depop does not bundle these three signals into a single alert. To reconcile, check each underlying figure in its own place: save rate and views in listing insights, follower total on your profile, and rating on your shop page. The alert simply watches all three at once. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Threshold settings. Each line is configurable; defaults are illustrative. | Variable | Confirm your Sensitivity tab values. |
| Net vs gross follower change. The alert uses net growth, not the level on your profile. | Variable | Compare net growth, not headcount. |
| Refresh timing. Breaches clear on the next refresh after you recover. | Marginal | Force a manual refresh after fixes. |