# Klaviyo Integration ## How to Set Up Your Klaviyo Integration Once you have the Because app installed, you can access it via your app list in Shopify. Once you’re inside the app, navigate to the upper right corner where you’ll see your Profile labeled with your initials. Click the dropdown menu and select **Integrations**.

*** ## Connecting Your Klaviyo Account By clicking on **Connect** in our integrations tab, you’ll be taken to the specific Klaviyo Integration page. This is where you will find additional details about the integration, with some simple instructions to follow to get set up quickly!

1. You’ll first need to navigate to the [API Keys tab](https://www.klaviyo.com/account#api-keys-tab?) inside your Klaviyo Dashboard. It should look a little something like this:

2. Then you'll just click on **Create Private API Key.** 1. When prompted, choose 'full access' from the dropdown. 2. You can name this whatever you like ("**Because**" has been the popular choice so far). 3. Once the **Private API Key** has been created, you’ll simply paste it into the field in our Integration tab.

It really is that simple! Once you’ve provided the API key, our backend will fetch the corresponding Campaigns, Segments, and Flows information! You will then have access to all of these options inside the Rules Engine, as that Rule Category will now be enabled for you as well!

You’ll want to reference our more detailed **Integration Use Cases** [here](https://www.trybecause.com/posts/klaviyo) for some ideas to get started! Klaviyo's full instructions on API keys are [here](https://developers.klaviyo.com/en/v1-2/docs/retrieve-api-credentials) as well if you need them, and as as always, should you run into any issues our team will be happy to help anytime! *** ## When to Use Segments vs. Flows & Campaigns ### Limitations of Flows & Campaigns The site visitor has to arrive on site directly from a Message in the Flow that you select (or from the Campaign you select), meaning they have to open and click the email and arrive on site via that click. Flows and Campaigns are limited in their scope in our current integration with Klaviyo because they will only work to show a Banner/Text Element on the Product page or Collection page you link to in your Welcome Flow Message (your landing page). So for example, you’d have to link the exact Product Page you want to show your Banner/Text Element on into your Flow as your landing page. Once a site visitor arrives on that Product Page (or Collection Page) and moves somewhere else on site, Because loses their identity. ### Using Segments to Fill the Gaps on Flows & Campaigns As an alternate option (and much more robust), you can create a Segment of users who have received (or even opened) a Welcome Flow message. You can then target those site visitors using Because on any Product Page or Collection Page of your site regardless of whether or not they’re coming from a Flow Message or just starting their own browsing session separately from an email. The other advantage of Segment targeting is that the user’s identity will persist throughout their shopping experience (meaning we know who they are) even as they move around the site. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://because.gitbook.io/because/integrations/klaviyo-integration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.