How to Filter Reports by Klaviyo Lists and Segments in Lifetimely

Filtering reports in Lifetimely by Klaviyo lists and segments helps you analyze customer lifetime value (LTV) across your email and SMS audiences. This allows you to identify high-value segments, track performance trends, and make data-driven marketing decisions.

📌 Note: While lists and segments can be used for filtering reports, Campaign and Flow metrics are available in custom dashboards for deeper performance tracking.

Use Case: Identify High-Value Customer Segments🚀

If you're using Klaviyo to run email and SMS campaigns, filtering your reports by Klaviyo segments in Lifetimely helps you:

  • Compare LTV across customer groups (e.g. VIP customers vs. one-time buyers)
  • Understand whether SMS or email marketing leads to stronger retention
  • Identify which segments offer the shortest CAC payback period
  • Optimize marketing spend by focusing on high-performing customer cohorts

These insights help you improve retention, allocate budget efficiently, and refine acquisition strategies.


How to Filter Reports by Klaviyo Segments

Step 1: Open an LTV Report

Go to Lifetimely > Lifetime Value > Cohorts

This report shows lifetime value trends over time.

Step 2: Apply Klaviyo Filters

Click Filter > Marketing

Choose Klaviyo list or segment from the filter type dropdown

Select a specific list or segment to apply

Step 3: Analyze the Results

  • Review LTV trends by Klaviyo segment
  • Compare first-touch vs. last-touch attribution
  • Add other filters like source or medium for deeper analysis

Outcome

By filtering reports with Klaviyo data, you’ll gain deeper insights into customer behavior and better understand which segments drive value over time.


Next Steps

  • Identify high-value customer segments for targeted marketing.
  • Adjust ad spend and email/SMS strategies based on LTV insights.
  • Use Campaign and Flow metrics in custom dashboards for a deeper understanding of marketing performance.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.