How to Setup Postscript Flows and Analyze Performance

First, learn about your potential

Using server-side tracking in conjunction with your existing client side Postscript tracking will allow you to collect additional information with our identity solution and session enrichment.

You can expect to improve your abandonment flows & identify abandoners that your client-side tracking misses due to cookie limitations!

This blog article is focused on Klaviyo, but the concepts and wins can be applied to your postscript flows to observe improved performance and unlock this secret weapon!

Next, set up you Postscript server-side destination

How to Set Up Elevar's Postscript Server-Side Integration

Events elevar sends

Once you've set up your Postscript Side Tracking, you'll be sending the following server-side events to Postscript:

Event Name Elevar Sends	Equivalent Postscript Event
Elevar - elevar_add_to_cart	Product Added to Cart
Elevar - elevar_begin_checkout	Checkout Started
Elevar - elevar_view_item	Subscriber Viewed Product
Elevar - elevar_page_view	There is no Postscript equivalent. This allows you to do site abandonment campaigns.
Elevar - elevar_view_item_list	There is no Postscript equivalent. This allows you to do collection abandonment campaigns.
Elevar - elevar_purchase	Order Created

Then, set up your abandonment automations

To calculate the ROI of the net new identified cart abandoners, we'll need to set up an Automation in Postscripts that sends messages to just that group of shoppers.

Clone your existing automation

Customize the name and trigger

Add "Elevar" to the name of the flow

Change the trigger so that it uses the Elevar server-side event as the trigger.

Add a cancellation trigger of the client-side event.

Add a Subscriber Filter to ensure users who are in the main client-side flow do not also enter the server-side flow.

Customize the message copy

Review the message copy & see if there are any invalid dynamic inputs, as shown below:

Use the Merge Tags button to see what dynamic inputs are available based on the trigger of the Automation.

If you're passing a dynamic Product Name value, try using the Producttitle or Varianttitle. If you're passing a dynamic checkout URL, try inputting a standard cart URL (e.g. website.com/cart) or the EventlocationURL (the page the shopper was on when they triggered the event).

Your end result will look something like this:

Activate the Automation

Finally, analyze the performance

Send messages to only the net new abandoners identified by Elevar so that you can see the net new revenue generated.

How to Calculate Additional Revenue from Postscript Server-Side Tracking