Custom Klaviyo Metrics from Shopify: Building View-to-Cart and Category Affinity Signals

Beyond the Out-of-the-Box Events

Klaviyo's Shopify integration gives you Viewed Product, Added to Cart, Started Checkout, Placed Order out of the box. Most brands build their segmentation on these 4 events. But the really powerful segmentation comes from DERIVED metrics — calculations built on top of the raw events that capture subscriber intent more precisely.

Examples of derived metrics:

• View-to-cart conversion rate (personal)
• Category affinity score (% of views in a given category)
• Price sensitivity index (% of browsing on sale items)
• Days since last category visit
• Cross-category explorer (viewed 3+ categories in last 30 days)

The Three Types of Custom Metrics

1. Calculated profile properties

Scheduled calculations stored on the Klaviyo profile. Updated daily. Example: "Average order value over last 90 days" as a stored property. Used in segmentation.

2. Custom events

Events you define and fire via Klaviyo's API when specific Shopify behaviors happen. Example: "Viewed Sale Item" triggers when a customer views any product with a compare_at_price greater than price.

3. Custom metrics (derived dashboards)

Aggregate views that surface patterns across your list. Example: a metric that shows the distribution of view-to-cart conversion rate across subscribers, segmented by acquisition source.

Setup Path for Custom Events

The cleanest setup uses Shopify's Flow app (free) or a dedicated tool like Alloy or Zapier:

1. Shopify Flow triggers on customer or order events (Cart Contains, Product Viewed, etc.)
2. Flow calls Klaviyo's Track API with custom event payload
3. Klaviyo receives the event and attaches it to the profile
4. Event becomes available in segmentation, flow triggers, and dashboards

Five High-Value Custom Events Every Brand Should Build

1. "Viewed Sale Item"

Fires when customer views a product with an active sale price. Creates segment of price-sensitive browsers.

2. "Viewed Premium Item"

Inverse: fires on views of products above average price. Creates premium-intent segment for targeting.

3. "Viewed Out-of-Stock"

Fires when customer views a product that's out of stock. Trigger a back-in-stock flow immediately.

4. "Browsed Category X"

Fires on views within a specific collection. Build category-affinity segments.

5. "High-Intent Browser"

Fires when customer views 3+ products in one session without adding to cart. Different flow than simple abandoned cart — they haven't even added yet.

Segmentation Examples

With custom metrics, you can build segments like:

• "Viewed premium skincare 3+ times but has only purchased from sale" — perfect for a premium-product education flow
• "Category affinity skincare > 70% AND no purchase in 60 days" — targeted re-engagement with skincare-focused content
• "Viewed sale items > 5 times in last 14 days" — flash-sale responsive audience
• "Browsed men's category but shipping address is female name" — gift-giving intent

These segments vastly outperform the generic "engaged last 30 days" segment most brands use.

Calculated Profile Properties

For ongoing metrics, use Klaviyo's Profile Property API. Examples:

• AOV over last 90 days: tells you if a customer is trending up or down in spend
• Days since last purchase: triggers for win-back timing
• Primary category: which product category they spend most on
• Preferred discount band: if they only buy at 20%+ off, price them accordingly

These require daily recalculation via a script, Zapier, or dedicated analytics tool.

Dashboard Metrics

In Klaviyo's Analytics, build custom metrics for:

• View-to-cart conversion rate by traffic source
• Revenue per email recipient by flow vs campaign
• Cohort retention curves
• Predictive CLV by acquisition month

These often need external BI tools (Looker, Metabase, or Shopify's native reports) layered on top of Klaviyo data.

The Build-or-Buy Decision

Under $2M DTC: custom events via Shopify Flow are enough. Free and capable.

$2M-10M: Add a tool like Alloy to make custom event workflows easier. Or use Klaviyo's API directly with a developer's help.

Over $10M: Build a dedicated data warehouse (Snowflake, BigQuery) feeding Klaviyo via reverse-ETL. Complete flexibility.

Common Mistakes