- 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 your warehouse. 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.- DeduplicationStable event IDs, so re-runs and backfills do not double rows.
- Bot and fraud filteringFiltered before load, with the filter decision recorded.
03 Activate
Delivered to your warehouse
A clean, resolved event stream into BigQuery, Snowflake or Redshift: the same data your dashboards run on.
See the warehouse integration → Your warehouseWhat it receives
event_idprimary key you can join onresolved person IDstitch sessions to customersfull property payloadnothing dropped, nothing sampledingest timestamprebuild any point-in-time view
The catch
Without charge_type in the warehouse, subscription revenue and new-customer revenue are indistinguishable, and LTV analysis double-counts the acquisition.
Where to check in your warehouseA stream you can audit
Query the events table directly: count distinct resolved person IDs against count distinct sessions, and compare the ratio to what your analytics reports.
What changes
What changes when Skio feeds your warehouse. Two gains on the warehouse side, two on the Skio side.
Your warehouse
One resolved event stream
The same identity-resolved events that reach your ad platforms, landed in your warehouse.
Your warehouse
Nothing sampled
Full-fidelity events, not an aggregate or a sample.
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, your warehouse included, is forwarded the same resolved events.
Upstack dashboardExample
Skio Data source Connected
Your warehouse Destination Healthy
Read the full warehouse 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 warehouse destination
Under Destinations, add your warehouse. Every resolved Skio event is then forwarded to it.
-
03
Check delivery to your warehouse
Every row traceable to the event that produced it and the time it landed.
FAQ
Questions about Skio and your warehouse.
How do I check that Skio events are reaching your warehouse?
Query the events table directly: count distinct resolved person IDs against count distinct sessions, and compare the ratio to what your analytics reports.
Will re-runs or backfills duplicate rows?
No. Stable event IDs, so re-runs and backfills do not double rows.
How long does it take to connect Skio to your warehouse?
Most brands are live in under 20 minutes. Once Skio is connected, every destination receives the same resolved events, your warehouse included.