I'm using Clay to enrich new contact and company records in Hubspot across the board. Basic process is: Company and/or Contact record created in Hubspot -> Webhook into Clay Company/Contact tables -> Enrichment (>15 properties on both objects) -> pushed back into Hubspot I'm worried about duplication with the enriched data:
Let's say the company name or URL changes (or another 'identifier')
This might be a bit pie in the sky but any tips on how to keep this 'tight' and actively set up to:
avoid duplication
Build de-duplication into the tables themselves so they can recognise duplicates and resolve them?
Hey Nick! Thanks for reaching out. Happy to help. Clay tables have an auto-dedupe setting that checks for duplicate records (using "exact match") in a specific column and automatically removes those records from your table. This can based on unique identifiers like a domain or LinkedIn url. To confirm, at what stage of the enrichment process are you most concerned about duplicate data? Would this be after running the enrichment for those records and updating in Hubspot? For context, duplicates tend to be more common for records that are not first searched for in Hubspot before running the integration. A way to mitigate that would be running Hubspot's lookup integration to first check for existing records. https://downloads.intercomcdn.com/i/o/w28k1kwz/1257955113/cbce433d05a9f7e13cdfba1d507a/CleanShot+2024-11-19+at+17_32_56%402x.png?expires=1732036500&signature=aa9ef8b0fb10f164785032031ca28ed3a2375bc6ecadeee7829aec4b97875890&req=dSIiEcB7mIBeWvMW1HO4zR%2BWLXEalM3jqB2sq8Q73Z%2F3FhgyetWs3k0bct2N%0AzZfd%0A
