A Klaviyo Integration for the Checkout, CRM or Ad Account That Isn't on Klaviyo's List
The welcome series is built and the abandoned-cart flow is drafted, and then it turns out your store runs on something Klaviyo doesn't connect to. Klaviyo's native integrations cover the large e-commerce platforms, and its directory lists hundreds of other apps. Anything outside those reaches Klaviyo through its APIs. Built carefully, that feed carries the same orders, products and browsing events a native store sends.
Native e-commerce integrations: Shopify, WooCommerce, BigCommerce, Magento (Adobe Commerce), PrestaShop, Salesforce Commerce Cloud, Square Online and Wix, among others. These bring orders, customers and products in for you.
Listed apps: hundreds more in Klaviyo's integrations directory, from Google Ads and Meta to help desks such as Gorgias. Read each listing for what it actually syncs.
Everything else: a custom checkout, a wholesale portal, an ERP, or CRM fields a listed app doesn't carry go in through Klaviyo's APIs.
What a custom-checkout feed sends Klaviyo, in the order it gets built
- 1
Profiles and consent
Every shopper becomes a profile keyed on email or phone number. Email and SMS consent go through Klaviyo's subscription endpoints, not just a field on the profile, or flows end up mailing the wrong people or nobody.
- 2
The catalog
Products, variants, prices and stock go in through the Catalogs API, so product blocks and recommendations in your emails have real items to pull from.
- 3
Shopping events
Viewed Product, Started Checkout and Placed Order, named the way Klaviyo's own integrations name them, so your flows and reports read like a native store's and each moment has a single name.
Watch for: two systems sending the same order under different event names. Klaviyo treats them as two separate metrics, and a flow only listens to one of them.
- 4
Past orders
Past orders load so segments such as "bought twice this year" work from the first day.
Watch for: a backfill running while post-purchase flows are live. Hold those flows until the history is in.
- 5
Fulfillment and refunds
Shipped, cancelled and refunded orders go in as events of their own, so shipping messages and win-back flows act on what really happened to the order.
A listed Klaviyo integration beside an API feed built for your store
Native integration
- Klaviyo or the platform builds and updates it, so platform changes are handled on their side.
- Data arrives in Klaviyo's standard shape, ready for segments and flows.
- Covers what the platform exposes, and none of what your business added on top.
API feed
- Reaches systems no listing covers: a custom checkout, an ERP, a wholesale portal, a loyalty platform.
- Sends custom profile properties a native sync leaves out, like account tier or contract status.
- Needs an owner on your side when either system changes its API.
The two sit together without trouble: the native integration for the storefront, and a feed for whatever sits behind it.
Questions people ask
Does Klaviyo work with WooCommerce?
Yes. WooCommerce is one of Klaviyo's native e-commerce integrations, installed through Klaviyo's plugin on the store, and it brings orders, customers and products into Klaviyo for flows and segments.
Can Klaviyo connect to Salesforce or HubSpot?
Both appear among Klaviyo's integrations, so start with the listing and check what it carries. CRM connectors tend to move profile and activity data. Deal stage, account owner or pipeline value on a Klaviyo profile normally takes an API sync that writes them as custom properties.
Does Klaviyo integrate with Google Ads?
Yes. Google Ads is one of Klaviyo's listed integrations, used to send a list or segment over as an ad audience, so targeting follows your current segments instead of an exported file from months ago.
What if my e-commerce platform isn't one of Klaviyo's native integrations?
Then the connection goes through Klaviyo's APIs: profiles, catalog, shopping events and order history, as in the steps above. Built that way, flows and segments get the same depth of data a native store provides.
Can I integrate Klaviyo with a custom-built checkout?
Yes, through the API, since a one-off checkout has no native app. n-frames builds that feed around how your checkout actually works, sending Started Checkout and Placed Order from the moments they really happen.