# Veeva Approved Email (VAE) — platform conventions

Structural vocabulary for the Email Drafter (Skill 4) when a template's **Target platform** is Veeva Approved Email. This explains *how VAE is built* so the drafter works within it. The brand-specific specifics — the actual approved fragments, tokens, limits and mandatory wording — live in `<Brand> Email Templates.docx`; this file is the general model, not a substitute for that.

## How a Veeva Approved Email is built

- The **template** is a locked, MLR-approved HTML document. End users (reps) **cannot edit the template** — approved content stays unchanged when the email is sent. Templates are UTF-8.
- The body is assembled from **Email Fragments**: pre-approved snippets of HTML, each carrying one message plus optional approved links. Fragments insert at the **`{{insertEmailFragments}}`** token in the template, which sits inside a `<table>`; each fragment is therefore a `<tr>`. Reps **select and order** the fragments; they display in the order arranged.
- **Tokens** add content or links and are placed inside `<a href="…">` tags. A Vault PromoMats document is linked with `<a href="{{$Vault Document ID}}">link text</a>`. Other behaviours (unsubscribe, sender, personalisation) come from **configuration tokens** defined in the brand's Veeva setup.

## What this means for drafting

- **Compose only from the brand's approved fragment set.** The drafter selects and sequences approved fragments and writes within them. It must **not invent fragments, token syntax, or wording**, and must not restructure the locked template.
- **Mandatory blocks are fixed** — ISI / fair balance, sender/sponsor, and unsubscribe are approved content (often their own fragments or config tokens). Reproduce them verbatim; never paraphrase.
- **Respect fragment limits** and the subject-line limit.
- If a needed message has no approved fragment, that is a **library/fragment gap** — surface it, don't fabricate a fragment.

## Capture these in `<Brand> Email Templates.docx` (VAE template)

- The **approved Email Fragment library**: each fragment's name, the message/claim it carries, its approved link(s), and any character limit.
- The **subject-line** limit (and how many options).
- The **mandatory blocks** verbatim (ISI/fair balance, sender), and the **unsubscribe** config token the approved template uses.
- The **footer** (often baked into the locked template).
- Image handling: which fragments carry images, referenced via Vault document tokens rather than embedded.

Take these from the brand's **real, approved Veeva exports/config** — exact token strings and fragment rules are version- and brand-specific and must not be guessed.

---

*Researched 2026-05-27 from Veeva CRM / Vault CRM Help. Veeva updates its platform regularly (CRM → Vault CRM migration ongoing), so verify token names and fragment rules against the brand's current Veeva configuration before relying on them.*

Sources:
- [Components of Approved Email — Veeva CRM Help](https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/InitialConfig/Components.htm)
- [Creating Approved Email Templates — Veeva CRM Help](https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/ManageCreateContent/CreatingContent/CreatingAETemplates.htm)
- [Creating Approved Email Fragments — Veeva CRM Help](https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/ManageCreateContent/CreatingContent/CreatingAEFragments.htm)
- [Approved Email Configuration Tokens — Veeva CRM Help](https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ApprovedEmail/ManageCreateContent/CreatingContent/ConfigTokens.htm)