Skip to main content
A variant is an approved alternative for a target. Dynamite chooses a variant at visit time; it does not write new content during the visit. Start with the original and one or two alternatives.

​
Describe the reason for each variant

A useful hypothesis explains who the content helps and why:
Visitors exploring operations need implementation proof before requesting a demo.
That gives a customer story a clear purpose. Labels like “high-converting version” do not.

​
Add requirements when needed

Use eligibility requirements to limit when a variant can be considered. Descriptions, audience names, and when are selection hints; they do not enforce a rule. A matching requirement makes a variant eligible. It does not guarantee selection.

​
Keep related content together

Put a matching image, offer, and CTA in one component. Use separate targets when all combinations make sense. Your application still enforces prices, discounts, and access rules.
Editing a shared component updates all its draft references. Editing a variant’s HTML creates a private copy if its old component was shared. Draft edits take effect after publication.
See the decision pipeline for validation and fallback behavior.