Understanding Duplications in Table Entries

Duplicates in your table occur when multiple rows have the same values in a specific column. To prevent this, enable Auto-dedupe: 1. Click the Auto-dedupe button at the bottom-right of your table 2. Toggle on "Enable automatic deduplication" 3. Select a column that serves as a unique identifier (like LinkedIn URL for people) 4. Click "Save changes" This automatically removes duplicate entries based on your chosen column.

Sources: Auto-update and Auto-dedupe Table Table management settings | Documentation | Clay University

Hey Miguel, thanks for reaching out. Can you enable auto-dedupe on the table like so:

Also, do you remember how many credits have you spent? Happy to add those. Also, a few tips to prevent wasting Clay credits: 1. Turn Off Auto-Update: Disable auto-update while setting up your table to avoid unnecessary credit usage. You can do this by clicking the three dots next to your table name and selecting "Auto-Update Columns" to toggle it off. Once your setup is finalized, you can turn it back on. 2. Qualify Leads Before Enriching: Enrich only the most relevant leads by filtering rows based on criteria like location or industry. Use Conditional Runs to set up rules for when enrichments should occur. 3. Test Enrichments on a Small Sample: Before running an enrichment on an entire column, test it on a small sample to ensure everything works as expected. 4. Use Your Own API Keys: Integrate your own API keys from other providers to reduce the credits spent in Clay. 5. Avoid Duplicate Enrichments: Use Lookup Columns to pull existing data into your current table to avoid spending credits twice for the same data.

For more details, you can refer to the Clay Credits Calculator and the Ways to Save Clay Credits guide.

That might be the case—it looks like all the rows were created today. What’s the source table you’re writing from? That’ll help me take a closer look.

Hey — to prevent duplicates in Clay, you can turn on Auto Dedupe for your table. That’ll make sure any incoming rows from Zapier (or other sources) don’t get duplicated based on a unique identifier like email or LinkedIn. Here’s how to set it up: https://docs.clay.com/en/articles/9642165-auto-update-and-auto-dedupe-table Also, even if duplicates are sent, they won’t be enriched again unless they’re new — so that should help avoid unnecessary credit use. Let me know if you want help configuring it.