Getting Started with Variants

Note: The Variants feature is currently available as part of an Early Access Program and may not be available to all users. For more information, you can reach out to our support team.

Variants enable personalized content delivery by creating different variations of an entry to cater to specific user needs, such as location, preferences, or attributes.

Note: Currently, variant groups and variants cannot be created, edited, or deleted within the stack.

This document explains key concepts and the functionality of variants.

Familiarize yourself with these essential terms:

1. Personalize Project: A project in Personalize allows you to manage and deliver personalized content across channels by linking it to an existing stack.
2. Experience: In Personalize, an experience defines and manages personalized content, A/B tests, or audience-specific variants to optimize content delivery and engagement.
3. Variant Group: A collection of related variants grouped for a common purpose or audience, such as location-based experiences or targeted promotions.

   Note: Each experience created in a Personalize project appears as a Variant Group in the linked stack.

4. Base Entry: The original entry from which all entry variants are derived. It contains the base content that all entry variants inherit unless they are customized for a specific variant.
5. Entry Variant: An entry variant is a customized version of the base entry, created to deliver personalized or scenario-specific content to different audiences.

   For example, a travel website could create variants like "Luxury Europe" or "Budget Adventure South America" to serve tailored content to specific regions.

Additional Resource: To learn more about the key terms within Personalize, refer to the Glossary and Key Features document

This section outlines the process of creating experiences, defining variants, and linking them to your stack.

1. Create an Experience: Set up an A/B test or segmented experience in Personalize to deliver content variations to different audience segments, optimizing engagement and conversions. These experiences are displayed as variant groups within the linked stacks.
2. Define Variants: Within each experience, define variants that describe the user experience. For example:
   • For a Color experience, you can create variants for different colors.
   • For a Marketplace experience, create region-based variants like Asia, Europe, or North America.
3. Linking to Stack: Link your Personalize project to a stack to inherit all experiences as variant groups within that stack.

This section explains how to manage variant groups to ensure personalized content delivery.

1. Linking Content Types: Connect variant groups to specific content types within your stack to create entry variants.
2. Unlinking Content Types: When you unlink a variant group from a content type, all associated entry variants will be disabled.

Learn how to create and manage entry variants for personalized content delivery.

1. Create Entry Variants: Within the entry editor, use the “[Base Entry]” dropdown to select a variant and create an entry variant.
2. Field Changes: Only fields you update in the entry variant will display the Variant Field tag, while all other fields inherit data from the base entry.
3. Versioning: Versioning: Once saved, an entry variant becomes independent of the base entry. You can manage versions, compare changes, or restore previous versions as needed.

Each entry variant can be published independently. You have full control over which entry variants are live at any given time. The following scenarios explain the publishing process:

1. If the base entry is not published in the required environment(s) and language(s), the system will first publish the latest version of the base entry, followed by the entry variant.
2. If the base entry is published in an older version, the system will skip republishing it and only publish the entry variant.
3. Similarly, if the base entry is already published in its latest version, the system will skip republishing it and directly publish the entry variant.

Note: Nested references for the base entry and entry variant will be published up to 5 levels, but entry variants of nested references will not. Learn more about publishing an entry variant.

Use APIs to manage and retrieve entry variants for personalized content:

• Content Delivery API: Retrieve specific entry variants via the Entry Variants collection in our Contentstack’s Delivery APIs.
• Content Management API:
  1. View all the available variant groups and link them to the content types within your stack via the Variant Groups collection in our Content Management API.
  2. Manage entry variants by creating, updating, deleting, publishing entry variants via the Entry Variants collection in our Content Management API.
• Applying Multiple Variants: Pass multiple variant UIDs in an API request to apply layered variants, with the latest entry variant taking precedence.

  For example, if you pass variant UIDs for Mumbai, India, and Asia, the Asia variant will take precedence, ensuring the content is most relevant to users in that location. This approach allows for flexible and granular content personalization across different markets or audience segments.

Understand how variants affect group fields, modular blocks, and sorting.

1. Group Fields: Only updated fields of a group field are saved within the entry variant; other fields inherited from the base entry remain unchanged.
2. Modular Blocks: Added or removed instances of block are handled appropriately, maintaining the base entry's structure.
3. Sorting and Reordering: Entry variants can have different order of instances in modular blocks or group fields. The final result will reflect the applied entry variant’s sorting and ordering.
4. Custom Attributes: If using custom attributes for audiences, ensure these are configured in the Personalize setup. The final variant selection will consider these attributes.

Key considerations when working with variants:

1. Field Limitations: The Taxonomy field does not support variants.
2. Branch Limitations: Variants are supported only in the main branch.
3. Publishing with References: When publishing entry variants, references are published up to 5 levels.
4. Delete Limitations: Deleted entry variants cannot be restored from Trash.

Additional Resource: Learn more about the limitations for entry variants.

By understanding how to use variant groups and entry variants, you can create tailored content experiences for your audience segments, boosting engagement and performance.