1. What area of Klaviyo do you need help with?
   • A) Flows — visual automation builder (welcome, abandoned cart, post-purchase, winback, browse abandonment, custom)
   • B) Campaigns — one-time/scheduled broadcasts, A/B testing, Smart Send Time
   • C) Segmentation — real-time behavior-based segments, predictive attributes, custom properties
   • D) Predictive Analytics — predicted CLV, next order date, churn risk, spend tier
   • E) Multi-channel — email, SMS/MMS, WhatsApp, RCS, mobile push notifications
   • F) Forms — pop-ups, fly-outs, embedded forms, multi-step forms for list growth
   • G) Reviews — product review collection, AI-powered responses, display widgets
   • H) Klaviyo Data Platform (KDP) — unified profiles, integrations, event processing
   • I) Advanced KDP — reverse ETL, custom objects, advanced webhooks, warehouse sync
   • J) AI Agents — Marketing Agent (campaign generation), Customer Agent (support automation)
   • K) Catalogs / Coupons — product catalog sync, personalized recommendations, back-in-stock, coupon codes
   • L) Reporting — revenue attribution, campaign/flow analytics, benchmarks, custom dashboards
   • M) Templates — drag-and-drop editor, dynamic blocks, mobile-responsive design
   • N) Customer Hub — self-service portal (order tracking, FAQ, support)
   • O) API / Integrations — REST API, webhooks, Shopify integration, third-party connectors
   • P) Account / Billing — plans, pricing, profile-based billing
   • Q) Something else — describe it
2. What's your role?
   • A) E-commerce operator / store owner
   • B) Email / lifecycle marketer
   • C) Developer / engineer
   • D) Agency / freelancer
   • E) Growth / marketing manager
   • F) Other
3. What are you trying to accomplish? (describe your specific goal or question)

• General email marketing strategy / best practices ->

  /sales-email-marketing

• Cross-platform email deliverability (not Klaviyo-specific) ->

  /sales-deliverability

• Email open/click tracking strategy ->

  /sales-email-tracking

• Connecting Klaviyo to other tools via middleware ->

  /sales-integration

• Checkout optimization (cart/checkout UX) ->

  /sales-checkout

• Customer.io-specific questions ->

  /sales-customerio

• Mailchimp-specific questions ->

  /sales-mailchimp

• What they are: Visual automation workflows triggered by events — purchase, browse, cart abandon, signup, custom events, date properties, price drop, back-in-stock
• Builder: Drag-and-drop canvas with trigger, conditional split, time delay, A/B split, and action nodes
• Cross-channel steps: A single flow can include email, SMS, and push notification steps — orchestrate across channels in one workflow
• Branching logic: Conditional splits based on profile properties, segment membership, event data, or predictive attributes (e.g., high CLV customers get a different path)
• A/B splits: Test different paths within a flow — split traffic by percentage and measure which branch performs better
• Time delays: Wait a fixed duration, until a specific time of day, or until a specific day of the week before the next step
• Pre-built templates: Welcome series, abandoned cart, post-purchase follow-up, winback, browse abandonment, back-in-stock, price drop, review request, birthday/anniversary
• Flow webhooks: POST action step that sends event/profile data to an external URL — use for syncing data to external systems within a flow

• What they are: One-time or scheduled broadcast sends to a list or segment
• A/B testing: Test subject line, content, or send time across variants. Klaviyo auto-selects the winner based on open rate or click rate
• Smart Send Time: Klaviyo analyzes each recipient's historical engagement patterns and sends at the time they are most likely to open — optimized per-recipient, not a single "best" time
• Send strategies: Send immediately, schedule for a specific date/time, or use Smart Send Time
• Segment targeting: Send to dynamic segments that auto-update — the segment is evaluated at send time, so new qualifying profiles are included

• Real-time segments: Segments update automatically as profiles match or stop matching conditions — no manual refresh needed
• Condition types: Behavior (opened email, placed order, viewed product), profile properties (location, custom fields), predictive attributes (CLV tier, churn risk), list membership, engagement metrics
• Nested conditions: Combine AND/OR logic with unlimited nesting depth for complex targeting
• Predictive attributes in segments: Segment by predicted CLV, churn risk, next order date, gender prediction — e.g., "high CLV customers likely to churn in 30 days"
• Use everywhere: Segments can be used as flow triggers, campaign recipients, conditional split conditions, form targeting rules, and reporting filters

