Skip to main content
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.
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

​
How every browser integration works

1

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.
2

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.
3

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. Amplitude, Mixpanel, Segment, and Klaviyo wait until the visitor sees the test: for a URL redirect test or template test, that is a visit to its trigger page or template.
4

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 or queued status confirms ABConvert’s local handoff, not necessarily vendor ingestion.

​
Read the card status

A status only confirms ABConvert’s handoff in the visitor’s browser. Confirm receipt in the vendor product. Turning an integration off and on again resets it to waiting until a new handoff.

​
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.
1

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 and save its returned webhook token.
2

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.
3

Confirm the provider-specific signal

Recharge reads Connected after its credentials and webhook registration are verified. After a standard token-bearing SKIO webhook reaches ABConvert, SKIO reads Delivery unverified. The token echo does not authenticate the request body, so this confirms receipt only and does not add subscription lifecycle outcomes to test results.
The labels describe different trust states. Recharge has an API connection that ABConvert can validate and repair. SKIO webhooks are created in the SKIO dashboard, so a token-bearing delivery remains Delivery unverified because it does not prove that SKIO sent the request. Standard SKIO webhooks do not provide lifecycle attribution.

​
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.