Frequently Asked Questions

Product Features & Capabilities

What are Variants in Hygraph and how do they work?

Variants in Hygraph are personalized versions of content entries tailored to specific user Segments. Each Variant inherits the structure of the main entry but allows customization of certain fields, enabling content teams to deliver targeted experiences without duplicating entries. Learn more in the Variants documentation.

What is a Segment in Hygraph?

A Segment is a named reference used to target a group of users based on shared characteristics or behaviors, such as demographics, behavioral data, or engagement. Segments are managed externally and used in Hygraph to deliver specific content Variants to these groups.

How do Variants enable personalization and A/B testing?

Variants allow you to create different versions of content for different Segments, supporting personalization and A/B testing use cases. This enables you to deliver tailored experiences and measure engagement or conversion rates for specific audiences.

Can I use Variants for multi-regional or multi-brand strategies?

Yes, Variants are ideal for managing multi-regional or multi-brand strategies efficiently. You can create content tailored to different regions or brands without duplicating entries, streamlining content management for global teams.

What are the prerequisites for using Variants in Hygraph?

To use Variants, you must have set up a content model and created at least one content entry based on that model.

How do permissions work for Variants?

Variants inherit permissions from their content model. If a user can read, create, and update a model, they have the same permissions for Variants of entries based on that model.

Are there limits to the number of Variants I can create?

Yes, you can create a maximum of 30 Variants per entry. Segments and Variants count toward the content entries limits of your billing plan. Variants are available as an enterprise feature; contact the sales team for access.

How do I enable Variant support for fields in my schema?

To enable Variant support, go to the Schema Editor, choose your content model, and edit the field you want to add Variants to. Under Settings, select the 'Enable variants' checkbox. Note that Variant support cannot be enabled for unique or custom fields.

What happens if I disable Variant support for a field?

If you disable Variant support or delete a field with Variant support enabled, the field and its associated content are removed from all Variants.

Can I localize fields in the Segment model?

No, you cannot localize the fields of the Segment model in Hygraph.

How do I add a Segment in Hygraph?

In the Content Editor, under Variants, go to Segments and select 'Add entry.' Provide the name and optional description, then save or save & publish. Repeat to add multiple Segments.

How do I add a Variant and link it to a Segment?

Open your content entry in the Content Editor, then under Variants, select 'Add.' Edit the available fields, select the Segment(s) the Variant applies to, and save or save & publish. You must publish the Segment to the same stage as the Variant to see it.

How do I modify a Variant or its linked Segments?

You can update the values in Variant fields or modify the Segments linked to a Variant. To link more Segments, select and add them. To unlink, use the context menu next to a Segment and click 'Remove.'

How do Variant fields behave when updated?

Each Variant maintains its own values independently. Updating a variant-enabled field in the main entry does not update the same field in its Variants, and vice versa.

Do I need to publish Variants separately from the main entry?

Yes, publishing the main entry does not auto-publish its Variants. You must publish each Variant separately, and the main entry must be published first.

How can I use Hygraph Variants for personalization?

You can use Hygraph's Variants to achieve personalization by identifying user Segments in real time and dynamically delivering content based on the Variants set up in Hygraph. For complex setups, a personalization engine is recommended. See this guide for more details.

Where can I find API documentation for Variants?

The API reference for fetching Variants and Segments is available at API reference for Variants.

How do I set up live preview for Variants?

After setting up a preview for your main content entry, you can set up live preview for Variants by following the instructions in this guide.

Can I use Variants with a personalization engine or CDP?

Yes, Hygraph Variants can be combined with a personalization engine or Customer Data Platform (CDP) for advanced personalized experiences. See this guide for implementation details.

What are some practical use cases for Variants?

Variants can be used to show different homepage banners to users in different countries, highlight content based on browsing history, display metric or imperial units depending on region, or present different introductions for developers vs. marketers.

Where can I find more guides on working with Variants?

Additional guides on creating and editing Variants, setting up personalization, and frontend logic are available in the Hygraph documentation: Create Variants of content entries and Personalization example with frontend logic.

Pricing & Plans

What pricing plans does Hygraph offer?

Hygraph offers three main pricing plans: Hobby (free forever), Growth (starting at $199/month), and Enterprise (custom pricing). Each plan includes different limits and features. See Hygraph's pricing page for details.

What features are included in the Enterprise plan?

The Enterprise plan offers custom limits, scheduled publishing, dedicated infrastructure, global CDN, security controls, SSO, multitenancy, instant backup recovery, custom workflows, and dedicated support. Try the Enterprise plan for 30 days or request a demo at this link.

Is the Hobby plan really free forever?

Yes, the Hobby plan is free forever and ideal for individuals or personal projects. It includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, and more. Sign up here.

Technical Requirements & Documentation

Where can I find technical documentation for Hygraph?

