Hi Michael, thanks for reaching out. Here's how the job changes signal setup works and how it impacts the functionality of the table outputs:
* If you only provide a Person LinkedIn Url column, Clay will track that list of people for any future job changes from the moment you create the Signal
* If you provide a Company LinkedIn Url (optional) column, Clay will do an initial historical check against the companies you provided. So e.g. if you say that Person X was at Company A, we will do a historical check to see if they're still in Company A, and if not, we will produce a Job Change event, regardless of when they started their current job. The use case for this is if customers want to check if their current data (e.g. from their CRM) is still up to date.
To make this work, we leverage several providers to aggregate reliable information on job changes. You can learn about what workflows you can build with this signal here. Let me know if you have any other question on the functionality!
.png){kind=logo}
