Can I integrate more than one store with one Klaviyo account?

  • 27 November 2020
  • 3 replies
  • 6039 views

Userlevel 4
Badge +15

Klaviyo currently supports only one integration of any type within a single Klaviyo account.

If you have more than one ecommerce store of the same type, you will need to create a Klaviyo account for each store. If you have more than one store, and each is supported by a different platform, it is technically possible to integrate all stores with the same Klaviyo account. However, we highly recommend against this option in order to streamline data analysis and prevent confusion amongst metrics with flows and segments. We don’t provide a way to separate stores within a single Klaviyo account.

For more information on the multi-account setup that we recommend, head to this Community conversation on the topic or the Multi-Account User Privileges article.

If you are using Magento, it’s possible to integrate a Magento server that has multiple stores on it. When you do this, we will sync all profiles and order data from each store into your account. Additionally, we will sync “Magento Store Name” and “Magento Website ID” properties for each profile created so you can identify the store where a profile belongs. Then, you can configure our extension on a site-by-site level to pick which list to add subscribers to, and you can filter flows and segments, using the Magento store name to separate flows between stores.


3 replies

Badge +1

This is really disappointing as It doesn’t seem to be documented anywhere and we are in the process of consolidating our 3 instance of Klaviyo into 1 and combine our offline sales into the database.

 

Is there a plan to resolve this issue? We run multiple stores across the globe and this suddenly it makes the tool more expensive to use.

 

Out of curiosity, why can’t you have more than one connection to Klaviyo? Is it a technical limitation or was just not thought of when it was built originally?

Userlevel 7
Badge +61

Hello @GregAtMud,

Thank you for sharing this feedback and thank you @ashley_mcdermott for your reply.

Greg, with respect to your first question, we have a note on this in our Integration FAQ (where Ashley sourced this information from). 

To speak to your second question, allowing a 1:1 store to Klaviyo integration was deliberate. Allow me to elaborate a bit on this point to help explain why: “streamline data analysis and prevent confusion amongst metrics with flows and segments”, this is because when integrating an ecommerce store with Klaviyo, Klaviyo’s onsite javascript is injected onto your page.This script contains a unique public API key linked to your Klaviyo account and is responsible for powering Klaviyo forms, capturing web tracking and ecommerce metrics specific to the Klaviyo account associated with that public API key. In theory, if you integrated multiple stores, you would need a corresponding Klaviyo onsite js script to “send data” to each discrete store (think multiple stores = multiple scripts). And running multiple scripts, will be problematic for a few reasons. For one, it will negatively impact site speed (performance). Second and more importantly, we wouldn’t be able to reliably power our (Klaviyo) forms if multiple scripts are present on your website, nor would we be able to reliably funnel metrics into the correct Klaviyo account. Say someone views a product on your site but there are 3 separate scripts present with 3 separate API keys (each representing a different Klaviyo account), which account should this “Viewed Product” metric go to? So technically speaking it’s possible to do but will have a negative impact on your site performance and we cannot guarantee that Klaviyo metrics will flow accurately into your various Klaviyo accounts.

I hope that helps explain the “why” a bit more and the best solution here is to open up different accounts for each store.

 

 

Badge +1

I might understand having to need 2 klaviyo accounts for 2 separate stores, but does this also mean you have to pay twice? Seems unfair and expensive

Reply