• Predicted CLV: Estimated total revenue a customer will generate over their lifetime
• Next order date: When a customer is most likely to place their next order
• Churn risk: Probability that a customer will not purchase again (high/medium/low)
• Average order value: Predicted average spend per order
• Spend tier: Automatic bucketing into high/medium/low spenders
• Gender prediction: Inferred gender based on name and purchase behavior
• Data requirements: Requires sufficient order history — typically 500+ orders and 180+ days of data before predictions appear
• Updates: Predictions refresh regularly as new data flows in

• Email: Full HTML email with drag-and-drop editor, dynamic content blocks, product feeds, personalization tags
• SMS/MMS: Text and multimedia messages, short links, opt-in/opt-out management, quiet hours, carrier compliance
• WhatsApp: Business messaging via WhatsApp (select regions), templates, rich media
• RCS for Business: Rich Communication Services messaging with branded sender, carousels, suggested actions
• Mobile push: Push notifications via Klaviyo SDK integration in iOS/Android apps
• Channel orchestration: Use flows to coordinate across channels — e.g., send email first, if not opened after 24h, send SMS

• Types: Pop-ups, fly-outs, embedded forms, full-page forms, multi-step forms
• Targeting rules: Show based on URL, time on page, scroll depth, exit intent, device type, segment membership, UTM parameters
• A/B testing: Test form variants (copy, design, timing, offer) and measure conversion rate
• Multi-step: Collect email first, then ask for SMS consent, preferences, or additional data in subsequent steps
• List growth: Forms automatically add subscribers to lists and trigger flow entries (e.g., welcome series)

• Collection: Automated review request emails/SMS after purchase with customizable timing
• AI-powered responses: Auto-generate responses to reviews using AI
• Display widgets: Embed star ratings, review carousels, and review pages on your storefront
• Integration: Reviews feed into segmentation (e.g., customers who left 5-star reviews) and product recommendations

• Unified profiles: Single customer view aggregating data from 350+ integrations, website tracking, email/SMS engagement, purchase history, and custom events
• Event processing: Ingests 2.5B events per day in real-time
• Native integrations: 350+ pre-built connectors including Shopify (deep native), BigCommerce, WooCommerce, Adobe Commerce, Salesforce Commerce Cloud, Salesforce CRM, Meta, TikTok, Google Ads, Zapier, Stripe, ReCharge, Yotpo, Gorgias, Zendesk
• Custom properties: Add any custom data to profiles via API or integrations
• Real-time processing: Events trigger flows and update segments within seconds

• Reverse ETL: Sync Klaviyo segments and profile data back to your data warehouse or other tools
• Custom objects: Define custom data models beyond profiles and events (e.g., subscriptions, loyalty tiers, support tickets)
• Advanced webhooks: System-level event-driven webhooks with HMAC-SHA256 signing — fire on any event (email received, clicked, spam complaint, review events, consent events). Distinct from flow webhooks
• Data transforms: Transform incoming data before it reaches profiles
• Warehouse sync: Bidirectional sync with data warehouses (Snowflake, BigQuery, Redshift)
• Pricing: Enterprise-only — custom pricing, not available on standard Email or Email + SMS plans

• Marketing Agent: Generate complete campaign drafts from a URL — Klaviyo analyzes the page content and creates email copy, subject lines, and design
• Customer Agent: AI-powered support automation that resolves approximately 65% of common support questions, recommends products, and handles order inquiries
• Customer Hub: Self-service portal where customers can track orders, browse FAQ, and get AI-assisted support

• Product catalog sync: Automatically sync products from your e-commerce platform (Shopify, BigCommerce, etc.) for use in emails and flows
• Personalized recommendations: Dynamic product blocks in emails that show products based on browsing history, purchase history, or collaborative filtering
• Back-in-stock alerts: Customers subscribe to notifications when out-of-stock items become available — triggers a flow automatically
• Price drop alerts: Notify customers when items they viewed or wishlisted drop in price

• Unique coupon codes: Generate unique, single-use coupon codes via the API for use in flows and campaigns — prevents code sharing
• Shopify integration: Sync with Shopify discount codes — Klaviyo generates codes that are valid in your Shopify checkout
• Dynamic insertion: Insert unique coupon codes into email/SMS content using template tags

