Troubleshooting Clay and HubSpot Integration Issues: Domain Discrepancies

Dominic Musgrove · 2024-09-03 15:50:55.694815+00

Hi, I am having two issues with my Clay / HubSpot integration, can anyone help? • When companies and contacts are added to HubSpot from Clay, they are not always associating due to the domains being different from contact email vs company domain. • When doing a look up for companies in HubSpot, it doesn't always find the companies due to the domains not being the same in Hubspot when compared to the Clay search (the company has changed from .com to .io), meaning we create a duplicate company.

Troubleshooting Clay and HubSpot Integration Issues: Domain Discrepancies | Clay

7 comments

· Sorted by Oldest

Dominic Musgrove
·
·
It’s quite a few contacts, just wherever there is not a clear domain match. I was wondering if there was a way of associating them by using the company domain. For example on the contact record, the email domain is slightly different but if I add the company domain to the contact record and then it identifies associated contacts this way rather than using the email domain of the contact. Maybe it’s something to sort in HubSpot. For the lookup not finding all companies, I think the database enrichment seems to the best bet. What is the most effective way to do this using Clay, as we have about 30,000 companies in HubSpot, so would be an expensive clean up? Thanks for getting back to me so quickly
Daniela Debebs (Clay)
·
·
Hey Dominic! Thanks for the reply. The contact record create/update action uses the domain in a contact's email to match against the company's domain value. If the contact & company's domain data is updated, it'll help with avoiding mismatches or duplicate records being created. A way to check this is to first run company Lookup to get the domains currently on record, and match that against the email domains in the contact table, to identify records that don't match. For database enrichment, we recommend importing a Hubspot list (through the integration) of the records that need to be enriched. You can prompt Claygent to visit each domain and retrieve the website url that is displayed after loading each page. That url can be formatted using the "normalize a domain" feature (costs zero credits) and the final output can be used to refresh the domains in your CRM. Claygent Neon costs between 1-4 credits per record, depending on the record selected. Claygent Neon is recommended for these type of task, but if you connect with your own API key, that action won't cost Clay credits. Let me know if you have any questions!
Dominic Musgrove
·
·
Thanks for the reply? Would it not be worth just doing a basic company enrichment that cost 1 credit? Shouldn’t this identify domain / URL as well as other key information?
Daniela Debebs (Clay)
·
·
Hey Dominic! Thanks for the reply. Yes, you can use the "enrich company" option to do this as well and extract the domain that's returned there too. This works great if you also want to get other data points from the same enrichment, at a lower credit cost. We recommended Claygent as the option to use if domains are the primary data point needed. For context, with "enrich company", there may be instances where a website is not available or has not been updated yet in a provider's database. Claygent can run a direct check with the website url provided to confirm any changes. You can run a test with sample data for both to determine what's best for your use-case. Let me know if this helps. https://downloads.intercomcdn.com/i/o/1168447691/2f880f49b4a9083146059516/CleanShot+2024-09-04+at+13_18_15%402x.png?expires=1725453900&signature=33175517a076d4f205baaea32688e17779bcb25b2229645aff518b2a4b8b57aa&req=dSEhHs16modWWPMW1HO4zf4kxiXnLLpW2Gd1docoQbkULOR1MW9%2BeJk%2FHt1j%0AtPHl%0A https://downloads.intercomcdn.com/i/o/1168433532/aafba129fd63344ef48f4fef/CleanShot+2024-09-04+at+13_06_28%402x.png?expires=1725453900&signature=ee75e0f9accd4ddad3b1a916574091d7fda385eaa136fbc91db27b7f26bddd28&req=dSEhHs19noRcW%2FMW1HO4zSEz42vgPdbSGMyHuq02lwG%2BO9LHNUnBjkI6FHrq%0APNK4%0A
Dominic Musgrove
·
·
What would be your prompt for this use case?
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 Dominic Musgrove! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Dominic Musgrove
·
·
It’s quite a few contacts, just wherever there is not a clear domain match. I was wondering if there was a way of associating them by using the company domain. For example on the contact record, the email domain is slightly different but if I add the company domain to the contact record and then it identifies associated contacts this way rather than using the email domain of the contact. Maybe it’s something to sort in HubSpot. For the lookup not finding all companies, I think the database enrichment seems to the best bet. What is the most effective way to do this using Clay, as we have about 30,000 companies in HubSpot, so would be an expensive clean up? Thanks for getting back to me so quickly
Daniela Debebs (Clay)
·
·
Hey Dominic! Thanks for the reply. The contact record create/update action uses the domain in a contact's email to match against the company's domain value. If the contact & company's domain data is updated, it'll help with avoiding mismatches or duplicate records being created. A way to check this is to first run company Lookup to get the domains currently on record, and match that against the email domains in the contact table, to identify records that don't match. For database enrichment, we recommend importing a Hubspot list (through the integration) of the records that need to be enriched. You can prompt Claygent to visit each domain and retrieve the website url that is displayed after loading each page. That url can be formatted using the "normalize a domain" feature (costs zero credits) and the final output can be used to refresh the domains in your CRM. Claygent Neon costs between 1-4 credits per record, depending on the record selected. Claygent Neon is recommended for these type of task, but if you connect with your own API key, that action won't cost Clay credits. Let me know if you have any questions!
Dominic Musgrove
·
·
Thanks for the reply? Would it not be worth just doing a basic company enrichment that cost 1 credit? Shouldn’t this identify domain / URL as well as other key information?
Daniela Debebs (Clay)
·
·
Hey Dominic! Thanks for the reply. Yes, you can use the "enrich company" option to do this as well and extract the domain that's returned there too. This works great if you also want to get other data points from the same enrichment, at a lower credit cost. We recommended Claygent as the option to use if domains are the primary data point needed. For context, with "enrich company", there may be instances where a website is not available or has not been updated yet in a provider's database. Claygent can run a direct check with the website url provided to confirm any changes. You can run a test with sample data for both to determine what's best for your use-case. Let me know if this helps. https://downloads.intercomcdn.com/i/o/1168447691/2f880f49b4a9083146059516/CleanShot+2024-09-04+at+13_18_15%402x.png?expires=1725453900&signature=33175517a076d4f205baaea32688e17779bcb25b2229645aff518b2a4b8b57aa&req=dSEhHs16modWWPMW1HO4zf4kxiXnLLpW2Gd1docoQbkULOR1MW9%2BeJk%2FHt1j%0AtPHl%0A https://downloads.intercomcdn.com/i/o/1168433532/aafba129fd63344ef48f4fef/CleanShot+2024-09-04+at+13_06_28%402x.png?expires=1725453900&signature=ee75e0f9accd4ddad3b1a916574091d7fda385eaa136fbc91db27b7f26bddd28&req=dSEhHs19noRcW%2FMW1HO4zSEz42vgPdbSGMyHuq02lwG%2BO9LHNUnBjkI6FHrq%0APNK4%0A
Dominic Musgrove
·
·
What would be your prompt for this use case?
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 Dominic Musgrove! This thread was recently closed by our Support team. If you have a moment, please share your feedback: