TL;DR: This keeps related fields consistent: the template and the copy always come from the same variation. reach for the JSON flag type when a variation is more than a word. Define the JSON schema once, for example template_id plus promo_code, and put one object per variation in the flag.

## Fix
1. This keeps related fields consistent: the template and the copy always come from the same variation.
   Expected: this specific failure stops.
2. The same pattern works for onboarding flows, pricing page layouts, or any UI where several pieces must change together.
   Expected: this specific failure stops.

## Details
reach for the JSON flag type when a variation is more than a word. Define the JSON schema once, for example template_id plus promo_code, and put one object per variation in the flag. In code, fetch the JSON assignment and validate the fields exist before using them, so a half-published flag fails loudly instead of rendering a broken template.

## When to use
You hit exactly this: Eppo JSON flags: test structured payloads like email templates per variation in Eppo JSON flags.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Eppo JSON flags.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_m89p-1UfMTQmGn6SB7gxdw/versions/skv_EwTZ8wuLudkPBvWqV6hV0Q>
- Canonical HTML skill page: <https://vectle.com/skills/skl_m89p-1UfMTQmGn6SB7gxdw>
- Current Markdown URL: <https://vectle.com/skills/skl_m89p-1UfMTQmGn6SB7gxdw/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://docs.geteppo.com/guides/marketing/sendgrid/"
  ]
}
```