• Revenue attribution: Track revenue generated by each campaign and flow — Klaviyo attributes purchases within a configurable attribution window
• Campaign analytics: Opens, clicks, conversions, revenue, unsubscribes, spam complaints per campaign
• Flow analytics: Per-step metrics showing where recipients convert, drop off, or skip
• Benchmarks: Compare your performance against industry peers (open rates, click rates, revenue per recipient)
• Custom dashboards: Build dashboards with custom metrics, date ranges, and visualizations
• SMS analytics: Delivery rates, click rates, opt-out rates, revenue per SMS

• Drag-and-drop editor: Visual email builder with content blocks (text, image, button, product, table, social links)
• Dynamic blocks: Show/hide content blocks based on profile properties or event data — personalize within a single template
• Mobile-responsive: Templates automatically adapt to mobile screens
• Product feeds: Dynamic product blocks that pull from your catalog based on recommendations, browsing history, or manual selection
• Saved rows/sections: Reusable template components for consistent branding across emails

• Base URL:

  https://a.klaviyo.com/api/

  (server-side),

  https://a.klaviyo.com/client/

  (client-side)
• Authentication:
  • Private API key:

    Authorization: Klaviyo-API-Key {private_key}

    header — used for all server-side endpoints
  • OAuth: For tech partner integrations — scoped access tokens
  • Public API key: Query parameter

    company_id={public_key}

    — used for client-side endpoints only (forms, client events)
• Format: JSON:API spec — resources have

  type

  ,

  id

  ,

  attributes

  , and

  relationships

  . Supports filtering (

  ?filter

  ), sparse fieldsets (

  ?fields[TYPE]

  ), includes (

  ?include

  ), and cursor-based pagination (

  ?page[cursor]

  )
• Rate limits: Fixed-window burst limit (per second) + steady limit (per minute), per-account. OAuth apps get separate quota. Exceeding limits returns HTTP 429
• Key endpoints:

  • POST /api/profiles/

    — create or update a profile (upsert by email or phone)

  • POST /api/events/

    — track a custom event

  • GET /api/campaigns/

    — list campaigns

  • POST /api/campaigns/

    — create a campaign

  • POST /api/campaign-send-jobs/

    — send a campaign

  • GET /api/flows/

    — list flows

  • GET /api/segments/

    — list segments

  • GET /api/metrics/

    — list metrics (event types)

  • POST /api/catalog-items/

    — create a catalog item

  • POST /api/coupon-codes/

    — create a unique coupon code

  • GET /api/webhook-topics/

    — list available webhook topics (Advanced KDP)

  • POST /api/webhooks/

    — create a webhook subscription (Advanced KDP)
  • Client:

    POST /client/subscriptions/

    — subscribe via form (public key auth)
  • Client:

    POST /client/events/

    — track client-side event (public key auth)
• SDKs: Official — Python (

  klaviyo-api

  ), Node.js (

  klaviyo-api

  ), Ruby (

  klaviyo-api-sdk

  ), PHP (

  klaviyo/api

  ). Also: Swift, Android/Kotlin SDKs for mobile push
• Docs: developers.klaviyo.com

• Pricing scales by active profiles — all subscribed contacts count toward your profile limit, not just those you email (Feb 2025 billing change)
• SMS credits are consumed per message segment (longer messages use more credits)
• WhatsApp and RCS messaging available on Email + SMS plan and above

1. Building an abandoned cart flow:
   1. Navigate to Flows > Create Flow > choose "Abandoned Cart" template (or start from scratch)
   2. Set the trigger: "Checkout Started" event (synced from Shopify/BigCommerce) or "Added to Cart" event
   3. Add a time delay — typically 1-4 hours for the first email (shorter delays capture more carts but may annoy customers who are still shopping)
   4. Add a conditional split: check if the "Placed Order" event has occurred since the flow was triggered — if yes, skip (they already converted)
   5. Add the first email step — include dynamic product blocks showing the abandoned items using the event's

      item

      properties
   6. Insert a unique coupon code if offering a discount (Coupons > generate unique codes to prevent sharing)
   7. Add a second time delay (24h) and a second email with stronger urgency or a discount incentive
   8. Optionally add an SMS step after the second email for subscribers with SMS consent — SMS has higher open rates for time-sensitive recovery
   9. Monitor flow analytics: check conversion rate per step, revenue attributed, and unsubscribe rate
