This usually happens because the Smartlead enrichment ran before all your data was updated.
Quick fix: Re-run the Smartlead integration after ensuring all your custom field data is populated.
For next time: Add a conditional run setting to only run the integration if all variables are present - this prevents empty fields from being pushed.
Also verify that your custom field names in Clay exactly match the variable names you set up in your Smartlead campaign (like {{subject_line}}, {{email_body}}). [1]
If you still need help with pushing custom variables from Clay to Smartlead, I'm here to assist. Would you like to provide more details about what you're trying to resolve or understand?
That's frustrating—let me help fix this. The issue is likely with the custom field mapping itself.
Check that your custom field names in Clay exactly match the variable names in your Smartlead campaign. [1] For example, if your Smartlead campaign uses {{subject_line}}, your Clay custom field must be named "subject_line" (exact match). [2]
Also verify you're mapping the custom fields to the correct columns containing your data—not just adding empty custom field names.
Can you double-check the custom field names match exactly between Clay and Smartlead?