Issues with Exact Keyword Match Toggle for Job Titles | Clay

Issues with Exact Keyword Match Toggle for Job Titles

The toggle “Exact keyword match” for job titles does not seem te work, for example. It would be nice to for example specify job titles with regular expressions?

5 comments

Channeled
APP
·
·
I apologize, but I don't have specific information about an "Exact keyword match" toggle for job titles in our system. However, I can provide some insights on how we handle job title searches in Clay. Our job title search functionality typically uses keyword matching rather than exact matches or regular expressions. When searching for job titles, you can use comma-separated keywords to filter results. For example, you might input "Engineer, Software, Developer" to find relevant titles. For more precise filtering, some of our integrations allow you to use both include and exclude keywords for job titles. This can help you narrow down your search results more effectively. While we don't currently support regular expressions for job title searches, you can use multiple keywords and exclusions to achieve more specific results. If you need further customization, you might consider using our "write to table" feature to process the data after initial retrieval. Is there a specific use case or type of job title you're trying to match that the current keyword system isn't addressing?
Sources: Find Contacts at Company with Companies, People, Jobs Find Open Jobs with PredictLeads Map Job Title to Persona with Clay
Bo (.
·
·
Hey, Thanks for bringing this up. We’re currently rolling back an update that was affecting how current titles were being calculated. Normally, when you add people into the table and click on them, you should see the correct titles. We’re working on a better format and will roll it out shortly. For now, the titles still include a bit more than an exact match but only because they have an exact match in their title Let me know if you have more questions
Bo (.
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.
Rutger B.
·
·
Ah great!
Rutger B.
·
·
will test soon