Replies: 6 comments 5 replies
|
Hey @jproz thank you for reaching us. We will expose the likelihood setting more freely @bosiraphael can you take a look at this? |
|
Hello @jproz, indeed all valid points. I will start working on the improvements and keep you updated when we roll them out. |
|
What do you mean by hosted plan exactly @jproz? We don't want BYOK on the cloud but self hosters are already free to provide their own keys |
|
I added the minimum likelihood as a workflow node optional parameter. For now the command menu item doesn't use the workflow directly because we have to wait the end of the workflow migration to implement it that way. So if you want to take advantage of these changes for now, you can create a workflow using the workflow nodes provided by the PDL app and set the minimum likelihood there. |
|
I don't know why you had an issue with 250 people enrichment cap. I couldn't find anything in the codebase that would implement such a cap. Are you sure you weren't just running out of credits? |

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hope this is the right place for this. I see Twenty built the People Data Labs integration. I've been using it and have a few pieces of feedback.
The reason I want it: the default drops to 2 whenever a record has a strong identifier (based on my spelunking). For LinkedIn URLs that's fine, since those match near-deterministically and score high anyway. But for records with an email and no LinkedIn, PDL's docs say those requests rarely score above 6, so every one of those matches lands in the 2-6 band that a threshold of 2 waves straight through. Their docs put a score of 2 at roughly a 10-30% chance of being the right person, and recommend 6 or higher wherever accuracy matters. https://docs.peopledatalabs.com/docs/input-parameters-person-enrichment-api
PDL uses 6 as the default in their own Salesforce integration: https://docs.peopledatalabs.com/docs/salesforce-integration-enrichment-settings
The practical effect is bad matches written to real records, and since matches are charged, I pay for them too. Keep 2 as the default if you like, but let me raise it.
BYOK on the hosted plan would be a huge win - even extra 100 free credits is a boon.
I hit a 250-person enrichment cap on my twenty account that seems to have locked me out of PDL app enrichment entirely. I gather it's a plan limit rather than anything in the app. If I'm paying a 20% margin over going direct to PDL, I don't follow why there's a cap at all. I only have around 300 more people left to even search, let alone match. And the low threshold makes the cap arrive faster, since weak matches consume credits just the same. (For what it’s worth, I’m actually totally fine with 20% margin - though I’m probably also paying some additional amount of credits for AI use on top?? - in support of your teams ongoing dev and less complexity; this is a one time cleanup and 250 annually with a 20% margin for auto update enrichment based in my criteria isn’t an awful trade off.)
Separately, and not part of the above: an Apollo option would be a nice-to-have if it's feasible. They have People Enrichment and Bulk People Enrichment endpoints, so the app should be close to what you've already built.
All of this comes from someone who really likes the product. Happy to give more detail on any of it.
It would also be amazing if someone could unblock my account with enrichment. ;) in the meantime, I’ve been using the free PDL API exposure, but I’ve just about blown through that monthly free 100 matches as well.
All reactions