Klaviyo
Klaviyo is the de facto email and SMS marketing platform for D2C and ecommerce brands. Many B2C onboarding flows need to sync customer events, profile attributes, and list memberships into Klaviyo so the right sequences fire at the right moment. Askel connects to each customer's Klaviyo account once and keeps that data moving without any per-customer plumbing on your end.
What you can do
Create and update profiles
Write profile attributes including email, phone, custom properties, and consent status. Askel uses Klaviyo's upsert endpoint so duplicate profiles are merged rather than created.
Add and remove profiles from lists
Manage list membership based on events in your product. Add a profile to a welcome series list when they sign up, or remove them from a promotional list when they unsubscribe.
Track custom events
Send named events with arbitrary properties to Klaviyo, for example Checkout Completed with order value and SKUs, or Trial Upgraded with plan name. These events can trigger flows or feed segment criteria.
Read segment membership
Check whether a profile belongs to a given segment before deciding what to show or send. No need to export the segment to a spreadsheet and match it by hand.
Trigger flow actions
Fire a flow trigger directly from your product when a key moment happens, such as an abandoned cart, a completed onboarding step, or a lapsed subscription renewal.
Audit every write
Every profile update and event call Askel makes is logged with the payload, the resolved Klaviyo list or event name, the API response, and the user or workflow step that triggered it.
Sending a post-signup welcome flow for a new DTC brand
You sell a customer loyalty platform to direct-to-consumer brands. A new customer, Maple & Ember, runs their marketing out of Klaviyo. When a shopper earns their first loyalty points in your platform, Maple & Ember wants Klaviyo to fire a welcome email series and tag the profile with the shopper's tier. Right now that happens via a nightly CSV export. They want it real-time.
- 1
Connect once
Maple & Ember's Klaviyo admin creates a Private API key with the scopes Askel needs, and pastes it into your product's integration settings. The key is stored encrypted by Askel and never logged.
- 2
Map the data
Askel reads Maple & Ember's Klaviyo lists and custom profile properties. Your team sees that the LoyaltyTier property already exists, so no new property creation is needed. The mapping is confirmed in minutes.
- 3
Dry-run with recent signups
Askel pulls the last 30 profiles that would have been synced and shows exactly which list they would be added to, what the LoyaltyTier property would be set to, and what events would be fired.
- 4
Go live
Activate the workflow. From now on, every first-points event in your platform immediately creates or updates the profile in Klaviyo, adds them to the Welcome Flow list, and sets LoyaltyTier.
- 5
Monitor and adjust
Askel logs each sync in real time. If Maple & Ember renames the LoyaltyTier property or changes a list ID, the affected step pauses and your team is notified before any bad data lands.
API token
Customer's Klaviyo account admin creates a Private API key in Account > Settings > API Keys with the scopes Askel needs, and pastes it into Askel. Askel sends it as `Authorization: Klaviyo-API-Key <key>` per request; the key never reaches your servers. If the customer wants to rotate the key, they paste a new one in the same settings screen and the old one can be revoked immediately.
How Askel sits between your product and the customer's system
FAQ for Klaviyo
Which Klaviyo API version does Askel use?+
What scopes should the Private API key have?+
Can one Klaviyo account be connected to multiple customers in my product?+
What happens if Klaviyo rate-limits a request?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.