> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abconvert.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Configure ABConvert with analytics, session replay, data warehouse, marketing, and subscription tools that already run on your Shopify storefront.

<Warning>
  **Pre-release.** These cards appear only when the Integrations hub is enabled for your ABConvert account. Your vendor setup must already be active before you turn on an ABConvert integration.
</Warning>

Use an integration to add ABConvert test-group context to a tool you already own. ABConvert does not install a vendor SDK, create a vendor account, or replace the vendor's consent controls.

## Choose the right integration for your goal

| Integration                                  | Configure in your vendor                               | ABConvert sends or reads                       | Common use                                             |
| -------------------------------------------- | ------------------------------------------------------ | ---------------------------------------------- | ------------------------------------------------------ |
| [Clarity](/integrations/clarity)             | Clarity web tag and project                            | Session tags and an assignment event           | Review recordings by test group                        |
| [Hotjar](/integrations/hotjar)               | Hotjar tracking code, User Attributes, session capture | Session attributes and an assignment event     | Filter recordings or target a survey                   |
| [Contentsquare](/integrations/contentsquare) | Contentsquare tag and approved domain                  | A dynamic variable per assigned test           | Compare journeys and zones by test group               |
| [Heatmap](/integrations/heatmap)             | Heatmap storefront script                              | A partner test-group tag                       | Compare heatmaps and recordings                        |
| [Amplitude](/integrations/amplitude)         | Amplitude Browser SDK and project                      | `$exposure` event                              | Analyze funnels and retention by test group            |
| [Mixpanel](/integrations/mixpanel)           | Mixpanel Browser SDK and project                       | `$experiment_started` event and super property | Use Mixpanel Experiments and funnels                   |
| [Segment](/integrations/segment)             | Segment Browser SDK and destinations                   | `Experiment Viewed` event                      | Route assignment context to your stack                 |
| [Klaviyo](/integrations/klaviyo)             | Klaviyo onsite tracking or a read-only API key         | Test-entry metric or segment membership        | Build flows and target tests by segment                |
| [BigQuery](/integrations/bigquery)           | BigQuery dataset permission                            | Daily copies of test and attributed-order data | Join tests to warehouse metrics                        |
| [Recharge](/integrations/recharge)           | Recharge API credentials and owned plans               | Subscription lifecycle and renewal attribution | Measure subscription outcomes                          |
| [SKIO](/integrations/skio)                   | SKIO Webhooks and owned Shopify selling plans          | Token-bearing lifecycle deliveries             | Offer an existing subscription plan in a checkout test |

## How every browser integration works

<Steps>
  <Step title="Install one vendor browser SDK">
    Install the vendor's storefront SDK through either its Shopify app or your theme. Do not install the same vendor browser SDK twice.
  </Step>

  <Step title="Apply your consent policy">
    Load the vendor SDK only under the analytics or marketing consent policy that applies to your store. ABConvert calls an SDK that is already available in the visitor's browser.
  </Step>

  <Step title="Enable the ABConvert card">
    In **Integrations**, enable the provider. ABConvert waits for the provider client and sends data only after a visitor receives an eligible active test assignment.
  </Step>

  <Step title="Verify vendor receipt">
    Use a fresh, consented visitor in an eligible test. Confirm the matching event, tag, session attribute, or warehouse row in the vendor product. A Connected or Called status confirms ABConvert's local handoff, not necessarily vendor ingestion.
  </Step>
</Steps>

## How subscription integrations work

Subscription integrations use plans that your subscription provider already owns. ABConvert does not create a plan or change its recurring price.

<Steps>
  <Step title="Connect the provider">
    Open the provider card in **Integrations**. Recharge validates its API credentials and manages its webhook registration. For SKIO, copy the ABConvert endpoint into SKIO Webhooks, then save the token SKIO returns.
  </Step>

  <Step title="Select an existing selling plan">
    In the checkout test, choose an existing provider-owned plan for each eligible test group. Do not change a subscription price directly in ABConvert.
  </Step>

  <Step title="Confirm the provider-specific signal">
    Recharge reads **Connected** after its credentials and webhook registration are verified. SKIO reads **Event received** after a token-bearing webhook reaches ABConvert. In either case, confirm an attributed subscription outcome before using lifecycle results to make a decision.
  </Step>
</Steps>

<Info>
  The two status labels describe different setup paths. Recharge has an API connection that ABConvert can validate and repair. SKIO webhooks are created in the SKIO dashboard, so **Event received** confirms inbound delivery from that manual setup; it does not by itself confirm lifecycle attribution.
</Info>

## What integrations do not do

* They do not create a test, choose a winner, or replace ABConvert's test statistics.
* They do not automatically make checkout, order, or purchase events appear in an analytics vendor. Configure those events in that vendor or its Shopify app.
* They do not bypass a consent manager, ad blocker, vendor plan requirement, or vendor project/domain setting.
* Preview and forced-assignment visits are excluded from attribution integrations. Verify with an ordinary eligible storefront visit.