Does 'source schedule' Feature Automatically Deduplicate Results?

Does the run "source schedule" feature dedup automatically? For example, there are 17k results from this source. If I re-run it, will it only bring in new names or just double the data?

7 comments

Channeled
APP
·
·
Clay offers auto-dedupe functionality to prevent duplicate records in your tables. Here's how it works: 1. You can enable auto-dedupe for your table, which continuously monitors a specified column to detect and remove duplicates by keeping the oldest row and deleting duplicates. 2. The auto-dedupe feature helps in two ways: • Keeps your table data clean by removing duplicates • Saves credits by preventing the same record from being enriched multiple timesTo set up a scheduled source: 1. Click the source column header and hover over "Sources" 2. Select the source you want to schedule 3. Choose "On a schedule" and set your preferred frequency (daily, weekly, or monthly)For best results, make sure to enable auto-dedupe on your table to prevent duplicate entries when the scheduled source runs. Sources: Configuring your table settings | Documentation | Clay University Auto-dedupe Table sources overview | Documentation | Clay University
Stefano
·
·
Hi Mathew, thank you for reaching out! Auto dedupe ensures that your table remains free of duplicate data. It works by checking a specific column, and if two rows have the same value in that column, one of them will be removed to prevent duplicates. Let me know if this helps!
Mathew I.
·
·
Yes but I don't have auto-dedup enabled
Mathew I.
·
·
Yet when I run the "scheduled" run of the source -- it auto-dedupes for me
Mathew I.
·
·
which is what I want -- just wanted to clarify
Mark L.
·
·
Hey Mathew, yes – duplicate rows would not be re-introduced. Behind-the-scenes, Clay keeps track of records surfaced by a particular source. If you import a row, and delete it later... or if it surfaces again in the search... Clay will know not to bring it into the table again.
Channeled
APP
·
·
Hi Mathew I.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: