Skip to main content
Pre-release. This guide applies when the Integrations hub is enabled for your ABConvert account. Configure SKIO only for the Shopify store connected to ABConvert.
SKIO lets you use the subscription selling plans it already owns in a checkout test and confirm webhook delivery to ABConvert.

​
When to use it

  • Compare two existing SKIO-owned subscription offers, such as monthly and prepaid delivery.
  • Confirm that SKIO sends lifecycle webhooks to ABConvert after you add an endpoint.
  • Select an existing subscription plan for each eligible test group.

​
When not to use it

  • Do not use SKIO standard webhooks to measure subscription lifecycle outcomes in test results. Use Recharge when you need supported lifecycle attribution.
  • Do not use ABConvert to change a recurring price. Create or change offers in SKIO, then select the existing selling plan in your checkout test.
  • Do not paste a SKIO API key as a webhook token. Use the token that SKIO creates for the individual webhook row.

​
How it works

ABConvert reads Shopify selling plans whose owner is SKIO. It does not create plans or change recurring prices. A standard SKIO webhook can reach ABConvert when its saved token matches, but that token does not authenticate the webhook body. ABConvert shows Delivery unverified after a token-echo-only delivery, not Connected. The token does not sign the webhook body. For that reason, standard SKIO webhook events confirm delivery health but do not update subscription lifecycle results for a test group.

​
Setup

1

Create the ABConvert endpoint

In Integrations, open SKIO and select Set up SKIO endpoint. Copy the ABConvert webhook URL.
2

Add the endpoint in SKIO

In the SKIO dashboard, go to API & Integrations → API Keys → Webhooks. Paste the ABConvert URL and select Add webhook.
3

Save the webhook token

Copy the token from the new SKIO webhook row. Return to ABConvert, paste it into Webhook token, then select Save SKIO webhook token. Treat the token as a secret.
4

Confirm delivery

Select the subscription and billing events you need in SKIO. Trigger an event in a test store, then confirm that ABConvert shows Delivery unverified and the event time. This confirms receipt only, not an authenticated provider delivery.
Delivery unverified means ABConvert received a token-echo-only request. It does not prove that SKIO sent the request, and it does not mean that ABConvert can attribute the event to a checkout test or include it in subscription lifecycle results.

​
Select a SKIO subscription plan in a test

ABConvert lists Shopify selling plans whose owner is SKIO for the product in your checkout test. Select one of those existing plans for each eligible test group. The provider remains the source of truth for the plan and its price.

​
Common mistakes

  • Replacing a SKIO webhook creates a new token. Save the replacement token in ABConvert before you test delivery again.
  • Testing with a real customer subscription can create a renewal or billing action. Use a dedicated test store and test subscription instead.
  • Treating an unverified delivery as a working connection can lead to decisions based on forgeable data. Check your checkout test results before using subscription metrics.

​
FAQ

The saved webhook token can be echoed by anyone who has seen it, so it is not proof that SKIO sent the request. Standard SKIO webhooks do not provide a body signature that ABConvert can use to safely mark the connection as working or attribute the event to a test group.
ABConvert does not use standard SKIO webhook events for subscription lifecycle attribution. The events confirm delivery only. Use Recharge if you need supported lifecycle and renewal attribution.
No. Use the token that SKIO shows for the specific webhook row. Keep API keys separate from webhook tokens.