Home
Connectors
Skio - Yotpo

Skio

Yotpo

Send every Skio event to Yotpo, server-side

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

Open Yotpo › Reviews › the request queue, which should now contain the orders that previously had no email attached.

Q: Will a customer be asked twice about one order?

No. One purchase, one request, even when the order is amended.

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

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

Each event is resolved to a person against a 750M+ device graph before it reaches Yotpo, so every touchpoint lands against one customer, not a fragment of one.

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 Yotpo. 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 purchase, one request, even when the order is amended.
Bot and fraud filteringFraudulent orders never enter the request queue.

Post-purchase timing is the whole product. These controls exist so requests go to the right person at the right point.

03 Activate

Delivered to Yotpo

Enrich post-purchase touchpoints in Yotpo with identity-resolved order data.

See the Yotpo integration

YotpoWhat it receives

emailwho to ask for the review
order_idwhich purchase the request is about
product IDswhich product is being reviewed

The catch

Review requests fire on every charge unless the first is separated out, so a subscriber is asked to review the same product monthly.

Where to check in YotpoDelivery you can audit

Yotpo Reviews the request queue

which should now contain the orders that previously had no email attached.

What changes

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

Yotpo

Server-side delivery

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

Yotpo

Identity-resolved events

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

Upstack dashboardExample

Skio Data source Connected

Yotpo Destination Healthy

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

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

Check delivery to Yotpo

Trace any request back to the order and customer it came from.