Why a job change is the trigger worth watching
Every B2B motion has a moment when the door is open. A champion who loved your product moves to a new company: for one quarter they have a mandate to bring in what worked, and no incumbent vendor defending the ground. A new VP inherits a stack they did not choose and re-evaluates all of it. A key contact leaves an account you own, and the renewal you thought was safe suddenly is not.
All three of those moments are the same underlying event: a job change. Teams that systematically work job-change triggers see reply and conversion rates that cold lists never touch, because the outreach lands exactly when the recipient is rethinking everything anyway.
The catch is that the window is short. The first quarter in a role is when priorities get set and budgets get claimed. A trigger that reaches you after the window closes is trivia, not pipeline.
Detection lag is the whole game
Ask any team that has tried job-change alerts what went wrong and the answer is the same: the alerts were stale. Most providers refresh their records on a crawl cycle measured in weeks or months, so the "new" VP in your alert has been in the seat for sixty days, already flooded by everyone else who got the same late signal.
That is why every event in this stream carries its detection lag in days, right on the record, where you can check it. Run the tool above and read the stamps yourself: same day, again and again. We publish the lag on every single event because we can, and nobody else in this category detects moves at this speed and accuracy.
Same-day detection changes what the trigger is worth. You are not the fifteenth email in the congratulations pile; you are reaching out while the move is still news to most of the market.
From one dropdown to a full trigger pipeline
This page gives you the stream filtered one way: by event type. The API gives you eight parameters: the event type, specific organizations targeted by their stable IDs, city, country code, title keywords, a recency window in days, and full pagination through the stream. Watch every departure from your top fifty accounts. Catch every new engineering leader in Germany. Track every title change that includes "procurement".
Then the trigger becomes a pipeline, because every event links into a professional graph of 400M+ relationships on the same key: enrich the person to their full 50+ data-point profile, enrich the organization they joined, and find their new verified work email, all before your competitor’s weekly digest has even noticed the move.
That is the difference between a data feed and an identity layer: the event is not the end of the lookup, it is the entry point into everything Renidly knows about the person and the company on the other side of it.