Home
Connectors
Loop Subscriptions - Postscript

Postscript

Send every Loop Subscriptions event to Postscript, server-side

Q: How do I check that Loop Subscriptions events are reaching Postscript?

Open Postscript › Subscribers › the individual subscriber's activity feed.

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 Loop Subscriptions to Postscript?

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

Each event is resolved to a person against a 750M+ device graph before it reaches Postscript, 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 Loop Subscriptions event reaches Postscript. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Loop Subscriptions

Capture Loop Subscriptions events server-side (new subscriptions, renewals, swaps and cancellations), each as what it actually is.

See the Loop Subscriptions integration

Loop SubscriptionsWhat it sends

subscription_idthe Loop subscription across its whole life
email / phonesubscriber contact
event_typerenewal, swap, skip, pause, cancel or save
line_itemsproducts after any swap
total / intervalcharge amount and billing cadence

02 Understand

Resolved to one person before it leaves

Every Loop Subscriptions 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 Postscript

Send identity-resolved events to Postscript so SMS flows reach subscribers the pixel missed.

See the Postscript integration

PostscriptWhat it receives

phonesubscriber key
emailprofile matching
order / cart propertiesautomation triggers

The catch

A save (a customer offered a discount instead of canceling) is the highest-signal retention event there is, and it is invisible to any flow triggered on orders alone.

Where to check in PostscriptSending you can audit

Postscript Subscribers the individual subscriber's activity feed

What changes

What changes when Loop Subscriptions feeds Postscript. Two gains on the Postscript side, two on the Loop Subscriptions side.

Postscript

Server-side delivery

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

Postscript

Identity-resolved events

Events sent to Postscript carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

Loop Subscriptions

Every event, server-side

Storefront and checkout events are captured from Loop Subscriptions on the server, independent of the browser.

Loop Subscriptions

One setup, every destination

Connect Loop Subscriptions once and forward to every ad platform, email tool and warehouse you run.

Setup

Live in under 20 minutes.

Connect Loop Subscriptions once and every destination, Postscript included, is forwarded the same resolved events.

Upstack dashboardExample

Loop Subscriptions Data source Connected

Postscript Destination Healthy

Read the full Postscript setup guide

01

Connect Loop Subscriptions

Capture Loop Subscriptions events server-side (new subscriptions, renewals, swaps and cancellations), each as what it actually is.
02

Add the Postscript destination

Under Destinations, add Postscript. Every resolved Loop Subscriptions event is then forwarded to it.
03

Check delivery to Postscript

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

FAQ

Questions about Loop Subscriptions and Postscript.

How do I check that Loop Subscriptions events are reaching Postscript?

Open Postscript › Subscribers › the individual subscriber's activity feed.

Can one purchase trigger the same flow twice?

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

How long does it take to connect Loop Subscriptions to Postscript?

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