Comprehensive technical documentation is available at Hygraph Documentation, including API references, schema components, webhooks, and AI integrations.

Does Hygraph provide APIs for content management?

Yes, Hygraph offers multiple APIs: Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. See API Reference Documentation for details.

What integrations does Hygraph support?

Hygraph supports integrations with DAMs (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), Adminix, Plasmic, and custom integrations via SDK or external APIs. Explore more in the Hygraph Marketplace.

How easy is it to implement Hygraph?

Implementation time varies by project complexity. For example, Top Villas launched in just 2 months, and Si Vale met aggressive deadlines smoothly. Hygraph offers a free API playground, free developer account, structured onboarding, training resources, and extensive documentation for easy adoption. See Top Villas case study.

Security & Compliance

What security certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure robust security and data protection. See Secure features page for details.

How does Hygraph ensure data security and compliance?

Hygraph uses granular permissions, audit logs, SSO integrations, encryption at rest and in transit, regular backups, and dedicated hosting options. It provides a process for reporting security incidents and uses ISO 27001-certified providers. See Secure features page.

Use Cases & Benefits

Who can benefit from using Hygraph?

Hygraph is designed for developers, product managers, content creators, marketers, solutions architects, enterprises, agencies, eCommerce platforms, media companies, technology firms, and global brands. Its flexibility suits SaaS, eCommerce, media, healthcare, and more. See case studies for examples.

What industries are represented in Hygraph's case studies?

Industries include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food & beverage, eCommerce, agency, gaming, events, government, consumer electronics, engineering, and construction. See case studies.

What business impact can customers expect from Hygraph?

Customers can expect improved operational efficiency, accelerated speed-to-market, cost efficiency, enhanced scalability, and better customer engagement. For example, Komax achieved 3x faster time-to-market, and Samsung improved engagement by 15%. See case studies.

Can you share specific customer success stories?

Yes. Samsung built a scalable API-first application, Dr. Oetker enhanced digital experience, Komax managed 20,000+ product variations across 40+ markets, AutoWeb increased monetization by 20%, BioCentury accelerated publishing, Voi scaled multilingual content, and HolidayCheck reduced developer bottlenecks. See case studies.

Performance & Ease of Use

How does Hygraph perform for high-traffic content delivery?

Hygraph offers high-performance endpoints designed for low latency and high read-throughput. Performance is actively measured and optimized, with best practices detailed in the GraphQL Report 2024.

What feedback have customers given about Hygraph's ease of use?

Customers praise Hygraph's intuitive UI, ease of setup, and ability for non-technical users to manage content independently. Real-time changes and custom app integration enhance the experience. Some users note complexity for less technical users. See customer feedback.

Pain Points & Solutions

What operational pain points does Hygraph solve?

Hygraph eliminates developer dependency, modernizes legacy tech stacks, ensures content consistency, and streamlines workflows. HolidayCheck reduced bottlenecks, and Dr. Oetker achieved global consistency. See HolidayCheck case study.

How does Hygraph address financial challenges?

Hygraph reduces operational and maintenance costs, accelerates speed-to-market, and supports cost-effective integrations. Komax achieved faster launches and lower costs, and Samsung scaled globally while reducing overhead. See Komax case study.

What technical pain points does Hygraph solve?

Hygraph simplifies schema evolution, integrates third-party systems, optimizes performance, and enhances localization and asset management. Voi scaled multilingual content, and Hygraph's Smart Edge Cache improves delivery speed. See Voi case study.

Competition & Market Differentiation

How does Hygraph differentiate itself from other CMS platforms?

Hygraph is the first GraphQL-native Headless CMS, offering content federation, user-friendly tools, enterprise-grade features, and proven ROI. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and is voted easiest to implement. See G2 report.

Why choose Hygraph over alternatives like WordPress, Sanity, Prismic, or Contentful?

Hygraph stands out with its GraphQL-native architecture, content federation, cost efficiency, accelerated speed-to-market, robust APIs, Smart Edge Cache, and localization capabilities. Its focus on flexibility and scalability makes it ideal for modern digital experiences. See case studies for proof.

Customer Proof & Recognition

Who are some of Hygraph's notable customers?

Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Vision Healthcare, HolidayCheck, and Voi. See case studies for details and logos.

What market recognition has Hygraph received?

Hygraph ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and has been voted the easiest to implement headless CMS four times. See G2 report for more.

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Help teams manage content creation and approval in a clear and structured way
Hygraph
Docs

#Variants

Today, users expect personalized content tailored to their preferences. Generic content is less effective because users prefer relevant content that appeals to them. With the introduction of Variants, Hygraph empowers content teams to deliver tailored content experiences that resonate with specific user Segments. This level of personalization not only enhances user engagement but also drives conversion rates.

#Key terms

