Home

Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Explore Events
Learn Clay here
Clay Cup

Powered by Tightknit

Fixing CSV Character Encoding Issues for Exported Files | Clay

Fixing CSV Character Encoding Issues for Exported Files

·

·

when exporting into a .CSV the I am getting the characters â€” in my personalised first line instead of - how do I fix this?

3 comments

· Sorted by Oldest

Clay Support
APP
·
·
The characters "â€"" appearing instead of "-" in your CSV export is a character encoding issue. This happens when special characters aren't properly encoded during export.
To fix this:
Use UTF-8 encoded CSV files - Make sure you're using UTF-8 encoding when working with your CSV files for the most reliable results.
Try the Google Sheets workaround - Upload your data to a public Google Sheet, then download it again as a CSV and attempt the upload once more. This often resolves encoding and formatting issues.
Create a clean export view - Before exporting, duplicate your current view and hide columns you don't need. Focus on including only the raw values you need for a cleaner export. [1]
If the issue persists after trying these steps, please ask to speak to a human for further assistance.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the character encoding issue in your CSV export, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other challenges you’re facing?