Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Postscript Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Postscript in the Integrations object
  • This integration is partner owned. Please reach out to the partner's support for any issues.
  • This destination is in Beta

Postscript(link takes you to an external page) empowers ecommerce brands to drive incremental revenue through SMS marketing. With tools for subscriber growth, personalized messaging, and performance tracking, Postscript helps businesses engage their audience and boost conversions.

This integration enables you to sync your Segment Engage Audiences to Postscript, allowing you to target SMS marketing campaigns to specific customer segments. You can automatically update subscriber lists in Postscript based on audience membership changes in Segment, ensuring your SMS campaigns always reach the right customers. The integration supports syncing users identified by email address or phone number only.

This destination is maintained by Postscript. For any issues with the destination, contact their Support team.


Getting started

getting-started page anchor
  1. From your workspace's Destination catalog page(link takes you to an external page) search for Postscript.
  2. Select Postscript and click Add Destination.
  3. Select an existing Source to connect to Postscript (Actions).
  4. Go to the Postscript app(link takes you to an external page).
  5. Select your Shop name in the left sidebar, then select API.
  6. Select Create Security key Pair on the top right side of the page, then confirm your action by selecting Yes.
  7. Add a label of "Segment" to your API key so you can track where this API key is used.
  8. Select Show in the Private Key column to reveal your private key.
  9. Copy this private key and paste it into the Secret Key field in the Postscript destination settings in Segment.
  10. After completing the setup, configure the 'Sync Audiences' Action in your destination settings to begin syncing Audience data to Postscript.

Property nameTypeRequiredDescription
Secret Keypassword
required

Your Postscript API secret key


Build your own Mappings. Combine supported triggers with the following Postscript-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Sync Audiences

sync-audiences page anchor

Sync Engage Audiences to Postscript

Sync Audiences is a Cloud action. The default Trigger is type = "identify" or type = "track"

Property nameTypeRequiredDescription
Email addressSTRING

Optional

The user's email address. Required if phone is not provided.


PhoneSTRING

Optional

The user's phone number. Required if email is not provided.


Traits or properties objectOBJECT
required

A computed object for track and identify events. This field should not need to be edited.


You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo(link takes you to an external page).

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

(information)

Real-time to batch destination sync frequency

Real-time audience syncs to Postscript may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.


Segment lets you change these destination settings from the Segment app without having to touch any code.

Property nameTypeRequiredDescription
Secret Keypassword
required

Your Postscript API secret key