Tie recognizes returning shoppers across sessions and devices, and passes that recognition to Postscript as events your browse and cart abandonment automations can trigger on. Postscript is connected with help from your Tie onboarding contact. You give us access and create an API key, we finish the connection on our side, and the Tie events then appear in your Postscript automation builder.
You may see Postscript marked Coming soon in the Provider list on your Onboarding page. You don't need to select it there. Connecting Postscript runs alongside the rest of your setup and never holds up going live, and if you also use Klaviyo for email, connect it on the Onboarding page as usual.
Step 1. Give Tie access to Postscript
In Postscript, add [email protected] as a user with Admin or Marketer permissions. This lets your Tie onboarding contact finish the connection and help with setup if needed.
Step 2. Create a private API key
In the Postscript dashboard, select your Shop Name in the side menu, then select API.
Select Create Security Key Pair at the top right of the page, then confirm.
Add a label to the key so you can track its usage later.
Select Show in the Private Key column to reveal the key.
You need an Owner or Admin role in Postscript to see the API menu. If you can't see it, ask an admin on your team to create the key for you.
Step 3. Send the private key to your Tie contact
Copy the private key and send it to your Tie onboarding contact. Send the private key, not the public one.
Please send it as a single-use secret link rather than pasting it into a shared channel or a plain email. The link itself is safe to send over Slack or email. How to send Tie your credentials securely walks through the options, and if none of them works for you, ask your Tie contact.
Step 4. Find the Tie events in Postscript
Once your Tie contact confirms the connection, three Tie events are available as triggers in Postscript's automation builder. Each one fires when Tie recognizes a shopper on your site, including returning shoppers Postscript wouldn't match on its own. Postscript only texts shoppers who have opted in to your SMS list, so recognizing a shopper never messages anyone who hasn't subscribed.
Event | Description |
| Fires when a shopper views a page on your site. |
| Fires when a shopper views a product. |
| Fires when a shopper adds an item to their cart. |
To find them, create or open an automation and choose the event under Trigger event or property.
Step 5. Turn your existing flows into Tie automations
Duplicate your existing browse or cart abandonment flow rather than building a new one from scratch.
Consider giving the Tie version its own copy instead of reusing the original flow's copy word for word. It's a small change for the shopper, and it makes Tie-triggered messages easy to tell apart later in a subscriber's profile history.
Swap the trigger to the matching Tie event,
revroll_view_itemfor browse andrevroll_add_to_cartfor cart.
Set up filters and cancellations on every Tie automation
Filters and cancellation logic keep Tie automations from colliding with your existing flows and sending a shopper duplicate messages, including a message to someone who has already moved from viewing a product to their cart to checkout.
Compliance to know. Carriers require that abandoned cart and checkout automations be limited to one message, sent within 48 hours of the trigger event. This is a carrier requirement, not a Postscript or Tie policy, and it applies across every automation that touches the same shopper event, not per platform.
Configure these four settings on every Tie automation.
Subscriber filter. Exclude anyone already enrolled in another browse or cart abandonment flow. In Postscript, choose Currently in Automation Flow includes and select every flow that comes before Tie in your waterfall.
Entry filter. Cap how often a shopper can re-enter the flow. We recommend no more than once every 3 days for cart and checkout abandonment, or once every 5 days for browse abandonment if you prefer a more conservative approach.
Cancellation triggers. Tell Postscript when to remove a shopper from the flow, for example cancelling the cart automation once the shopper begins checkout.
Time delay. Match the delay in your non-Tie abandonment flows, and never go below 15 minutes. The floor is a safety margin in case something upstream doesn't fire as expected.
If you run other identification tools alongside Tie, reflect their events in the same filters, cancellation triggers and time delay. Where you can, place Tie first in your identification waterfall. Tie recognizes returning shoppers across sessions and devices in real time, so it typically fires earliest.
A few things to avoid:
Mixing cancellation logic across flows
Launching without a delay window configured
Letting Tie and non-Tie abandonment flows overlap
Personalize messages with merge tags
In the Postscript message editor, select Merge Tags, then Trigger Event Properties, to insert details about what the shopper was looking at and send them back to exactly where they left off.
Merge tag | Description |
Image Url | Product image link |
Item Id | Unique product identifier |
Item Name | Title of the product |
Page Url | Viewed page link |
Price | Cost of the product |
Product Url | Product page link |
Quantity | Number of items selected |
Check that your Tie automations are sending
In Postscript, go to Data & Insights, then Messages. Under Summary by Message Type, find your Tie automations to see Revenue per Message, Revenue per Order, Unsubscribe Rate and a built-in ROI column for each.
ROI here is total revenue from that message type divided by what it cost to send, which is the messaging cost plus carrier fees. The Total row at the bottom gives the same ratio across every message type. Postscript doesn't break carrier fees out per message, so treat ROI as a guide rather than an exact figure.
If a Tie automation looks quiet, widen the date range first, because the report starts with a recent window. If the report itself looks off, refresh the page, and check Postscript's SMS and MMS Analytics tab, which is hosted inside Postscript.
Use Tie's data in your campaigns (brands using Klaviyo for email)
Tie does more than trigger automations. Every matched shopper profile is enriched with demographic and behavioral context in Klaviyo, including Predict scores. Predict gives each identified shopper three daily scores from 0 to 10, for how likely they are to open, click and buy on their next send.
Postscript has a native Klaviyo integration that lets you use Klaviyo lists as segments in both campaigns and automations. Postscript's guide to using Klaviyo lists to segment subscribers covers the setup. Once it's on, Tie's attributes and Predict scores can power your Postscript campaigns too.
A few ways to use them:
Send campaigns to low-intent or high-intent shoppers based on their Predict purchase score, and A/B test copy, offers and incentives.
Launching a new product for women? Build a Klaviyo list from Tie's gender data.
Opening a retail store? Use Tie's geographic data to text shoppers in that area.
What happens next
Your Tie contact completes the Postscript connection on our side and lets you know when the Tie events are live in your automation builder. Connecting Postscript never holds up going live.