- US device IDs in the graph
- 750M+
- Match rate on events
- 90%+
- Identity window, per customer
- Lifetime
- Most brands are live
- <20 min
How it flows
How a Skio event reaches X. Captured on the server, resolved to a person, then sent.
01 Capture
Captured from Skio
Capture Skio subscription events server-side, with the first charge distinguished from every renewal that follows it.
See the Skio integration →
SkioWhat it sends subscription_idthe Skio subscription, stable across chargesemail / phonesubscriber contactcharge_typefirst charge, renewal, swap or skipline_itemsproducts on this chargetotal / intervalcharge amount and billing cadence
02 Understand
Resolved to one person before it leaves
Every Skio event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.
How resolution works →
Resolved 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.
03 Activate
Delivered to X
Server-side conversions to the X Conversions API, resolved to a person and deduplicated against the browser pixel.
See the X integration →
XWhat it receives hashed email / phoneidentity matching on arrivaltwclidcredit the click that drove itexternal_idstable person across sessionsevent_iddedupe against the browser pixelvalue / currencyvalue-based bidding
The catch
A first charge is an acquisition and a renewal is not, but both arrive as purchases.
Sending renewals as conversions is the single most common way a subscription brand teaches Meta to re-buy its existing subscribers.
Where to check in XDelivery you can audit
X Ads › Tools › Events Manager
The events table separates browser and server events, so a deduplicated pair shows as one conversion.
What changes
What changes when Skio feeds X. Two gains on the X side, two on the Skio side.
X
Server-side delivery
Events reach X through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
X
Identity-resolved events
Events sent to X carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.
Skio
Every event, server-side
Storefront and checkout events are captured from Skio on the server, independent of the browser.
Skio
One setup, every destination
Connect Skio once and forward to every ad platform, email tool and warehouse you run.
Setup
Live in under 20 minutes.
Connect Skio once and every destination, X included, is forwarded the same resolved events.
Upstack dashboardExample
Skio Data source Connected
X Destination Healthy
Read the full X setup guide → -
01
Connect Skio
Capture Skio subscription events server-side, with the first charge distinguished from every renewal that follows it.
-
02
Add the X destination
Under Destinations, add X. Every resolved Skio event is then forwarded to it.
-
03
Check delivery to X
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.
FAQ
Questions about Skio and X.
How do I check that Skio events are reaching X?
Open X Ads › Tools › Events Manager. The events table separates browser and server events, so a deduplicated pair shows as one conversion.
Will a purchase be counted twice?
No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
How long does it take to connect Skio to X?
Most brands are live in under 20 minutes. Once Skio is connected, every destination receives the same resolved events, X included.