Segments - A named reference used to target a group of users based on shared characteristics or behaviors. The actual user lists for these groups are defined and managed in an external system. You use Segments to deliver specific content, that is, Variants to these external user groups. Examples of shared characteristics for segmentation are:

  • Demographics: Age, gender, location, language
  • Behavioral data: Pages visited, products viewed, time on site
  • Engagement: Frequency of visits, previous purchases, email interactions

Variants - Personalized versions of content entries that are served depending on the defined Segment. Variants define what version of the content a Segment sees.

A main content entry can have many Variants, each tailored to a specific Segment. These Variants are not separate entries but linked to the main entry. They inherit structure or layout from the main entry while allowing customization of certain fields.

#Benefits

With Variants, you can create different pieces of content for different audiences. Here are a few benefits of Variants:

  • Enables personalization and A/B testing use cases
  • Provides support for targeted content without duplicating entries
  • Helps manage multi-regional or multi-brand strategies efficiently

#Use cases

Hygraph doesn’t decide which content Variant is shown to your end-users, and we don’t collect or process any end-user data to drive Segment creation. While it is possible to build personalized experiences without an additional tool, we recommend using a personalization engine for more complex setups.

Here are a few use cases that Variants support:

  • Show different homepage banners to users in Germany vs. the US.
  • Highlight specific content to users based on their browsing history, or the platform they come from.
  • Display metric units for Europe and imperial units for the US on a product page.
  • Present different introductions or visuals depending on whether the reader is a developer or a marketer.

#Get started

Prerequisites

  • You have already set up a content model.
  • You have created at least one content entry based on the content model.

Permissions

Variants inherit permissions from their content model. So if a user can read, create, and update a model, they have the same permissions for Variants of entries based on the model.

Limits

Steps

  1. Enable Variant support for fields.
  2. (Optional) Modify your Segment system model.
  3. Add Segments.
  4. Add Variants for the main entry and link the Variant to one or more Segments.

#Enable Variant support for fields

First, you need to enable Variant support on a per-field basis in your schema.

  1. Go to the Schema Editor, and choose your content model.
  2. On the Fields tab, click Edit field for the field that you want to add Variants.
    • Currently, Variants are not supported for custom fields. Our team is working on adding this functionality to the feature, and we’ll share new additions in future updates.
  3. Under Settings, select the Enable variants check box.
    • You cannot enable Variant support for unique fields.
  4. Click Update.

Repeat these steps for as many fields in the schema, as required.

If you disable Variant support for a field or delete a field that has Variant support enabled, the field and its associated content is removed from all Variants.

#(Optional) Modify your Segment system model

The Segment system model includes certain fields, by default. You can add more fields to the Segment model from the Field Types sidebar. Currently, Variants are not supported for custom fields. You cannot localize the fields of the Segment model.

#Add a Segment

Next, add Segments to display content from different Variants.

  1. In the Content Editor, under Variants, go to Segments.
  2. Select Add entry.
  3. Provide the name of the Segment and optionally, add a description.
  4. Click Save or Save & publish.

Repeat the above steps to add multiple Segments.

  1. Go to the Content Editor, and open your content entry. This is the main content entry.
  2. In the right sidebar, under Variants, select Add. A new version of the content entry is displayed. The values from the main entry for the default locale are copied into the Variant entry. This makes it easier to make adjustments, especially when the Variant only differs slightly from the main entry.
    • To add a new locale to the Variant, in the right sidebar, under Localizations, click the + icon next to the locale. The empty localized fields appear and you can enter the localized text for the Variant in these fields.
  3. Only the fields that have Variant support enabled are available for editing. Make changes to the available fields, as required.
    • Turn on the Show all fields toggle to view the rest of the fields in the content model in read-only mode. If you want to edit the read-only fields, you need to go back to the content entry.
  4. Now, click Select segment.
  5. Choose one or more Segments that this Variant applies, and click Add selected entries.
  6. Click Save or Save & publish.

#Modify a Variant

After you save a Variant, you can modify the values in different fields of the Variant. You can also modify the Segments that you linked to this Variant.

  • Link more Segments - Select the Segment that you added, and click Add segment.
  • Unlink a Segment - Hover over the context menu next to a Segment, and click Remove.

#Behavior of Variant fields

Each variant maintains its own values independently. If the same content is needed across entries, you need to manually update it in each entry. When working with variant fields, note the following points:

  • Main entry updates: Updating a variant-enabled field in the main entry does not update the same field in its variants.
  • Variant Entry updates: Changes made to variant fields do not affect the corresponding fields in the main entry.

Publishing the main entry doesn’t auto-publish its variants. You need to publish each variant separately. To be able to publish a variant, you must have already published the main entry.

#Next steps

Use Hygraph's Variants to achieve personalization in your setup, whether you are just starting out or already have a personalization engine or a Customer Data Platform (CDP) in your setup.

You need to identify user Segments in real time, and then dynamically deliver content based on the Variants that you set up in Hygraph.