Klaviyo E Commerce Marketing Skill For integrating Klaviyo email/SMS marketing customer profiles, event tracking, campaigns, flows, and segmentation. Sources: [Klaviyo API Docs](https://developers.klaviyo.com/en/docs) [API Reference](https://developers.klaviyo.com/en/reference/api overview) Why Klaviyo Feature Benefit E commerce Native Built for online stores, deep integrations Event Based Trigger flows from any customer action Segmentation Advanced filtering on behavior + properties Email + SMS Unified platform for both channels Analytics Revenue attribution per campaign API Basics Base URLs Type URL Server side (Private) https://a.klaviyo.com/api Client side (Public) https://a.klaviyo.com/client Authentication API Key Scopes Scope Access Read only View data only Full Read + write (default) Custom Specific permissions Installation Node.js Python Direct HTTP (Any Language) Profiles (Customers) Create/Update Profile Get Profile Update Profile Properties Events (Tracking) Track Event (Server Side) Common E Commerce Events Client Side Tracking (JavaScript) Lists & Segments Add Profile to List Remove from List Get List Members Create List Campaigns Get Campaigns Get Campaign Performance Flows (Automations) Get Flows Common Flow Triggers Flow Type Trigger Event Welcome Series Added to List Abandoned Cart Added to Cart + No Purchase Browse Abandon Viewed Product + No Cart Post Purchase Placed Order Winback No Order in X Days Review Request Fulfilled Order Webhooks Create Webhook Webhook Topics Topic Trigger profile.created New profile created profile.updated Profile properties changed profile.merged Profiles merged event.created New event tracked list.member.added Profile added to list list.member.removed Profile removed from list Verify Webhook Signature Rate Limits Window Limit Burst 75 requests/second Steady 700 requests/minute Handle Rate Limiting Pagination Filtering & Sorting Integration Patterns E Commerce Order Sync Subscription Status Sync Environment Variables Add to credentials.md : Checklist Setup [ ] Klaviyo account created [ ] Private API key generated [ ] Public API key noted (company ID) [ ] API revision set in headers Integration [ ] Profile sync on signup/update [ ] Key events tracked (view, cart, order) [ ] Order events include Items array [ ] Revenue tracked with $value [ ] Unique IDs for deduplication Testing [ ] Test profile creation [ ] Test event tracking [ ] Verify events in Klaviyo dashboard [ ] Test webhook delivery [ ] Test rate limit handling Anti Patterns Missing email/phone Every profile needs at least one identifier Duplicate events Use unique id for orders/transactions Missing Items array Required for product recommendations Client side only Server side tracking is more reliable Ignoring rate limits Implement exponential backoff Hardcoded API keys Use environment variables Missing revenue tracking Include $value for ROI attribution