Skip to main content

Postscript Integration - Implementation Guide

This guide walks through how to connect Brij with Postscript so that phone numbers collected through Brij experiences are synced to Postscript in real time.

Once enabled, the integration will:

  • Create a subscriber in Postscript when a user submits a phone number with SMS marketing consent through a Brij experience
  • Send an opt-out signal to Postscript when a user text messages "stop" to any Brij Rebate campaign

This is especially useful for rebate campaigns and other phone-number-driven experiences. For example:

  1. A user starts a rebate campaign in Brij
  2. Brij collects their phone number and sends follow-up SMS messages (e.g., proof of purchase requests)
  3. That phone number is sent to Postscript as a new subscriber
  4. If the user later opts out of SMS in Brij, that opt-out is also sent to Postscript

Prerequisites

Before starting, make sure you have the following:

  • A Postscript account with permission to create or view API keys
  • At least one active Brij experience that collects phone numbers w/ marketing consent (rebate experiences and/or registration experiences)

Step 1 - Set Up SMS Marketing Consent Language

Postscript requires that your SMS Marketing consent language in Brij matches their verbiage exactly. See the link below for the exact language to use, but ensure the Terms and Privacy links are still active and pointing to the Brij privacy page

https://help.postscript.io/en/articles/13564345-what-is-the-tcpa-approved-compliance-language-i-need-to-use-when-collecting-subscribers

Step 2 - Generate a Postscript API Key

A Brand team member needs to generate the API key, unless access to their Postscript account has been given to a Brij team member.

Here's where to grab an API key from Postscript:

  1. Log in to Postscript
  2. Go to Account Settings
  3. Click API
  4. On the API page, click Create Security Key Pair in the upper-right corner
  5. Create a new key labeled for Brij
  6. Copy the private key

Step 3 - Setup the integration in Brij

Create a new Automation

  1. Go to the Automations page in Brij here: https://v2.brij.it/brand/automations
  2. Click the "New Automation" button
  3. Choose the Postscript icon and enter a name for it, then click Save & Next
  4. Authentication
    1. Click the Authentication dropdown and either choose an existing Postscript auth from a previous automation, or click "New Authentication"
    2. Select apiKey as the type of authentication
    3. Enter a name for the authentication (in case you make multiple keys) and paste in your API Key from Postscript. Click "Save & Next".
  5. Action
    1. Click Next (no action needed on this step).
  6. Filters
    1. Filters are used if only certain experiences or modules should create subscribers in Postscript. If an experience or event doesn't have any SMS consent to begin with, nothing will happen, so it's ok to leave everything turned on if you want all possible consented subscribers sent to postscript from any experience.
      1. The primary use case for filtering experiences is if you want to create separate automations so each experience or group of experiences create profiles with different keywords or tags in Postscript. More on this in a later step
      2. If you want to filter experiences, select the relevant Brij experiences that collect phone numbers. If the experiences share a common registration module, you can simply select the module and leave all experiences turned on.
  7. Triggers
    1. Triggers are used if you only want to send certain events to postscript to create subscribers. If an event trigger never happens in your account, like rebates, it's ok to leave this on and nothing will happen. Most brands leave them all on so all possible consented subscribers are sent to Postscript from any event.
      1. Rebate Initiation — captures phone numbers for subscriber creation
      2. Registration Submission — captures phone numbers for subscriber creation
      3. SMS Opt-Out — ensures rebate opt-out actions in Brij are reflected in Postscript
      4. These are the only events that collect phone numbers or handle opt-outs, so all three should be selected.
  8. Configuration - enter the following three fields as desired.
    1. Postscript Keyword - This is found in Postscript under Acquisition → Keywords as shown in screenshot below. The keyword tracks where the subscriber signed up from and triggers automated actions like sending a welcome SMS or applying a coupon.
    2. Subscriber Tags - enter "brij" without quotes, as it's the only way to group and find all Brij created profiles in Postscript. 
    3. Subscribe Origin - enter "other" without quotes, which means the subscriber was created from an external source
      1. the alternate option you may enter is "website" which means the subscriber came from a web form. This distinction is decided by the brand and may be relevant if the brij experience is embedded on the brand's website. Most often "other" is used. 
    4. Example of everything filled out on the Brij configuration page:
  9. On the final Configuration page, click "Save & Activate" to make this integration live. You're now sending profiles to Postscript!

What to expect after activation

Once the automation is live:

  • Brij will begin sending phone numbers from the selected experiences to Postscript
  • Eligible users will be created as subscribers in Postscript and EVERY profile created in Postscript will automatically get a text message sent to them asking to confirm their subscription by replying "Y".
  • SMS opt-out events from Brij will be sent to Postscript so those users are unsubscribed from marketing

Subscriber creation and opt-out handling will happen automatically as users move through supported Brij flows.

Troubleshooting

Subscribers are not appearing in Postscript

  • Confirm the integration was installed successfully
  • Verify the Postscript private API key was pasted correctly during authentication
  • Make sure the selected Brij experiences actually collect phone numbers
  • Confirm the correct trigger events were selected in the automation

Opt-outs are not syncing to Postscript

  • Make sure the SMS Opt-Out event is included in the Brij automation triggers

The wrong experiences were included

  • Review the Filters step and make sure only phone-number-based experiences are selected
Updated

Was this article helpful?

0 out of 0 found this helpful

Related articles