When I CSV export people in whose names are some foreign characters like René or Stéphanie, it means that it will also contain the same character in LinkedIn URL. When exporting it completley messes up the record so the name and URL cannot be used for outreach. Ways to fix it?
To fix issues with CSV exports containing foreign characters, try these steps: 1. Use UTF-8 encoded CSV files for the most reliable results. 2. Remove commas, colons, and semicolons from your CSV data to prevent mixing up fields. 3. Create a dedicated "CSV Export View" in Clay: • Duplicate your current view • Hide or delete unnecessary columns • Focus on including only essential raw values 4. If problems persist, try uploading your data to a public Google Sheet, then download it as a CSV and attempt the upload again. If these steps don't resolve the issue, request human assistance by clicking on "Talk to a person" for further support.
Does clay offer exporting talbes to UTF-8 encoded CSV?
Yes, we offer exporting tables to CSV files. While our documentation doesn't explicitly mention UTF-8 encoding, it's recommended to use UTF-8 encoded CSV files for the most reliable results when working with Clay. To export a table, open it, click on "Actions," then "Export," and finally "Download CSV." This process will generate a CSV file that you can use in other applications or for further analysis.
It gives a CSV, but by the output of records it's visible that it's not UTF-8 encoded CSV.
While our documentation doesn't explicitly mention UTF-8 encoding for exports, we recommend using UTF-8 encoded CSV files for the most reliable results when working with Clay. To export a table, open it, click on "Actions," then "Export," and finally "Download CSV." If you're experiencing issues with foreign characters, try these steps: 1. Create a dedicated "CSV Export View" in Clay 2. Remove unnecessary columns 3. Focus on including only essential raw values If problems persist, upload your data to a public Google Sheet, then download it as a CSV and attempt the upload again. If these steps don't resolve the issue, please request human assistance by clicking on "Talk to a person" for further support.
By the time I export it to CSV the format of the records is already messed up, so I cannot fix it by changing the CSV to UTF-8 encoded CSV
To export tables from Clay to a properly UTF-8 encoded CSV and prevent issues with foreign characters, follow these steps: 1. Open the table you want to export. 2. Click on "Actions" > "Export" > "Download CSV". While our export process should generate UTF-8 encoded CSVs, if you're still experiencing issues with foreign characters, try these additional steps: 1. Create a dedicated "CSV Export View" in Clay: • Duplicate your current view • Hide or delete unnecessary columns • Focus on including only essential raw values 2. Use the "Encode URI Components" integration to encode text or lists, ensuring they're safe for use in URLs. If problems persist, upload your data to a public Google Sheet, then download it as a CSV and attempt the upload again. If these steps don't resolve the issue, please request human assistance by clicking on "Talk to a person" for further support.
Does clay export the CSV as a UTF-8 encoded CSV?
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.
.png){kind=logo}
