Klaviyo + Go Fig

Marketing

Integrate Klaviyo with Go Fig for advanced email and SMS marketing analytics.

Klaviyo is the dominant email and SMS automation system for DTC and ecommerce brands, with heavy integration into Shopify and first-party predictive metrics (predicted LTV, churn risk, next-purchase probability) that finance teams would love to believe but rarely validate. Go Fig connects via the Klaviyo API v2024, lands profiles, lists, segments, flows, campaigns, event metrics, catalog items, and Klaviyo's predictive scores in your Financial Intelligence Graph, and joins on email or phone number to orders in Shopify and invoices in Stripe or your accounting system. Celeste and your AI financial analysts can then produce flow-level revenue attribution using real orders (not Klaviyo's attributed number), contribution margin by SMS campaign net of send cost, and cohort LTV segmented by Klaviyo list or tag. Klaviyo's predictive LTV is also reconciled to realized LTV so finance can tell when the model is off and by how much.

Connect Klaviyo See All Integrations

Key facts

API: Klaviyo API v2024
Grain: Profile, flow, campaign, message, metric event
Predictive scores: Predicted LTV, churn risk, next-purchase probability
Sync cadence: Hourly incremental
Multi-account: Multiple Klaviyo accounts in one tenant

SOC 2 Type II · All integrations

What you can do with Klaviyo data in Go Fig

Flow revenue and SMS economics

Attribute realized revenue to each Klaviyo flow and SMS campaign, net of send cost, so finance can rank automations by true contribution margin rather than Klaviyo's default attribution.

Cohort LTV by list and tag

Segment customer cohorts by Klaviyo list or tag and calculate LTV, gross margin, and payback using realized order data from Shopify or Stripe.

Predictive LTV reconciliation

Compare Klaviyo's predicted LTV and churn risk against realized outcomes so finance can validate (or caveat) the predictions that drive the merchandising and retention roadmap.

Data available from Klaviyo

Go Fig extracts and normalizes the following data from your Klaviyo account:

Profiles and custom profile properties

Lists and segments

Campaigns (email and SMS)

Flows and flow messages

Metric events (placed order, viewed product, etc.)

Revenue data at message level

SMS send and delivery metrics

Predicted LTV and churn risk

Predicted next order date

Catalog items and categories

Forms and pop-ups

Coupon and promo codes

How to connect Klaviyo

Generate a private API key in Klaviyo

In Klaviyo, open Settings, API Keys, and create a Private Key scoped to the read permissions Go Fig requests (profiles, events, metrics, campaigns, flows, catalogs). Paste the key into Go Fig. For multi-store brands running separate Klaviyo accounts per region or brand, repeat per account.

Select metric events and attribution window

Klaviyo tracks a long tail of metric events (placed order, viewed product, started checkout). Pick the events finance cares about and the attribution window Klaviyo should apply (5-day click is the Klaviyo default). Go Fig stores raw events so Celeste can regenerate attribution under alternative windows if needed.

Configure profile identity resolution

Profiles in Klaviyo are keyed by email, with phone number as a secondary identifier. Go Fig matches profile email to customer email in Shopify, Stripe, and your accounting system for closed-loop attribution. Where a profile has multiple emails over time, identity history is preserved.

Join to Shopify and accounting for closed-loop LTV

If Shopify and your accounting connector are live, Go Fig ties Klaviyo flow and campaign sends to realized orders and recognized revenue. The Klaviyo starter dashboard populates on first sync with flow revenue, SMS economics, cohort LTV, and a predictive-LTV reconciliation.

Authentication: Private API key scoped per account in Klaviyo admin under Settings, API Keys. Go Fig uses scoped read access (profiles:read, events:read, metrics:read, campaigns:read, flows:read, catalogs:read). The key is stored encrypted and never exposed to end users.

Common Questions About Klaviyo Integration

How does Go Fig handle Klaviyo's attributed revenue versus real revenue?

Klaviyo reports attributed revenue based on a 5-day click and 1-day open window by default, which typically over-reports revenue compared to a finance-grade view. Go Fig pulls both the Klaviyo-attributed number and the realized order revenue from Shopify or Stripe, joined on email and phone number, and surfaces the variance. Most brands see Klaviyo attribution running 10 to 30 percent higher than realized last-click revenue, and Go Fig quantifies the gap.

Can Go Fig attribute SMS campaigns to margin, not just revenue?

Yes. SMS send costs (per-message fees from Klaviyo's SMS credits) are pulled alongside the revenue Klaviyo attributes to each send. Joined to Shopify order data plus product-level COGS (if available in the accounting system), Celeste produces contribution margin per SMS campaign so finance can see when an SMS flow is discounting away its own profit.

How are Klaviyo's predictive scores validated against reality?

Klaviyo ships predicted LTV, predicted next-order date, and churn risk scores at the profile level. Go Fig stores those predictions at the time they were generated and compares them against realized outcomes later. The resulting calibration curve tells you whether Klaviyo's model is well-calibrated for your brand or whether it systematically over- or under-predicts, which matters if the retention team is making merchandising and budget decisions from it.

Does Go Fig support multiple Klaviyo accounts?

Yes. Multi-brand and multi-region DTC companies often run separate Klaviyo accounts per brand or per geography. Each account connects with its own private API key and Go Fig preserves the account ID as a column so campaigns, flows, and revenue roll up cleanly by brand, region, or globally.

What is the historical backfill limit for Klaviyo?

The Klaviyo API exposes full account history for profiles, lists, campaigns, flows, and catalog. Metric event history is effectively unlimited on paid plans, though paginating through very large event streams can take several hours on initial sync. Go Fig stores everything permanently after the first backfill, so subsequent year-over-year comparisons are always available.