Skip to main content

Recharge Subscription Frequency Changed Personalization Guide

The Recharge Subscription Frequency Changed event triggers a Listrak Custom Event when a customer updates the frequency of their subscription order. In the journey, you can message a customer to confirm their subscription changes, display their billing details, and display the items included in the subscription.

This guide will outline the personalization options to customize the journey and messages triggered by the Recharge integration.


Personalizing the Journey with Custom Event Properties

The Custom Event called Recharge Subscription Frequency Changed [[Your Store Name]] is automatically created as part of the integration process. Recharge passes the following payload to Listrak customized with the specific product information for the subscription.

{
"eventCategory": "subscription",
"eventType": "SubscriptionFrequencyChanged",
"eventTimestamp": "2026-04-30T10:40:00.0000000+00:00",
"customer": {
"email": "[email protected]",
"firstName": "Jane",
"lastName": "Smith",
"externalCustomerId": "24662915678374",
"billingCity": "Philadelphia",
"billingProvince": "Pennsylvania"
},
"subscription": {
"id": "784594001",
"status": "active",
"createdAt": "2026-03-01T10:00:00+00:00",
"updatedAt": "2026-04-30T10:40:00+00:00",
"cancelledAt": null,
"cancellationReason": null,
"orderIntervalUnit": "month",
"orderIntervalFrequency": 2,
"nextChargeScheduledAt": "2026-06-30",
"previousFrequency": "1 month",
"newFrequency": "2 month"
},
"product": {
"title": "Classic Cotton T-Shirt",
"price": "18.74",
"quantity": 1,
"productId": "15268877402278",
"variantId": "56305470505126",
"sku": "T100",
"imageUrl": "https://cdn.example.com/tshirt.jpg",
"linkUrl": "https://store.example.com/products/classic-cotton-t-shirt",
"productHandle": "classic-cotton-t-shirt"
}
}

The JSON is saved to a Custom Event field and used to personalize the message. The table below outlines all fields created in Custom Event. Fields other than the JSON can be used as criteria in a Custom Event Decision Split, allowing customers to receive different messages or different logic based on the values of these fields.

Property Name

Data Type

CustomJson

String

product_title

String

customer_billing_city

String

customer_billing_province

String

Personalizing the Message with Recharge Data

You can customize any message(s) in the journey based on the data passed in the JSON. The table below outlines the fields you can include in a message to display the data about a customer's updated subscription. The field values will match what is included in the payload mentioned in the previous section.

Object

Fields Used

customer

firstName, lastName, email, billingCity, billingProvince

subscription

id, status, orderIntervalFrequency, orderIntervalUnit, nextChargeScheduledAt, previousFrequency, newFrequency

product

title, price, quantity, sku, imageUrl

💡 previousFrequency and newFrequency are formatted as "1 month", "2 week", etc.

You have the option to create a fully coded HTML email from scratch or to edit the template that includes the basic design elements listed below.

If you code a message yourself, you can add any or all of fields from the table above. To display the personalized data, you will use the format {{object.fieldname}}. For example, to display the customer's first name uses the following tag. {{customer.firstName}}.

Example Template

You can also use the example template as a starting point.

[[HB BlockType="Custom" Source="Custom.customJson"]]
<div class="email-wrapper">
<div class="email-container">
<div class="email-header"><div class="brand">Your<span>Store</span></div></div>
<div class="email-hero">
<h1>Your delivery frequency has been updated 📅</h1>
<p>{{customer.firstName}}, your subscription schedule has changed. Here's what's new.</p>
</div>
<div class="email-body">
<p class="greeting">Hi <strong>{{customer.firstName}} {{customer.lastName}}</strong>,<br/><br/>We've updated the delivery frequency on your subscription. Your next order will follow the new schedule shown below.</p>
<p class="section-label">Frequency Change Summary</p>
<div style="background:#f8fafc;border:1px solid #e2e8f0;border-radius:8px;padding:20px 24px;margin:0 0 28px;">
<div style="display:flex;align-items:center;gap:12px;">
<div>
<div style="font-size:11px;font-weight:700;text-transform:uppercase;color:#64748b;margin:0 0 4px;">Previous Frequency</div>
<div style="font-size:16px;font-weight:700;color:#1a2b4a;">Every {{subscription.previousFrequency}}</div>
</div>
<div style="font-size:22px;color:#00bfa5;padding:0 8px;">→</div>
<div>
<div style="font-size:11px;font-weight:700;text-transform:uppercase;color:#64748b;margin:0 0 4px;">New Frequency</div>
<div style="font-size:16px;font-weight:700;color:#1a2b4a;">Every {{subscription.newFrequency}}</div>
</div>
</div>
</div>
<div class="product-card">
<img src="{{product.imageUrl}}" alt="{{product.title}}" />
<div class="product-info">
<p class="product-label">Your Subscription Item</p>
<h2>{{product.title}}</h2>
<div class="product-meta">
<div class="meta-item">Price<strong>${{product.price}}</strong></div>
<div class="meta-item">Quantity<strong>{{product.quantity}}</strong></div>
<div class="meta-item">SKU<strong>{{product.sku}}</strong></div>
</div>
</div>
</div>
<table class="detail-table">
<tr><td class="label">Status</td><td class="value"><span class="badge">{{subscription.status}}</span></td></tr>
<tr><td class="label">New Frequency</td><td class="value">Every {{subscription.orderIntervalFrequency}} {{subscription.orderIntervalUnit}}(s)</td></tr>
<tr><td class="label">Next Charge Date</td><td class="value">{{subscription.nextChargeScheduledAt}}</td></tr>
<tr><td class="label">Subscription ID</td><td class="value">{{subscription.id}}</td></tr>
</table>
<div class="cta-wrap"><a href="#" class="cta-btn">Manage My Subscription</a></div>
</div>
<div class="email-footer">
<p class="footer-brand">YourStore</p>
<p>This email was sent to {{customer.email}}</p>
<p>{{customer.billingCity}}, {{customer.billingProvince}}</p>
</div>
</div>
</div>
[[/HB]]

Did this answer your question?