> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/loyalty-and-rewards/loyalty-klaviyo-integration/monthly-loyalty-updates.md).

# Monthly loyalty updates

Send a scheduled monthly loyalty digest with the Roadmap: Loyalty Monthly Update metric — enable it, set the time, and pair it with profile properties.

A monthly digest keeps the program salient for members who haven't shopped recently — a **retention lever** that works by simply reminding customers the balance exists. Unlike every other loyalty metric, this one fires on a schedule you control, not on customer behaviour.

### Klaviyo event name

* `Roadmap: Loyalty Monthly Update` — your scheduled monthly digest event.

It's **off by default**. In Roadmap's Klaviyo settings: tick **Enabled**, use **Set Time** to choose when it fires each month, and **Send Now** to fire a test immediately.

### Event properties

| Data point   | Event property               |
| ------------ | ---------------------------- |
| Update month | `update_month` (e.g. *July*) |
| Update year  | `update_year`                |
| Customer ID  | `customer_id`                |

The event is deliberately thin — the content comes from [profile properties](/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-profile-properties-and-email-snippets.md), which are always current at send time.

### Recommended flow structure

1. **Trigger:** `Roadmap: Loyalty Monthly Update`
2. **Email — immediately:** "Your {{ event.update\_month }} loyalty summary"

Build the body entirely from profile lookups:

```liquid
Balance: {{ person.roadmap_loyalty_total_points|default:'0' }} points
Tier: {{ person.roadmap_loyalty_current_tier_name|default:'—' }}
Next tier: {{ person.roadmap_loyalty_next_tier_points|default:'' }} points to {{ person.roadmap_loyalty_next_tier_name|default:'' }}
Expiring soon: {{ person.roadmap_loyalty_expiring_points|default:'0' }} points in the next 30 days
```

### Strategy

* **One email, four numbers.** Balance, tier, next goal, expiring — that's the whole digest; resist making it a newsletter.
* **Suppress zero-value sends.** Add a flow filter (e.g. `roadmap_loyalty_total_points` greater than 0) so point-less profiles don't get an empty summary.
* The expiring-points line quietly feeds the [points expiring](/loyalty-and-rewards/loyalty-klaviyo-integration/points-expiring-reminders.md) urgency play all year round.

### Related guides

* [Loyalty × Klaviyo: overview](/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-klaviyo-overview.md)
* [Loyalty profile properties and email snippets](/loyalty-and-rewards/loyalty-klaviyo-integration/loyalty-profile-properties-and-email-snippets.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.roadmap.so/loyalty-and-rewards/loyalty-klaviyo-integration/monthly-loyalty-updates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.