You've been able to use subscriber metadata in your emails for a while now — things like {{ subscriber.metadata.first_name }} to personalize greetings, or {{ subscriber.metadata.company }} to tailor content per reader. That's great for per-subscriber personalization, but what about values that are the same across your entire newsletter?

Now you can use {{ newsletter.metadata }} in your email templates. It works exactly the same way: set key-value pairs on your newsletter, then reference them in any email, automation, or template.

How it works

Head to the API and set metadata on your newsletter:

PATCH /v1/newsletters
{
  "metadata": {
    "podcast_url": "https://pod.example.com",
    "current_sponsor": "Acme Corp",
    "issue_season": "Spring 2026"
  }
}

Then use those values anywhere you write email content:

This issue is brought to you by {{ newsletter.metadata.current_sponsor }}.

Listen to our latest episode: {{ newsletter.metadata.podcast_url }}

A few ideas

• Sponsorship info: Store your current sponsor's name and URL in newsletter metadata, then reference it in your footer template. When the sponsor changes, update the metadata once instead of editing every template.
• Seasonal or rotating content: Keep a current_theme or issue_season value that you swap out periodically, and reference it in your subject lines or headers.
• Global links: Store URLs that appear across many emails — your podcast, your community forum, your latest lead magnet — so you can update them in one place.

The key difference from subscriber metadata is scope: subscriber metadata varies per reader, newsletter metadata is the same for everyone. Think of it as global variables for your newsletter.