Hey!
It sounds like there might be an issue with the field mapping between Clay and Smartlead. Here are a few things to check that should help resolve the issue:
1. Ensure Field Names Match
• Double-check that the custom fields in Smartlead match exactly with the fields you’re pushing from Clay. Even small differences, like spaces or capitalization, can cause issues.
2. Mapping in the Integration
• When setting up the integration in Clay, ensure that you’ve correctly mapped each field to the corresponding custom field in Smartlead. You can do this by reviewing the field settings during the setup.
From there you can also use the Smartlead Lookup to check for the contact if it has the value and uder which name.
3. CSV Export Troubleshooting
• If you’re manually exporting the data from Clay and uploading it to Smartlead, make sure the CSV file structure is correct. Check if the column headers in the exported file align perfectly with Smartlead’s expected fields.
4. Smartlead Campaign Settings
• Ensure that the campaign in Smartlead is properly set up to accept the data you’re importing, particularly with the right custom fields enabled for mapping.
If everything seems set up correctly and it’s still not working, try checking Smartlead’s field mapping documentation or reach out to their support to ensure nothing’s being missed on their end.
Let me know if you need any more help with this! 😊
.png){kind=logo}
