Skip to main content
Request a demo
  1. Home
  2. Integrations
  3. Skio
Upstack Data

Skio integration: every charge captured server-side and resolved to a person

Capture Skio subscription events server-side, with the first charge distinguished from every renewal that follows it.

Request a demo Start free trial
Role
Source
Category
Payments & subscriptions
Pre-built connectors
34 destinations
Plans
All plans

What Upstack captures

Every Skio event leaves resolved to a person. Captured on the server, resolved to a person, then sent.

In: from SkioWhat it carries
  • subscription_idthe Skio subscription, stable across charges
  • email / phonesubscriber contact
  • charge_typefirst charge, renewal, swap or skip
  • line_itemsproducts on this charge
  • total / intervalcharge amount and billing cadence

First charges and renewals, told apart.

Upstack DataResolved before it is sent
  • IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
  • customer_typeNew or returning, resolved before send.
  • DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
  • Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Out: to Meta Conversions API1 of 34 destinations
  • em, ph (SHA-256)raise Event Match Quality
  • fbclid / _fbpcredit the click that drove it
  • external_idstable person across sessions
  • event_iddedupe against the browser pixel
  • value / currencyvalue-based bidding

Conversions API with higher Event Match Quality.

See the set-up reference See all 34 destinations How resolution works

About Skio

Upstack reads that distinction and preserves it.

New subscriptions can be forwarded as their own conversion, renewals as recurring revenue, cancellations as state changes rather than silence. Ad platforms then optimize toward acquiring subscribers instead of re-finding the ones you already have.

What Skio is

Skio builds subscription infrastructure for Shopify brands, with a focus on making subscriptions feel native rather than bolted on.

A subscription produces one acquisition and then many charges, and downstream tools see them all as identical revenue.

How Skio works

Skio manages the subscription lifecycle: the first charge, then renewals on a schedule, plus swaps, skips, pauses and cancellations. Each updates state, and only the first is an acquisition. But they all arrive looking like an order.

What you can do with it

Three jobs Skio does once it is connected.

01

Capture every order server-side

Skio events are captured from the server rather than the shopper’s browser, so ad blockers and ITP stop deciding which of your conversions get counted. Nothing depends on a script surviving the page.

02

Resolve each event to a person

Every Skio event is matched against a 750M+ device graph before it leaves, so a phone browse and a desktop checkout resolve to one customer rather than two strangers. Returning buyers are recognized as returning.

03

First charge separated from renewal

The acquisition is forwarded as a conversion and renewals as recurring revenue, so ad platforms stop bidding to re-acquire existing subscribers.

Pre-built connectors

Skio forwards to 34 destinations. Connect Skio once. Every destination is already wired.

See all 34 Skio connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for Skio as a source.

FAQ

Skio integration questions.

What does Upstack capture from Skio?

Capture Skio subscription events server-side, with the first charge distinguished from every renewal that follows it.

Which plans include the Skio integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which destinations can Skio send to?

34 destinations, including Meta Conversions API, Google Ads Conversions, TikTok Events API, Pinterest, Snapchat and Reddit. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other sources to connect.

See all integrations

Get Skio tracking right.

A 15-minute walkthrough tailored to your stack and channels.

Request a demo Start free trial