2. Setting up real-time segments with predictive attributes:
   1. Navigate to Lists & Segments > Create Segment
   2. Add conditions using the segment builder — combine behavior conditions (placed order in last 90 days) with predictive attributes (predicted CLV is high, churn risk is medium or high)
   3. Use AND/OR logic to define your target audience — e.g., "Placed Order at least 2 times AND Predicted CLV is High AND Churn Risk is Medium"
   4. Preview the segment to verify it captures the expected profiles
   5. Segments update in real-time — as profiles match or stop matching conditions, they enter or exit the segment automatically
   6. Use the segment as a campaign audience, flow trigger condition, or conditional split within a flow
3. Configuring the Shopify-Klaviyo integration:
   1. In Klaviyo, go to Integrations > Add Integration > Shopify
   2. Enter your Shopify store URL and authorize the connection
   3. Klaviyo syncs: customers (as profiles), orders (as "Placed Order" events), products (as catalog items), carts (as "Added to Cart" / "Checkout Started" events)
   4. Enable on-site tracking: Klaviyo's JavaScript snippet is added to your Shopify theme to track browse behavior ("Viewed Product", "Active on Site")
   5. Verify data is flowing: check Metrics in Klaviyo to confirm Shopify events are appearing
   6. Set up core flows that leverage Shopify data: abandoned cart (Checkout Started trigger), post-purchase (Placed Order trigger), browse abandonment (Viewed Product trigger), back-in-stock (catalog sync)
   7. Enable Shopify coupon sync if using unique coupon codes in flows
4. Setting up SMS alongside email:
   1. Ensure you are on the Email + SMS plan (from $35/mo)
   2. Complete SMS compliance setup: register your brand for 10DLC (US), set up toll-free or short code numbers, configure quiet hours
   3. Create SMS consent collection: add an SMS opt-in step to your signup forms (multi-step forms work best — collect email first, then SMS consent)
   4. Build cross-channel flows: in your existing flows, add SMS steps after email steps — e.g., if email not opened after 24h, send SMS
   5. Respect channel preferences: use conditional splits to check SMS consent before sending SMS steps
   6. Monitor SMS-specific metrics: delivery rate, click rate, opt-out rate, revenue per SMS
5. Using the Klaviyo API to sync custom data:
   1. Generate a private API key in Klaviyo: Account > Settings > API Keys > Create Private API Key
   2. Set appropriate scopes — only grant the scopes your integration needs (profiles read/write, events write, etc.)
   3. Use JSON:API format for all requests — wrap data in

      {"data": {"type": "...", "attributes": {...}}}

      structure
   4. Upsert profiles:

      POST /api/profiles/

      — Klaviyo matches on email or phone and updates if existing, creates if new
   5. Track events:

      POST /api/events/

      — pass metric name, profile identifier, properties, and timestamp
   6. Handle rate limits: implement exponential backoff when receiving HTTP 429 responses
   7. Use cursor-based pagination for list endpoints: follow the

      links.next

      URL in responses

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.

1. Profile-based billing counts ALL active profiles (Feb 2025 change) — not just those you email. A large imported list you never email still counts toward your profile limit and billing tier. Clean regularly by suppressing or deleting profiles you do not intend to contact. This is a significant change from the previous model where only emailed profiles counted.
2. Advanced KDP (custom objects, reverse ETL, advanced webhooks) is enterprise-only pricing — don't assume it's available on standard plans. Features like custom objects, warehouse sync, data transforms, and system-level webhooks require the Advanced KDP tier with custom enterprise pricing. Standard Email and Email + SMS plans do not include these capabilities.
3. Flow webhooks are NOT the same as system webhooks — flow webhooks fire as a flow action step, system webhooks (Advanced KDP) fire on any event. Most accounts only have access to flow webhooks (a POST action within a flow step). System webhooks that fire on email events (received, clicked, spam), review events, and consent events with HMAC-SHA256 signing are an Advanced KDP feature. Don't confuse the two when planning integrations.
4. SMS requires separate compliance setup (TCPA/10DLC in US, carrier registration) — don't assume SMS is ready to use just because you're on the Email + SMS plan. You must register your brand, verify your phone number, configure quiet hours, and comply with carrier requirements before sending SMS. This registration process can take days to weeks depending on carrier approval timelines.
5. Predictive analytics require sufficient data (typically 500+ orders and 180+ days of history) — new stores won't see predictions immediately. Features like predicted CLV, churn risk, next order date, and gender prediction need a meaningful volume of historical order data before Klaviyo's models produce results. If you just launched your store or recently migrated to Klaviyo, expect to wait until you accumulate enough data.

