Job Change Template: Understanding Unemployment and Re-Entries in Data

Travers N. · 2024-10-09 19:44:14.879997+00

In the job change template I'm often seeing blank results, which is fine, what I've found is this denotes that they have left the company I put in as historical, but they are now unemployed. I'm wondering, if they do end up starting somewhere else, will a new entry log in the table? Or since that person has already been logged as changing jobs, it will not fire through the table again?

Job Change Template: Understanding Unemployment and Re-Entries in Data | Clay

14 comments

· Sorted by Oldest

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Bruno R.
·
·
Hi Travers, thanks for reaching out. To clarify how the current job change table inputs function: * If you only provide a Person LinkedIn Url column, we 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, we 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. I hope this was helpful. If there's anything else I can assist you with, please let me know!
Travers N.
·
·
Got it. So for historical checks, it will not continue to enrich. I'm building a bunch of these tables and it looks like I bumped into a limit,. What is the current limit on the number of these tables allowed, and is there any way to increase it?
Bruno R.
·
·
The limit is currently set to three tables per workspace!
Bruno R.
·
·
I can submit a request to bump that limit for your workspace.
Travers N.
·
·
Thanks!
Travers N.
·
·
How often does the future signal run?
Travers N.
·
·
Yes, please - wondering how often the signal for future job changes runs 🙂
Travers N.
·
·
Also, if I have a webhook pushing linkedin URLs into the staging table that the job change table is pulling from, it will continue to pick those up, right? Or is it only the initial pull?
LuisArturo
·
·
Hey there Travers thanks for reaching out, to you answer your question this particular feature currently will run whenever out providers does a check for the info, which can take up to 35 days to do so. Also this feature will continue to pull any leads that exist in the table that it is connected to, as it is searching that table for the results.
Travers N.
·
·
Awesome. And just so I'm 100% clear, if someone were to change jobs twice, a notification would fire both times, right?
LuisArturo
·
·
If the double change is present in their LinkedIn profiles experiences then yes it would fire off twice.
Travers N.
·
·
Awesome. Thanks!
Channeled
APP
·
·
Hi Travers N.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Bruno R.
·
·
Hi Travers, thanks for reaching out. To clarify how the current job change table inputs function: * If you only provide a Person LinkedIn Url column, we 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, we 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. I hope this was helpful. If there's anything else I can assist you with, please let me know!
Travers N.
·
·
Got it. So for historical checks, it will not continue to enrich. I'm building a bunch of these tables and it looks like I bumped into a limit,. What is the current limit on the number of these tables allowed, and is there any way to increase it?
Bruno R.
·
·
The limit is currently set to three tables per workspace!
Bruno R.
·
·
I can submit a request to bump that limit for your workspace.
Travers N.
·
·
Thanks!
Travers N.
·
·
How often does the future signal run?
Travers N.
·
·
Yes, please - wondering how often the signal for future job changes runs 🙂
Travers N.
·
·
Also, if I have a webhook pushing linkedin URLs into the staging table that the job change table is pulling from, it will continue to pick those up, right? Or is it only the initial pull?
LuisArturo
·
·
Hey there Travers thanks for reaching out, to you answer your question this particular feature currently will run whenever out providers does a check for the info, which can take up to 35 days to do so. Also this feature will continue to pull any leads that exist in the table that it is connected to, as it is searching that table for the results.
Travers N.
·
·
Awesome. And just so I'm 100% clear, if someone were to change jobs twice, a notification would fire both times, right?
LuisArturo
·
·
If the double change is present in their LinkedIn profiles experiences then yes it would fire off twice.
Travers N.
·
·
Awesome. Thanks!
Channeled
APP
·
·
Hi Travers N.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: