Tracking Job Changes for 150k Contacts in Hubspot: Any Limits?

Antonio V. · 2025-05-23 17:54:30.306098+00

Hey Clay team! I'm trying to track job changes for 150k contacts from Hubspot but it looks like it's not working. Is there any limit of contact volume for job changes signal? Thanks for your help in advance!

Tracking Job Changes for 150k Contacts in Hubspot: Any Limits? | Clay

7 comments

· Sorted by Oldest

Channeled
APP
·
·
While there's no explicit limit mentioned for job change signals specifically, there are likely practical limitations when monitoring such a large volume of contacts. From our case studies, we've seen examples of customers successfully tracking around 5,000 contacts for job changes. The job change signal costs 5 credits per result, which could become resource-intensive at your scale. The issue might be related to search filter limits. Similar to how search results can be limited per company, there may be processing constraints for very large datasets. To set up job change monitoring effectively: 1. Make sure you have LinkedIn URLs for all contacts 2. Consider monitoring smaller, high-priority segments first 3. Check if you have the appropriate plan level If you need more specific troubleshooting, please request human assistance by clicking "Talk to a person."
Sources: How Regency Supply used Clay to find niche prospects & automate research and scoring - The GTM with Clay Blog Track Job Changes Monitor for job changes | Documentation | Clay University Monitor for job changes | Documentation | Clay University
Bo (.
·
·
Antonio - Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Antonio V.
·
·
https://app.clay.com/workspaces/166653/workbooks/wb_0swsc7p4WHqfp2Vc6pn/tables/t_0swsc7pEYtnfxEFRQjv/views/gv_0swsc7qY5gKjGvPoWig
Antonio V.
·
·
This is the one, Bo
Bo (.
·
·
Hey — I see you’ve got a 50,000-contact job change signal search running. The issue seems to be that no initial check was made to map each person’s previous company, so Clay can’t detect a change. To fix it, you’ll need to recreate the search and make sure to map the previous company field first. That way, Clay can compare it to the new company and flag any job changes. Right now, it’s only showing new results without that comparison. Let me know if you’d like help setting this up.
(99 kB)
Antonio V.
·
·
Hey team! I see, but what about the volume? I want to track 75k contacts and the list limit is 50k - could I track that volume at once?
Bo (.
·
·
Hey, You won’t be able to track all 75k contacts in a single table since the limit is 50,000 rows per table. However, you can split the list across multiple tables, and everything should work just fine that way. Let me know if you want help setting that up.

Channeled
APP
·
·
While there's no explicit limit mentioned for job change signals specifically, there are likely practical limitations when monitoring such a large volume of contacts. From our case studies, we've seen examples of customers successfully tracking around 5,000 contacts for job changes. The job change signal costs 5 credits per result, which could become resource-intensive at your scale. The issue might be related to search filter limits. Similar to how search results can be limited per company, there may be processing constraints for very large datasets. To set up job change monitoring effectively: 1. Make sure you have LinkedIn URLs for all contacts 2. Consider monitoring smaller, high-priority segments first 3. Check if you have the appropriate plan level If you need more specific troubleshooting, please request human assistance by clicking "Talk to a person."
Sources: How Regency Supply used Clay to find niche prospects & automate research and scoring - The GTM with Clay Blog Track Job Changes Monitor for job changes | Documentation | Clay University Monitor for job changes | Documentation | Clay University
Bo (.
·
·
Antonio - Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Antonio V.
·
·
https://app.clay.com/workspaces/166653/workbooks/wb_0swsc7p4WHqfp2Vc6pn/tables/t_0swsc7pEYtnfxEFRQjv/views/gv_0swsc7qY5gKjGvPoWig
Antonio V.
·
·
This is the one, Bo
Bo (.
·
·
Hey — I see you’ve got a 50,000-contact job change signal search running. The issue seems to be that no initial check was made to map each person’s previous company, so Clay can’t detect a change. To fix it, you’ll need to recreate the search and make sure to map the previous company field first. That way, Clay can compare it to the new company and flag any job changes. Right now, it’s only showing new results without that comparison. Let me know if you’d like help setting this up.
(99 kB)
Antonio V.
·
·
Hey team! I see, but what about the volume? I want to track 75k contacts and the list limit is 50k - could I track that volume at once?
Bo (.
·
·
Hey, You won’t be able to track all 75k contacts in a single table since the limit is 50,000 rows per table. However, you can split the list across multiple tables, and everything should work just fine that way. Let me know if you want help setting that up.