Home
Connectors
Skio - Attentive

Send every Skio event to Attentive, server-side

Q: How do I check that Skio events are reaching Attentive?

Open Attentive › the subscriber's timeline, where the event appears against the profile rather than as an unattached activity.

Q: Can one purchase trigger the same flow twice?

No. One order produces one event, so a single purchase cannot trigger the same flow twice.

Q: How long does it take to connect Skio to Attentive?

Most brands are live in under 20 minutes. Once Skio is connected, every destination receives the same resolved events, Attentive included.

Each event is resolved to a person against a 750M+ device graph before it reaches Attentive, so flows trigger on a known profile rather than an anonymous session.

Request a demo Start free trial

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 Attentive. 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 charges
email / phonesubscriber contact
charge_typefirst charge, renewal, swap or skip
line_itemsproducts on this charge
total / 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.
DeduplicationOne order produces one event, so a single purchase cannot trigger the same flow twice.
Bot and fraud filteringAutomated traffic never becomes a profile, so list quality and deliverability are not paying for it.

Messaging mistakes are expensive and public. These controls exist so a flow never fires against a profile that should not have received it.

03 Activate

Delivered to Attentive

Feed resolved customer profiles into Attentive so SMS journeys trigger on people, not sessions.

See the Attentive integration

AttentiveWhat it receives

phonethe subscriber key
emailsecondary identifier for cross-channel
event propertieswhat the journey triggers on

The catch

Flows keyed on order events welcome a subscriber again on every renewal, because nothing downstream distinguishes charge one from charge nine.

Where to check in AttentiveSending you can audit

Attentive the subscriber's timeline

where the event appears against the profile rather than as an unattached activity.

What changes

What changes when Skio feeds Attentive. Two gains on the Attentive side, two on the Skio side.

Attentive

Server-side delivery

Events reach Attentive through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

Attentive

Identity-resolved events

Events sent to Attentive 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, Attentive included, is forwarded the same resolved events.

Upstack dashboardExample

Skio Data source Connected

Attentive Destination Healthy

Read the full Attentive 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 Attentive destination

Under Destinations, add Attentive. Every resolved Skio event is then forwarded to it.
03

Check delivery to Attentive

Trace any event to the profile it resolved to, and see why.