Keep: renewal radar

A movement watch on YOUR OWN sponsors: when one of them does something at another tracked event that an organiser would want to know about, the radar surfaces it, with the observation and its source. Retention protects revenue already booked.

Where: Keep in the left rail. Paste the sponsors you already have: one name per line, a comma-separated list, or a CSV (paste it or press Upload a CSV). Argus reports how many of them it tracks, then every dated move it observed on them elsewhere in the corpus.

The three watch classes

• Competitor at a comparable event. A sponsor of yours is now listed at an event comparable to your own. Worth knowing while you plan your renewal conversation.
• Tier down elsewhere. A sponsor of yours moved down a tier at another tracked event. An observed fact about their spending shape, with the page behind it.
• Gone quiet. A sponsor of yours has stopped appearing on rosters it used to be on, judged only against pages complete enough to show it. The same absence discipline as everywhere in Argus applies.

The radar recommends rather than records, so an absence it cannot read competently is left out rather than shown with a caution. Two cases are dropped: where the corpus still serves that company as a current sponsor of that same edition, and where the only evidence on file for them at that event is press coverage or the sponsor's own page, which can show a presence and can never show an absence. Argus counts every observation it leaves out for those reasons and keeps that count with the result, so a shorter list is never a silent one. Every one of those rows stays visible, labelled, in the signal stream.

The engagement path and the digest

Inside a Ducket workspace, the radar runs against an engagement's own sponsor roster with all three classes, and a radar section can ride your email digest. Both paths reuse the same strict matching rules as the sponsor-list check, so a radar row is about the company you mean rather than a name-alike.