• /sales-email-marketing

  — Opt-in email marketing strategy across tools

• /sales-deliverability

  — Cross-platform email deliverability (SPF/DKIM/DMARC, warmup, inbox placement)

• /sales-email-tracking

  — Email engagement tracking strategy

• /sales-integration

  — Connect Klaviyo to CRM, warehouse, or other tools

• /sales-checkout

  — Checkout optimization (Klaviyo integrates with e-commerce checkout flows)

• /sales-customerio

  — Customer.io platform help (primary Klaviyo competitor for behavior-driven automation)

• /sales-mailchimp

  — Mailchimp platform help (primary Klaviyo competitor for email marketing)

• /sales-do

  — Not sure which skill to use? The router matches any sales objective to the right skill. Install:

  npx skills add sales-skills/sales --skills sales-do

1. Confirms Shopify integration is syncing "Checkout Started" events (the trigger for abandoned cart flows)
2. Creates a flow with "Checkout Started" trigger and an immediate conditional split checking if "Placed Order" has occurred (to skip converters)
3. Adds a 2-hour time delay, then the first email with dynamic product blocks showing abandoned items and a clear CTA to complete checkout
4. Adds a 24-hour time delay, then a second email with urgency copy and a unique coupon code (10% off) generated via Klaviyo's coupon feature
5. After the second email, adds a conditional split checking SMS consent — if consented, sends an SMS reminder with a short link to the cart after 12 more hours
6. Recommends monitoring per-step conversion rates and adjusting time delays based on data (shorter delays for high-AOV products, longer for browse-stage abandonment) Result: User has a multi-touch, cross-channel abandoned cart flow that recovers revenue via email first, then SMS for non-openers, with unique coupon codes to prevent abuse

1. Designs a multi-step signup form: step 1 collects email (with incentive, e.g., 15% off first order), step 2 asks for phone number and SMS consent with a clear value proposition ("Get exclusive SMS-only deals")
2. Creates a welcome flow triggered by "Subscribed to List" — the list the form adds subscribers to
3. First email (immediate): delivers the welcome discount code, introduces the brand, sets email frequency expectations
4. Adds a conditional split after 24 hours: checks if the profile has SMS consent — if yes, sends a welcome SMS with a different exclusive offer to reward SMS opt-in
5. Continues the email series: email 2 (day 3) highlights best-selling products with dynamic product blocks, email 3 (day 5) shares social proof / customer stories, email 4 (day 7) features category browsing with personalized recommendations
6. Adds a final conditional split at day 14: if no purchase yet, sends a last-chance reminder with the original discount code expiring soon Result: User has a welcome series that maximizes both email and SMS list growth, delivers a cohesive onboarding experience, and drives first purchase conversion

1. Confirms the store has sufficient data for predictive analytics (500+ orders, 180+ days of history) — if not, recommends a behavior-based approximation (e.g., "placed order 2+ times but not in last 90 days")
2. Creates a segment combining predictive attributes: "Predicted CLV is High AND Churn Risk is Medium or High" — targets high-value customers showing signs of disengagement
3. Builds a winback flow triggered by segment entry: when a profile enters this segment (churn risk increases), they enter the flow automatically
4. Flow sequence: email 1 (day 0) is a personal check-in with product recommendations based on past purchases; email 2 (day 4) highlights new arrivals or restocks in their preferred categories; email 3 (day 8) offers an exclusive loyalty incentive (unique coupon code, free shipping, or loyalty points)
5. Adds a conditional split after email 3: if still no purchase, sends an SMS (if consented) with a time-limited offer
6. Recommends monitoring the segment size over time — if it is growing, investigate root causes (product issues, shipping delays, competitive pressure) rather than relying solely on automation Result: User has a proactive churn prevention system that automatically identifies at-risk high-value customers and re-engages them with a personalized multi-touch sequence before they lapse