Why did a signal disappear or change?
A signal can change because the data was still settling, or disappear because the situation it flagged resolved on its own — neither one is a bug.
This isn’t a bug. There are two distinct reasons a signal can change or disappear — it’s worth figuring out which one is your case.
Reason 1: the data was still settling
A signal built on volatile data — very recent, usually from today or yesterday — can change as that data settles over the following days. This happens because the source platform itself (Google, Meta, etc.) sometimes keeps adjusting its values after you’ve first seen them — a click logged late, a conversion attributed out of order. When that happens, the signal updates to reflect the final value, which sometimes means it stops existing.
It’s the same principle behind every signal’s confidence score: very recent data starts with lower confidence precisely to leave room for this kind of adjustment. We explain this in full in How Raveki understands your data.
Reason 2: the situation resolved on its own
A signal describes a situation — an unusual cost, a drop in a metric, an opportunity. If that situation stops repeating for several days in a row, Raveki considers it resolved and the signal stops showing as active. Raveki isn’t hiding anything — it’s reflecting that what was happening isn’t happening anymore.
If the situation happens again
If Raveki closed a signal because the situation stopped, and that same situation happens again later, the signal reopens on its own, without you needing to reactivate anything.