> ## Documentation Index
> Fetch the complete documentation index at: https://loops.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Recipe: Product updates

> Our updated, definitive guide for sending product updates.

## Introduction

A product update should be sent once a month with updates about what you shipped recently. This typically includes new features, improvements, and bug fixes.

Things to keep in mind:

* Brevity is key. Users don't want to read a novel.
* If you send valuable content, users will come to expect (and open) it.
* It's okay to send multiple emails in a month if that's your shipping cadence.

> [card] [Email best practices](https://loops.so/docs/guides/open-rates.md)
>
> Learn more tips for crafting effective emails and improving open rates.

## How to craft a product update email:

![Example of a product update email sent from Loops](https://mintcdn.com/loops/W7EWSDUW0GR-XWrp/images/product-updates.png?fit=max\&auto=format\&n=W7EWSDUW0GR-XWrp\&q=85\&s=ccb380f8c5efe02b058a39adda101efc)

Example of a product update email sent from Loops

1. [Create a new email Campaign](https://loops.so/docs/creating-emails/editor.md)
2. Add your logo at the top of the email, [save it as a component](https://loops.so/docs/creating-emails/components.md) if you haven't already.
3. Add a simple subject line, like "The latest updates from Loops"
4. Add a simple intro paragraph, with a link to the full changelog, potentially socials and a highlight of the most important changes along with a call to action to read the full email.
5. Try to limit the number of updates to 2-3, and make sure they are relevant to the content. It's better to have one or two impactful, relevant updates than a long list of updates that are not relevant to the user.
6. In the footer, add a link to the full changelog, socials, and a link to unsubscribe.
7. [Send the email!](https://loops.so/docs/sending-first-email.md)

> [!WARNING]
>
> Be careful not to overwhelm your users with too many updates. Focus on the
> most impactful changes.

## Choosing your audience

### For new senders

If you're just starting out, send to all users and maintain a steady cadence over time.

### For established senders

If you have an existing list but haven't sent product updates before:

* Send to active users who have engaged with your product in the last 30 days
* Include users who have created an account in the last 30 days
* If the audience size is less than 5,000 users, send to all users

> [card] [Audience segmentation](https://loops.so/docs/contacts/filters-segments.md)
>
> Learn how to create targeted segments for your product updates.

> [card] [Creating emails](https://loops.so/docs/sending-first-email.md)
>
> Learn how to create and send your first email in Loops.

> [card] [Personalizing emails](https://loops.so/docs/creating-emails/personalizing-emails.md)
>
> Add dynamic content to make your product updates more relevant.

> [card] [Email components](https://loops.so/docs/creating-emails/components.md)
>
> Create reusable elements for consistent product update emails.

> [card] [Types of emails](https://loops.so/docs/types-of-emails.md)
>
> Explore different types of emails you can send with Loops.


## Related topics

- [Recipe: Active 30-day users segment](https://loops.so/docs/guides/active-30-day-users.md)
- [Recipe: SaaS customer lifecycle emails](https://loops.so/docs/guides/lifecycle-emails.md)
- [Recipe: Onboarding completion workflow](https://loops.so/docs/guides/onboarding-completion.md)
- [Recipe: Churn risk segment and re-engagement workflow](https://loops.so/docs/guides/churn-risk-segment.md)
- [Create and send your first campaign with the API or an agent](https://loops.so/docs/guides/first-campaign-api.md)