A/B Testing Sequences
Split sequence traffic between two variants and compare outcomes
A/B testing lets you route contacts between two active sequence variants to compare outcomes.
Requirements
Before enabling A/B:
- Primary sequence is created
- Variant B sequence exists
- Both sequences have at least one step
- Variant B is active when executing
Configuration
In Sequence Settings:
- Enable A/B test.
- Select Variant B Sequence.
- Set Split Percentage (1-99%) for Variant B.
Example: 30% means 30% of enrolled contacts go to B and 70% stay in A.
How Assignment Works
During API/internal execution enrollment, each contact is assigned:
- Variant A (primary sequence)
- Variant B (configured variant sequence)
Assignment is random using your split percentage.
Operational Notes
- If Variant B is inactive or has no steps, enrollment is blocked.
- Keep variant names explicit (for example,
Post-Visit vAandPost-Visit vB). - Change only one major variable at a time (timing, message style, channel order).
Measurement Tips
Track differences in:
- Completion rate
- Review conversion
- Detractor resolution speed
- Response quality
Use Reports Overview and sequence metadata to compare outcomes over a meaningful sample size.
// Related articles
Sequence Settings Reference
Understand all sequence-level settings and how they affect delivery behavior
API-Triggered Sequences
Enroll contacts into sequences programmatically using the API
Sequence Status and Lifecycle
Understand draft, active, paused, and archived sequence states
Sequence Troubleshooting
Diagnose why sequences are not running or certain steps are skipped
Was this article helpful?
Let us know if you found this article helpful or if you need more information.
Join hundreds of businesses already using demeterrr to collect feedback, boost reviews, and grow faster.
Start Your Trial