> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/products/crm-automation/communication-channels/content-variations.md).

# Content Variations

Content Variations help in customizing any communication resource whether it's an Email, Popup, SMS, or any other content, based on the conditions rules system.

1. Simply enter any resource and click on Content Variations.
2. Click **Create** and enter the **Variation name**. If your label offers them, you can also pick the language or brand of the variation here.
3. Click on the new variation to edit the variation and the conditions

{% hint style="info" %}
The available variation properties can be configured for your label by contacting your Success Manager. While properties with predefined options (such as Language, Country, Brand, and Currency) are recommended to maintain clean variation logic, numeric and text properties can also be configured.
{% endhint %}

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FC9ITILSRooyqoPKMR6S5%2Fr2-017-shot-1-87ab96b4-72592b.png?alt=media" alt=""><figcaption><p>Creating a content variation with Add Custom Variations: 1 — Variation name; 2 — the Brand and Language conditions</p></figcaption></figure></div>

Once you click save you will be redirected to the content variations list, which can look like the following when having different variations. The priority of the variations is determined by the number of conditions. The more conditions a variation will have it will have top priority, if no variation will be found matching a user, the system will always fall back to the lowest priority/default.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-3e1c583101d15f25295f5cb2503b78b6e2441f7c%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure></div>

Within each individual property field, you can select multiple values using "OR" logic (for example, Language: English OR Spanish). When you configure multiple different property fields on the same variation (such as Language AND Country), all conditions must be satisfied ("AND" logic) for that variation to match a user.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FSRPvxbBb0bsQEYUBgqtI%2Fr2-018-shot-3-13fe9b0c-060c36.png?alt=media" alt=""><figcaption><p>Variation conditions: 1 — several values in one field mean OR (here German or Portuguese); 2 — values in different fields must all match (AND); 3 — the preview of the variation</p></figcaption></figure></div>

{% hint style="danger" %}
When creating a Popup variation, it uses the original popup template by default, but you can select and customize a different template for the variation if needed using the Template dropdown.
{% endhint %}

### Auto-Translation and Variation Management

### Auto-Translating Variations

For Email, SMS, Push, Inbox, and Popup resources, you can automatically generate localized variations using the **Add translations** button on the Content Variations tab. The system translates the content of your default resource into the selected languages and creates one new variation per language in **Draft** status for your review. Each new variation gets a language condition, and its name starts with the language code, for example `[DE]`.

### Variation Statuses

Each variation has an independent status:

* **Active**: Evaluated during live campaigns. Only active variations are matched against recipient properties.
* **Draft**: Saved but not evaluated for message sending. Recipients will fall back to other matching active variations or the default template.
* **Archived**: Disabled and hidden from evaluation. Archiving a base communication resource automatically archives all of its variations.

### Resource Cloning

When duplicating a communication resource, you can choose whether to clone only the base resource or to clone all its content variations along with it (the **Copy variations** switch in the clone dialog).

### Dynamic Personalization Alternatives

If you only need to swap specific dynamic values (such as brand logos, links, or localized text snippets) within a single template rather than authoring separate full variations, see [Tags, properties, and event data in the communication resources](/welcome/products/crm-automation/communication-channels/tags-properties-and-event-data-in-the-communication-resources.md) for using condition-based Label Tags.

### Frequently Asked Questions

**What happens if a user matches multiple content variations?**

The system selects the variation with the highest priority (the one with the largest number of condition rules). Exactly one variation is selected and sent per delivery. If several matching variations have the same number of conditions, the order between them is not fixed, so any one of them can be sent. Give such variations conditions that do not overlap.

**What happens if no variation matches the user?**

The user automatically receives the base **Default** resource (the original version authored before variations were added). The default resource has priority 0 and serves as the universal fallback.

**Can I edit a variation while a campaign is actively running?**

Yes. Updates to variation content take effect immediately upon saving in the Back-Office. Any subsequent message triggered by the campaign will use the newly saved content.

**How do I test or preview how a variation looks?**

Open a variation to see its content in the preview next to the form. To check which variation a player gets, open the default resource and send a preview to a test player: the message uses the variation that matches the profile of that player. When you send a preview from a variation, the test player must match the conditions of that variation, or the preview is not sent.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartico.ai/welcome/products/crm-automation/communication-channels/content-variations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.