Issue with Importing Rows into Clay: Seeking Solutions

There could be a few reasons why your rows aren't importing even though the columns are loading properly: 1. File size: Ensure your CSV doesn't exceed 50,000 rows, which is our maximum limit. 2. Encoding: Use UTF-8 encoded CSV files for best results. 3. Column separators: Make sure your CSV uses comma-separated values. 4. File name: Keep the CSV file name short. 5. Import settings: When importing, check if you've selected "Save and run rows in this CSV" instead of "Save and don't run". If these don't resolve the issue, try uploading your data to a public Google Sheet, then download it as a CSV and attempt the upload again. If you still need help, request human assistance by clicking on "Talk to a person".

Source: How to import your CSV into Clay | Documentation | Clay University

If you've tried all the recommended steps and the rows still aren't importing, there could be a few other reasons: 1. Hidden formatting issues in your CSV file. 2. Incorrect column separators. 3. Incompatible file encoding. To troubleshoot further: 1. Try uploading your data to a public Google Sheet, then download it as a CSV and attempt the upload again. 2. Double-check that you've selected "Save and run rows in this CSV" instead of "Save and don't run" when importing. 3. Ensure you're using the correct import method: Actions > Import > Import Companies From a CSV. If these steps don't resolve the issue, request human assistance by clicking on "Talk to a person" for more in-depth troubleshooting.

Sources: How to import your CSV into Clay | Documentation | Clay University Import a File

If you're experiencing issues importing rows across multiple CSV files despite following troubleshooting steps, there might be some underlying formatting problems. Here are a few additional things to check: 1. Remove commas, colons, and semicolons from your CSV data fields. 2. Ensure your CSV uses either commas or semicolons as column separators consistently, not a mix of both. 3. Double-check that your files are UTF-8 encoded. 4. Verify that each CSV doesn't exceed 72 columns and 50,000 rows. If the issue persists after these checks, you may need more in-depth troubleshooting. Request human assistance by clicking on "Talk to a person" for further support.

Hey John - We're working on making improvements to CSVs but in the meantime, we've found users are often successful by first uploading the CSV to Google Sheets, exporting it from there, and then uploading into Clay. Do you want to share the CSV you're trying to work with?