Skip to main content
Skip table of contents

Integrating Malomo and Postscript

Est Time: 10-15 Minutes.

Getting Started:

The Malomo and Postscript integration offers Merchants a powerful avenue to deliver real-time automated SMS updates to their customers. The Postscript integration will deliver SMS updates to recipients with tracking updates and a link to the customer’s unique tracking page.

In order to make sure that your Postscript account can function properly with Malomo, please ensure both are connected to the same Shopify Account. For more information on how Postscript uses Automations, see here.

Before moving forward with setting up Automations - we recommend taking a look at our Malomo and Postscript Best Practices. 

Integration Setup:

Step 1: Create a Postscript private API key

In order to send data to your Postscript account, you will need to create a private API key to be used by the Malomo integration.

To create a Postscript private API key:
  1. Log in to your Postscript dashboard and navigate to API’s in the upper right hand corner.

  2. From the API screen, select Create Security Key Pair. You will see a new pair of API keys appear in the list below. The Private Key is the one you will need to provide to Malomo.

Step 2: Connect Malomo to your Postscript account

  1. Navigate to the Apps section and click on the Install button for the Postscript

  2. Once on this integration page, you will be able to copy and paste your API key from step 1. Do this and hit continue.

  • Authenticate this API key with your username and password. Upon authentication, this API key will be added and will connect your Postscript Account to Malomo.


Congratulations, you have successfully authenticated your Postscript Account with Malomo! If you see a status other than “Success!”, please email and our team will assist you.

Step 3: Review or Set your Default Tracking Page URL

Postscript uses the Default Tracking Page URL set in the Malomo Dashboard to share your live tracking page with your customer. To review this page, go to Malomo > Account > Overview and look for the Default Tracking Page URL section. If this section is blank, please add in the full URL of your live tracking page. If you have multiple live tracking pages, please select the page you would like to assign as the default tracking experience.

To learn more about setting or reviewing your default tracking page, check out this article.

Step 4: Setting up Automations between Malomo and Postscript

The Malomo and Postscript Integration rely on orders to be placed in order to function. Prior to setting up an Automation, ensure you either have new orders placed, or place a “fake” order yourself in the time between the integration being authenticated and automations being set up. 

  1. In your Postscript Dashboard, go to ‘Automations’ and click ‘Create Automation’. You will want to create a “Custom Automation”. 

  2. From there, you will want to give your Automation a name. We recommend naming conventions similar to the trigger you have chosen to initiate the automation.

    1. Please note, we do not recommend triggering a status off of InTransit, as the journey will trigger multiple texts to your customer. Our system receives the InTransit status on every scan event received between PreTransit and OutForDelivery.

  3. Once you have selected your triggers, you can determine the message properties that you want to be sent with your message. To link customers to your custom tracking page, we recommend using the { order_url} tag once you've set your Default Tracking Page URL. You can also build your tracking URL with the {order_id} tag, such as this:{order_id} 

  4. We also recommend using the {order_number} tag to give customers a reference point. 

  5. We recommend that you run through a few tests of your Integration to your own user prior to saving your work.

  6. We also recommend that you add “Reply STOP to unsubscribe” in your message and try to keep your text under 160 characters. 

  7. Once you are comfortable with your automation, hit save!

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.