Skip to main content
Request a demo
  1. Home
  2. Integrations
  3. Postscript
Upstack Data

Postscript integration: server-side events resolved to a known profile

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

Request a demo Start free trial
Role
Destination
Category
Email & SMS
Pre-built connectors
12 sources
Plans
All plans

What Upstack sends

Every event reaches Postscript attached to a profile. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources
  • order_idShopify order and checkout token
  • email / phonecustomer contact from checkout
  • customer_idShopify customer record, if they have one
  • line_itemsproducts, variants and quantities
  • total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

Upstack DataResolved 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.
Out: to PostscriptOn every event
  • phonesubscriber key
  • emailprofile matching
  • order / cart propertiesautomation triggers

SMS flows reach subscribers the pixel missed.

See the set-up reference See all 12 sources How resolution works

About Postscript

Postscript sees what Shopify sees.

Upstack widens that: sessions that never reached checkout are resolved to known subscribers, so abandonment and browse automations reach people Shopify could not identify. Orders arrive server-side, so automations are not waiting on a browser event that may never fire.

What Postscript is

Postscript is an SMS marketing platform built specifically for Shopify brands, covering campaigns, automations and subscriber growth.

Its automations fire on storefront and checkout behavior, which means they only reach the subscribers whose behavior actually made it through.

How Postscript works

Postscript is built specifically for Shopify, syncing orders, customers and products directly from the store. Subscribers are keyed on phone number. Automations trigger on storefront and checkout behavior (abandoned checkout, post-purchase, win-back) and evaluate conditions against the subscriber and their order history. Because it reads Shopify directly, its view of a customer is as complete as Shopify’s own.

What you can do with it

Three jobs this connector does inside Postscript.

01

Send complete conversions

Conversions reach Postscript through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

02

Optimize on the customer you want

Map any order attribute to the conversion Postscript receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

03

Automations that reach the subscriber

Storefront and checkout behavior arrives tied to a known subscriber, so automations stop silently skipping the people they couldn’t identify.

Pre-built connectors

12 sources connect to Postscript. Whichever of these you run, Postscript is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for Postscript as a destination, next to the Postscript developer docs.

FAQ

Postscript integration questions.

What does Upstack send to Postscript?

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

How do I check that events are reaching Postscript?

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

Which plans include the Postscript integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which sources can send events to Postscript?

12 sources: Shopify, WooCommerce, BigCommerce, Checkout Champ, Recharge, Custom stack, Funnelish, Lasso Commerce, Phoenix Technologies, Skio, Loop Subscriptions and Stripe. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other destinations to send to.

See all integrations

Get Postscript tracking right.

A 15-minute walkthrough tailored to your stack and channels.

Request a demo Start free trial