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

# Integrations

See which apps and services work with TA Subscriptions App, and where to connect them.

The **Integrations** page lists the apps and services that work together with TA Subscriptions App. Some need a connection set up in the app. Others just need to be installed on your store and set up in their own app.

## Open the Integrations page

In the app menu, click **Settings**, then click the **Integrations** card.

Each card shows the app's logo, name, and a short description. Click the app name to open its listing on the Shopify App Store in a new tab.

![The Integrations page with its integration cards, the Klaviyo Configure button and status badge highlighted](https://3752025337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F479XnzvtVA5dDE3Rt2Uh%2Fuploads%2Ftno7GK2tuv2OvBIQNN0O%2Fintegrations-list.png?alt=media)

## Available integrations

| Integration                        | What it does with your subscriptions                                                                                                           | Set up in TA Subscriptions App?           | Guide                                                                                                                              |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Klaviyo**                        | Sends subscription events, such as a new subscription, a pause, or a failed payment, to Klaviyo. Use them to trigger flows and build segments. | Yes. Click **Configure** on the card.     | [Klaviyo](https://subscriptions-docs.tech-arms.io/features/integrations/klaviyo.md)                                                |
| **BSS B2B Wholesale Pricing**      | Lets wholesale customers see their B2B price in the subscription widget.                                                                       | No. Install and set it up in its own app. | [BSS B2B Wholesale Pricing](https://subscriptions-docs.tech-arms.io/features/integrations/bss-b2b-wholesale-pricing.md)            |
| **TA Product Labels & Badges**     | Adds labels and badges, such as "Subscribe & Save", to your subscription products.                                                             | No. Install and set it up in its own app. | [TA AI Product Labels & Badges](https://subscriptions-docs.tech-arms.io/features/integrations/ta-ai-product-labels-and-badges.md)  |
| **TA Banner Slider, Sales Pop up** | Promotes your subscription offers with banners, announcement bars, and pop-ups.                                                                | No. Install and set it up in its own app. | [TA Banner Slider, Sales Pop Up](https://subscriptions-docs.tech-arms.io/features/integrations/ta-banner-slider-sales-pop-up.md)   |
| **TA MAPPY: Store Locator & Maps** | Shows your stores, dealers, or pickup points on a map.                                                                                         | No. Install and set it up in its own app. | [TA MAPPY: Store Locator & Maps](https://subscriptions-docs.tech-arms.io/features/integrations/ta-mappy-store-locator-and-maps.md) |

## Integration status

The badge on each card means different things:

* **Klaviyo** shows **Integrated** when the integration is active, your API key is saved, and at least one event is turned on. Otherwise it shows **Not integrated**.
* **The other cards always show Integrated.** This means the app works with TA Subscriptions App. It does not check whether you installed the app on your store.

{% hint style="info" %}
If the page shows **No integrations available yet**, reload the page. If the message stays, contact us.
{% endhint %}

## Good to know

* Integrations are available on every pricing plan.
* Apps other than Klaviyo have their own settings and support team. For questions about how those apps work, contact their support from inside the app.
* Looking for an integration that is not listed? Contact us and tell us which app you use.

*If you need help, feel free to reach out to us via in-app* [***Live chat***](https://go.crisp.chat/chat/embed/?website_id=c4ae10a3-f762-4968-b35a-c931caf62a96)***,*** [***Book a call***](https://calendly.com/ta-subscription-app-support/30min) *or at* [***support@tech-arms.io***](mailto:support@tech-arms.io)***.***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://subscriptions-docs.tech-arms.io/features/integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
