Curious about the best practice when using Clay and Instantly as a Sequencer, its related to using SpinTax to improve deliverability and test more variation in messages.

Question

If I create a clay table with
Name
Email
Subject 1
Body 1
Subject 2
Body 2
..... Then I can push this to Instantly and set the email templates up using just {{Subject 2}}  {{Body 2}} for example this is simple but it gives me very similar emails, but obviously with some personalization created in Clay workflows. It seems it's recommended to use SpinTax on your templates in instantly so how are people using this setup approaching building their email templates, are they using Clay for the list and basic personalization tokens and then building templates more manually in Instantly or something different?

Community Member · Accepted Answer

I usually handle data enrichment and basic personalization in clay (name, company, role, etc.) and leave template variations and spintax to Instantly.
workflow: 1. build the list in clay with all relevant personalization tokens.
2. create 1–3 core templates in Instantly and use spintax for subjects, intros, and body variations.
3. push the enriched clay table into Instantly and test to ensure spintax renders correctly with your tokens.
this keeps list management automated in clay while leveraging Instantly for deliverability and A/B testing.

Curious about the best practice when using Clay and Instantly as a Sequencer, its related to using SpinTax to improve deliverability and test more variation in messages.

1 Answer

Add your take