Issues with Inaccurate Data in Experience Level Table

This table has many people who aren’t according to the initial request. I’ve asked for people who have less than 1 month of experience in their current role and I’ve received people like this. The biggest problem is that I don’t even get these data directly from the crawl to be able to actually stop the wrong contacts with a formula.

12 comments

Andreas W.
·
·
Hey Theo, just dropping in as a user here. She started the current role in August 202, so I can see how that would pup up in the results just when calculating. I can’t see the table obviously, but that may be a tweak you could try.
Theo K.
·
·
Yeah thanks that might be a bad example but I had a few others too.
Theo K.
·
·
I will share more Andreas W. but yeah you re right on this one.
Andreas W.
·
·
got it, what’s the method you’re using? Screenshot/video… Only the Clay team can see the table ofc 🙂
Theo K.
·
·
Here is another example.
Theo K.
·
·
Here is the search (it’s a Clay People Search)
Daniela D.
·
·
Thanks for jumping in Andreas! Hey Theo! Thanks for reaching out. I ran a quick check with the examples you shared. Noticed one source in the table was filtered based on the maximum number of months as 1 and the second source was filtered based on the minimum number as 1. The condition "Minimum Number Of Months Since Start Date Of Current Role: 1" means that it will capture anyone who has been in their current role for at least one month, which includes those who have been in the role for 1 month, 2 months, or even longer. The example you shared was imported via the second source in your table. That's why they were included in the results, because a "minimum of 1" was used in the filter. On the other hand, the filter "Maximum Number Of Months Since Start Date Of Current Role: 1" will include people who have been in their current role for up to one month. This means it will import contacts who have been in their current position for 1 month or less. It will exclude anyone who has been in the role for more than 1 month. To only get, people within the 1 month range, "Maximum Number Of Months Since Start Date Of Current Role: 1" is the option to go with. Let me know if this helps! https://downloads.intercomcdn.com/i/o/1173482763/f300ed32628c4f978ec4e12d/CleanShot+2024-09-09+at+10_51_33%402x.png?expires=1725876900&signature=212c15d0432f6714a7a746578992ae255b0c93f9240dbaf993b6d7ab129787f1&req=dSEgFc12n4ZZWvMW1HO4zQOCwL%2FuHVS%2FTJ9xQYOeFLCr80jEVstsNtwry%2Bc3%0ACsRI%0A
Theo K.
·
·
Pfff I see thanks a lot 🙏 what about what Andreas shared? How can I avoid people who changed position but stayed within the same company? Daniela D.
Daniela D.
·
·
Thanks for the reply! There currently isn't a way to apply a filter for that directly in the search. However, you can use a formula to filter further after importing results into the table. The formula can look at the experience array in "enrich person" and tag any contact whose new position is within the same company. Shared an example formula below. Once that is done, you can filter your table based on contacts that fit your criteria or set conditional formulas for enrichments to only run for those contacts. Here's a quick guide for using AI formulas: https://www.clay.com/learn/how-to-use-ai-formulas Let me know if this helps. https://downloads.intercomcdn.com/i/o/1173541249/cb4fc216930e63fbb67c0cf2/CleanShot+2024-09-09+at+11_39_33%402x.png?expires=1725880500&signature=731fbe606c37636b2753302e743b83cbf5460c8f78d5f50fb745a7fa9507a2f2&req=dSEgFcx6nINbUPMW1HO4zSOL6zEJArYzDn3IXpYJVdZwXkwaOGUqE84%2FwV8v%0AggdF%0A
1
1
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Theo K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Andreas W.
·
·
Theo K. lemme know if you get stuck somewhere in your workflow happy to help in a short call or anything