Klaviyo Integration: Loyalty & List Management

Modified on Tue, 18 Feb at 11:23 AM

Overview

The SiteVibes-Klaviyo integration enables real-time synchronization of customer loyalty data, automated list management, and points expiration notifications. This documentation covers the core features and setup process.

Setup Requirements

  • Active Klaviyo account with API access

  • Klaviyo API key

  • SiteVibes admin access


Integration Setup

1. Klaviyo Credentials

  1. Navigate to Settings → Integrations in your SiteVibes dashboard

  2. Locate the "Klaviyo Integration Credentials" section

  3. Enter your Klaviyo API key

  4. Click "Update Credentials" to save

2. Configure Integration Settings

Loyalty Points Sync Options

  • Daily Updates: Points are synced once per day

  • Real-time Updates: Points are synced immediately when changes occur

  • Enable Points Expiring Event: Activates expiration notifications

To configure these settings:

  1. Go to "Klaviyo Integration Settings"

  2. Select your preferred sync option

  3. Toggle "Enable Points Expiring Event" if desired

  4. Click "Update settings" to save changes

3. Email List Configuration

Automatic List Management

The integration supports several specialized email lists in Klaviyo:

  • Loyalty List: Members of your loyalty program

  • Referral List: Customers who have participated in referrals

  • General Q&A List: Customers engaging with Q&A features

  • Product Reviews List: Automatically includes users who submit 5-star reviews

For each list type:

  1. Click "Create new List" if you need a new list

  2. Or select an existing list from your Klaviyo account

  3. Click "Update" to save the mapping

Subscription Status

  • All users added to lists are automatically set as subscribed members

  • Subscription status is maintained across list updates

  • Opt-out preferences are respected

4. Setting Up Klaviyo Metrics

Creating Points Expiration Metrics

  1. Navigate to Metrics in Klaviyo

  2. Click "Create metric"

  3. Configure the following settings:

    • Name: Enter a descriptive name for your points expiration metric

    • Aggregation Method: Select "Value"

    • Metric Name: Choose "SiteVibes Points Expiring"

    • Metric Value Property: Select "sv_loyalty_number_of_points_expiring"

Additional filters can be added to refine the metric using the "Add filter" button. Up to 3 filters can be applied per metric, and you can combine up to 5 metrics.

5. Setting Up Klaviyo Flows

Available Triggers

The integration provides several trigger events in Klaviyo:

  1. Active on Site: Triggers when a customer is actively browsing your site

  2. SiteVibes Points Expiring: Triggers when a customer's loyalty points are approaching expiration

  3. Viewed Product: Triggers when a customer views a product

Points Expiration Flow

To create an expiration notification flow:

  1. In Klaviyo:

    • Create a new flow

    • Select "SiteVibes Points Expiring" as the trigger event

    • Design your email template

  2. Recommended Timeline:

    • First notice: 30 days before expiration

    • Reminder: 14 days before expiration

    • Final notice: 3 days before expiration


Troubleshooting

Common Issues

  1. Points Not Syncing

    • Verify API key is correct

    • Check sync settings are enabled

    • Confirm customer email addresses match between systems

  2. Missing Expiration Notifications

    • Ensure "Enable Points Expiring Event" is toggled on

    • Verify Klaviyo flow is properly configured

    • Check email templates are active

  3. List Management Issues

    • Verify list IDs are correct

    • Check for duplicate email addresses

    • Confirm API permissions

Support

For additional assistance:

  • Contact SiteVibes support

  • Reference Klaviyo's API documentation

  • Check the integration status in your dashboard








Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article