Home

Clay Announcements
Discuss Anything
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

Discuss Anything

Discuss Anything

Best Practices for Using Clay Signals with Healthcare Subsidiaries and Salesforce Accounts

·Mar 09, 2026 05:03 PM·

Hey all! I am trying to identify the best way to approach Clay signals for subsidiaries. Has anyone found an optimal approach? I have a list of accounts from Salesforce, which are either a subsidiary of a parent company, or they have no parent company. These are small healthcare facilities, so using out-of-the-box Clay signals seems to only pull parent company data and connecting to the exact subsidiary has been a challenge. An example would be a new hire is showing up as a signal 5 times for all 5 subsidiaries, but in reality, the new hire only works at the corporate level, not at the specific facility/subsidiary. To pull signals, I used the specific facility-level domain, but it still pulls in the parent company. Additionally, these subsidiaries typically do not have a linkedin account, which is why I went the domain route. If anyone has insights here it'd be much appreciated!

3 comments

· Sorted by Oldest

Marvellous
·
·
I’ve seen this pain point with subsidiaries, signals often bleed from the parent company because Clay defaults to corporate domains. One approach is combining facility-level domains with Salesforce’s account hierarchy to filter out parent-level activity. You can also set up custom rules to only surface events tied to the subsidiary email patterns or unique identifiers. I’ve helped teams map signals this way to get cleaner, actionable data. Are you mostly trying to catch hires, or broader activity across the facilities? Jimmy G.
Jimmy G.
·
·
Hey Marvellous, thanks for reaching out! I started with trying to find new hires, but I'm also wanting to identify job change, job posting, and news signals. When you mention your approaches, are you doing that within their signals features? I find I am able to get to accurate results, when I enrich companies outside the signals feature, but I was hoping I could use their signals features, since that seems like the best way to avoid spending a ton of credits to identify signals.
Marvellous
·
·
For what you’re trying to do, you can stay within Clay signals but get more accurate subsidiary-level data by combining facility-level domains with Salesforce hierarchies and applying filters to exclude parent-level events. You can also set up custom rules for signals like hires, job changes, postings, and news so they only trigger at the subsidiary level. This keeps everything inside Clay and avoids unnecessary credit use from external enrichment. If you want, I can help you implement this directly so you start getting clean, actionable data right away, do you want to dive into that? Jimmy G.