---
title: Postscript integration
slug: postscript
description: How the Personizely Postscript integration works: API key connection, adding SMS subscribers to a keyword with tags, properties sent and consent.
docTags: 
createdAt: 2026-10-17T09:58:45.297Z
---

The Postscript integration adds visitors who give their phone number in a Personizely widget to your Postscript SMS list through a keyword, with customer tags and their profile data as subscriber properties. Postscript then runs the keyword's opt-in flow and your SMS automations.

**Available on:** all platforms; Postscript itself is built for Shopify stores. SMS only.

## Connect Postscript

1. In Postscript, create a private API key in your **API** settings.
2. In Personizely, go to **Settings → Integrations**, find **Postscript** (under **SMS**) and click **Connect**.
3. Paste the key in **API Key** and click **Connect**. Your Postscript keywords are loaded.

After creating a keyword in Postscript, click **Refresh** on the integration to see it.

## What's synced

| Personizely data                                               | Postscript subscriber      |
| -------------------------------------------------------------- | -------------------------- |
| Phone                                                          | Phone number               |
| Email                                                          | Email                      |
| Your tags                                                      | Customer tags              |
| Shopify customer, when the visitor is a known Shopify customer | Linked Shopify customer ID |
| Every other field with a value                                 | Subscriber property        |

Property names are the Personizely field name in lowercase with spaces and symbols replaced by underscores: "First name" becomes `first_name`, "Birthdate" becomes `birthdate`. The subscriber's origin is recorded as website.

## Automation actions

Add this under **Automation → Action in → Postscript**. It needs a phone number on the visitor's profile.

| Action                          | What it does                                                         | Options                                                |
| ------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------ |
| **Add subscriber with keyword** | Creates the subscriber through the keyword, with tags and properties | **Keyword**; **Customer tags** (default `Personizely`) |

Use separate keywords, or different tags, for different widgets to compare them in Postscript.

## Consent and compliance

- **Postscript runs the opt-in.** The keyword decides the compliance flow, such as the double opt-in confirmation text the subscriber must reply to. Personizely doesn't send any SMS.
- **Your form shows the terms.** Include the SMS consent language Postscript and your region require next to the Phone field, and an **SMS marketing consent** checkbox if you collect consent explicitly.
- **Phone format.** Personizely sends numbers in international format, such as `+14155550123`. Use the Form element's phone field, which formats numbers for you.

## Target filters

Postscript has no list filter in Personizely, and changes in Postscript aren't synced back. To avoid asking SMS subscribers again, target with the [Visitor fields filter](docId:8O0nDK0HiHXgMjILAg_OC) filter, for example "Phone is empty". See [Email list and tag filters](docId\:bDZFefAR-ceJy5XgJmNrv) for platforms that do sync lists.

## Gotchas

- **No phone, no subscriber.** The action is skipped when the profile has no phone number, for example on an email-only step. Put it on the step that collects the phone.
- **Existing subscribers.** If the number is already subscribed in Postscript, Postscript decides whether the keyword applies again; tags and properties may not be updated for existing subscribers.
- **No click-ID identification.** Postscript links don't identify visitors in Personizely.
- **Shopify customer link.** The Shopify customer ID is only sent when Personizely already knows the visitor as a Shopify customer, for example because they're logged in.

## Examples

- **Email then SMS:** step 1 runs your email platform's action; step 2 collects Phone with SMS terms and runs **Add subscriber with keyword** "WELCOME" with tag `popup`.
- **Exit-intent SMS offer:** an [Exit-intent trigger](docId\:lo2ZnWIQG9Ch3GYd5TUcM) popup with a Phone field → keyword "SAVE10", tag `exit-popup`.
- **Birthday club:** Form with Phone and Birthdate → keyword "BDAY". Postscript receives `birthdate` as a property for a birthday flow.

## Related

- [Email and SMS integrations](docId\:q8l96CeLAKMNxvuIxhl7v)
- [Integrations](docId\:YweYsNdyWfChY1Z9KMneN)
- [Attentive integration](docId\:On3u83jo7GYVk9D9eaJu4)
- [Form element](docId:_32XhaAm6KMwlL3_ZIH25)
- [Widget automations](docId\:J2UM-jhfDgQFopQlTvf_l)