memberr sends five store credit events to Klaviyo: added, available, deducted, will expire, expired. Each event has properties (amount, balance, expiry date). Each is a trigger for a flow.
This article covers setup, the four must-have flows, and merge fields for personalization.
Setup: Connect memberr to Klaviyo
memberr app > Integrations > Klaviyo > Connect
Once connected, memberr syncs:
- Customer properties (balance, upcoming balance, currency, referral link)
- Events (credit added, available, deducted, will/did expire)
Properties update continuously. Events fire when actions occur.
Docs: memberr Klaviyo Integration
Events and Properties
Events
| Event | Trigger |
|---|---|
Store Credit added | Credit issued to account |
Store Credit available | Delayed credit becomes usable |
Store Credit deducted | Credit used at checkout |
Store Credit will expire | 7/3/1 days before expiry |
Store Credit expired | Credit expired |
Each event includes:
amount(integer, smallest currency unit)amount_formatted(decimal, no symbol)amount_with_symbol(formatted with currency symbol, e.g., "$10.00")source_type(refund, cashback, campaign, etc.)expires_at(if applicable)
Plus all customer properties (balance, membership, etc.).
Docs: Klaviyo Events
Merge Fields (Customer Properties)
| Field | Description | Example |
|---|---|---|
memberr_currency_code | Currency code | "USD" |
memberr_current_balance | Balance (integer, for segmentation) | 1000 |
memberr_upcoming_balance | Pending balance (integer) | 500 |
memberr_current_balance_formatted | Balance (decimal) | "10.00" |
memberr_upcoming_balance_formatted | Pending (decimal) | "5.00" |
memberr_current_balance_with_symbol | Balance + symbol | "$10.00" |
memberr_upcoming_balance_with_symbol | Pending + symbol | "$5.00" |
memberr_ref_link | Referral link | "https://..." |
memberr_birthday | Birthday | "1990-01-01" |
Use raw values (no formatting) for segmentation. Use formatted values (with symbol) for display in emails.
Docs: Klaviyo Merge Fields
Four Must-Have Flows
1. Credit Added - Announcement
Trigger: Store Credit added
Goal: Notify customer immediately when they earn credit.
Timing: Send within 5 minutes of trigger.
Email:
Subject: "You earned $10 store credit"
Body:
Why it works:
Immediate notification = high awareness. Customer knows they have credit and is more likely to return and use it.
2. Credit Available - Delayed Credit Announcement
Trigger: Store Credit available
Goal: Notify when delayed credit becomes usable.
Timing: Send same day as trigger (credit just unlocked).
Email:
Subject: "Your $15 credit is now available"
Body:
Use case:
You issue credit on December 20 but set it to become available January 1. This flow triggers January 1 and reminds them to use the unlocked credit.
3. Credit Will Expire - Reminder
Trigger: Store Credit will expire
Goal: Create urgency before credit expires.
Timing:
memberr sends this event at configurable intervals (7 days, 3 days, 1 day before expiry). Build separate flows for each, or use one flow with conditional logic based on notification_type property.
Recommended: Send at 3 days and 1 day before expiry.
Email (3 days before):
Subject: "Your $10 credit expires in 3 days"
Body:
Email (1 day before):
Subject: "⚠️$10 credit expires tomorrow"
Body:
Why it works:
Urgency drives action. Redemption spikes 24-48 hours before expiry. Without reminders, customers forget and lose credit (bad experience).
4. Credit Deducted - Thank You
Trigger: Store Credit deducted
Goal: Confirm credit was applied, encourage next purchase.
Timing: Send within 24 hours of trigger (post-purchase).
Email:
Subject: "Thanks for using your store credit"
Body:
Why it works:
Confirms the credit worked (customer sees savings). If they have remaining balance, reminds them to return. If balance is $0, reinforces positive experience ("I saved money").
Nice-to-Have Flows
5. Balance Reminder (Monthly)
Trigger: None (scheduled campaign)
Goal: Remind customers with credit to use it.
Timing: Monthly, send to segment where memberr_current_balance > 0.
Email:
Subject: "You have waiting"
Body:
Why it works:
Customers forget they have credit. Monthly reminder increases utilization.
6. Welcome Series with Credit
Trigger: Subscribed to list (or added credit for new customers)
Goal: Introduce program, announce welcome credit.
Timing: Send immediately after subscription.
Email:
Subject: "Welcome! Here's $10 to get started"
Body:
Why it works:
First-time buyers with credit are more likely to convert. Welcome credit removes price friction.
7. Referral Flow
Trigger: None (proactive)
Goal: Encourage referrals by promoting ref link.
Timing: Send to customers with high LTV or recent purchases.
Email:
Subject: "Give $10, get $10"
Body:
Why it works:
Referrals driven by credit rewards are higher-converting than generic "tell a friend" asks. Both parties get value.
Best Practices
1. Use formatted values for display
Always show {{ memberr_current_balance_with_symbol }} in emails (includes currency symbol, properly formatted). Don't use raw integer values.
2. Use raw values for segmentation
Filter segments with memberr_current_balance > 1000 (integer, cents). Don't use formatted fields in conditions.
3. Conditional logic for expiry
4. Personalize with source_type
Adjust messaging based on how credit was earned (cashback, referral, campaign). Use {{ event.source_type }} to conditionally change copy.
5. A/B test subject lines
Test urgency ("Expires in 3 days!") vs. value ("You have $15 credit") vs. curiosity ("Don't lose this...").
6. Mobile-optimize
60% of email opens are mobile. Keep subject lines under 40 characters. Use large CTA buttons.
Store credit flows are event-driven, not time-based. They fire when something happens (credit added, expiring, used). This makes them more relevant than generic campaigns.
Set them up once, and they run automatically. memberr sends the events, Klaviyo sends the emails, customers get notified at the right time.
For campaign strategy, see Store Credit Campaigns. For general communication tactics, see Store Credit Communication.