Home

Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Hire GTME Talent
Explore Events

Powered by Tightknit

Job Change Signal: One Table vs. Persona-Specific Tables | Clay

Job Change Signal: One Table vs. Persona-Specific Tables

·Jan 12, 2026 01:34 PM·

Question on the job change signal. Would you recommend running everything in one table or splitting it by persona into separate tables? My assumption is that splitting into multiple persona based tables would be more expensive. Is that correct?

5 comments

· Sorted by Oldest

Clay Support
APP
·
·
Your assumption is correct - splitting into multiple persona-based tables would be more expensive. Job change signals cost 5 credits per result, so more tables means more credit usage. [1]
However, there's a practical limit: you can only connect a maximum of 10 tables across workbooks, and data can only flow in one direction (A → B → C). [2]
For job change monitoring, one table is usually more efficient. You can use the "Send row" feature to filter and segment results afterward if needed, which transfers specific columns to destination tables without the ongoing signal costs. [3]
Clay Support
APP
·
·
Is that what you were looking for?
Lennart L.
·
·
Thanks
Clay Support
APP
·
·
If you need any more help with your job change signal setup or have other questions, I’m here to assist. Would you like to share more about what you’re trying to achieve or any other details?
Clay Support
APP
·
·
You're welcome. If you have any more questions or need further assistance, feel free to ask.