> For the complete documentation index, see [llms.txt](https://because.gitbook.io/because/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://because.gitbook.io/because/integrations.md).

# Integrations

- [Klaviyo Integration](https://because.gitbook.io/because/integrations/klaviyo-integration.md): The Because + Klaviyo integration introduces a whole new world of website personalization opportunities based on Klaviyo data.
- [Understanding Klaviyo Targeting Logic in Because](https://because.gitbook.io/because/integrations/klaviyo-integration/understanding-klaviyo-targeting-logic-in-because.md)
- [Klaviyo Use Cases](https://because.gitbook.io/because/integrations/klaviyo-integration/klaviyo-use-cases.md): The Because Klaviyo integration is a powerful feature that dynamically personalizes on-site content based on Klaviyo data.
- [How to Link Klaviyo Popups to Because Campaigns](https://because.gitbook.io/because/integrations/klaviyo-integration/how-to-link-klaviyo-popups-to-because-campaigns.md): Want to capture more email subscribers and increase conversions? Because now allows you to seamlessly trigger a Klaviyo popup from a Because campaign.
- [Klaviyo Profile Data & Dynamic Text Tokens](https://because.gitbook.io/because/integrations/klaviyo-integration/klaviyo-profile-data-and-dynamic-text-tokens.md): The Because app now offers a deeper integration with Klaviyo, giving you direct access to customer profile data attributes—without needing to create dedicated segments.
- [Shopify Data Integration](https://because.gitbook.io/because/integrations/shopify-data-integration.md): The Because app now integrates directly with Shopify customer data, allowing you to create more personalized shopping experiences based on past customer behavior—without needing complex segmentation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://because.gitbook.io/because/integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.