Skio to Tatari
Forward every Skio event to Tatari server-side, resolved to a person against a 750M+ device graph — with restored click IDs, deduplicated conversions and delivery you can audit.
Connection
Connect Skio to Tatari with Upstack Data
Skio
Capture Skio subscription events server-side, with the first charge distinguished from every renewal that follows it.
Skio integration
Tatari
Send resolved purchases to Tatari so linear and streaming TV are measured against the same order data as every other channel.
Tatari integrationWhat changes
What changes when Skio feeds Tatari.
Server-side delivery
Events reach Tatari through its server API, not the browser — so ad blockers, ITP and consent banners don’t cost you conversions.
Identity-resolved events
Every event sent to Tatari carries a resolved customer, matched against a 750M+ device graph.
Every event, server-side
Storefront and checkout events are captured from Skio on the server, independent of the browser.
One setup, every destination
Connect Skio once and forward to every ad platform, email tool and warehouse you run.
What actually moves
What Skio carries, and what Tatari needs.
Skio and Tatari describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Skio can put on an event, the right is what Tatari can actually use.
Skio sends
- subscription_id
- the Skio subscription, stable across charges
- email / phone
- subscriber contact
- charge_type
- first charge, renewal, swap or skip
- line_items
- products on this charge
- total / interval
- charge amount and billing cadence
- customer_type
- new or returning, resolved before send
Tatari receives
- hashed email / phone
- match a purchase to an exposed household
- ip / user_agent
- household matching for a no-click channel
- order timestamp
- correlate against airing times
- value / currency
- feed the incrementality model revenue
- customer_type
- separate acquisition from repeat purchase
Delivery you can audit
How you know it is working.
Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.
Per-event inspection
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.Deduplication
Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.Bot and fraud filtering
Automated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Where to check in Tatari
TatariMeasurementConversions. The conversion feed is the input to the lift model, so its completeness is checked here first.
Related connectors
Other places Skio can send to.
- SkioMeta Conversions API
- SkioGoogle Ads Conversions
- SkioTikTok Events API
- SkioPinterest
- SkioSnapchat
- SkioReddit
- SkioMicrosoft Ads
- SkioX
Other sources that feed Tatari.
- ShopifyTatari
- WooCommerceTatari
- BigCommerceTatari
- Checkout ChampTatari
- RechargeTatari
- Custom stackTatari
- FunnelishTatari
- Lasso CommerceTatari
- Phoenix TechnologiesTatari
- Loop SubscriptionsTatari
- StripeTatari
- Everything Tatari can take12 sources feed Tatari, and the setup is the same for each one.Tatari integration
- How resolution worksEvery event matched against a 750M+ device graph before it is forwarded.Upstack Signal
- What it costsThree plans that scale with your order volume. Every connector is on every plan.See pricing
Get Skio talking to Tatari.
A 15-minute walkthrough of this connector on your own account.