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 tests assign provider-owned plans to products in subscription test groups. A one-time purchase test group sells the same products without plans. You can select an existing Recharge, Stay.AI, or SKIO plan. Set up your plans and your app’s product page widget first; see Before you start. You can also create a Recharge plan from the test if your Recharge API token haswrite_plans permission. ABConvert does not change the recurring price of an existing plan.
1
Connect the provider
Open the provider card in Integrations. Recharge validates its API credentials and manages its webhook registration. Stay.AI checks its API key and sets up its webhooks. For SKIO, add the ABConvert endpoint in SKIO Webhooks, save its returned webhook token, and configure the separate API key and site ID described in SKIO setup.
2
Select products and plans
In a subscription test, choose your products, then assign a plan for each product in every subscription test group. A one-time purchase test group needs no plan. SKIO and Stay.AI plans must already exist. For Recharge, select existing plans or create them from the test.
3
Confirm the provider-specific signal
Recharge reads Connected after its credentials and webhook registration are verified. Stay.AI reads Connected after its API key is verified, and tracks first orders only. SKIO reads Delivery unverified after a token-bearing delivery until a separate API lookup verifies the subscription event. Saving an API key alone does not mark the connection Connected.
The labels describe different trust states. Recharge has an API connection that ABConvert can validate and repair. SKIO webhooks do not sign the event body, so ABConvert verifies subscription facts through a separate API connection before applying them. Paid renewals also require Shopify payment confirmation.
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.