> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usedynamite.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Read /start/capabilities before choosing an integration. Use the deployed server’s tools/list for current tool inputs.

# Variants

> Define the versions a target can show.

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](https://docs.usedynamite.com/experiences/eligibility.md) 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.

> [accordion] Fields and shared components
>
> | Field | Purpose |
> | - | - |
> | `id` | Identifier within the target |
> | `description` | What the variant shows |
> | `hypothesis` | Why it may help |
> | `audiences`, `when` | Selection hints |
> | `value` | Text, HTML, order, or option value |
> | `componentId` | Shared component reference |
> | `requires…` | Eligibility requirements |
>
> 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](https://docs.usedynamite.com/internals/decision-pipeline.md) for validation and fallback behavior.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.