Skip to main content
Notifies you when tracked individuals experience career changes such as job departures, promotions, additional roles, or moves to new companies. This radar type helps you monitor contact movements and relationship changes.

Content Structure

The content object contains the job change information:

Change Types

Change Type Examples

Role Object Structure

Both new_role and previous_role objects contain: Both role objects are always present in the payload with a consistent structure. Structural nulls: When a change type leaves an entire object empty (e.g. departure → all new_role fields null, additional_role → all previous_role fields null), this is indicated in the Change Type Examples table above. Data nulls: Within a populated object, end_date is null when the role is current. company_domain may be null if the company has no public domain. Other fields are populated whenever the data is available from the source.

Examples

These examples include base webhook fields along with contact-job-change-specific content. Select a change type to see its payload shape.

Important Notes

Contact Identification: Radar creation accepts an individual email, a LinkedIn person profile URL (linkedin.com/in/...), or a full name. Role-based/shared emails and company, school, or legacy /pub/ LinkedIn URLs are rejected. Within the same company and radar type, duplicate matching uses email or the normalized LinkedIn profile URL; full name alone is not a duplicate key. Multiple Contacts: You can track multiple individuals at the same company with separate radars. Contact Identifiers in Payload: The data object echoes back the identifiers you supplied at radar creation (profile_url, email, full_name). Only the fields you originally provided are included — if you created the radar with a LinkedIn URL only, email and full_name will be absent from the payload. Tracking Period: Changes are detected based on publicly available professional information. Previous Role Context: The previous_role object contains the role at the company you originally tracked, not necessarily the most recent role the person held. For example, if you’re tracking someone at Microsoft and they move to Meta, then later move to Google, the previous_role will show their Microsoft role (your tracked company), not their Meta role. Tracking Continuity: If you do not want to track contacts at new companies that TAMradar identifies, you should deactivate the radar. For example, if you’re tracking someone at Microsoft and they move to Meta, TAMradar will automatically start tracking their Meta role. Deactivate the radar if you only want to monitor the original company.