How to connect Alia Popups with Postscript
This setup summary follows Alia’s Postscript documentation, rechecked 6 September 2026. It has not been tested in a live merchant account. Use the vendor article if the current interface differs.
What you need
Access to the correct Alia and Postscript accounts, a test contact you control and a clear decision about which channel and welcome flow you are connecting. Keep integration credentials in the vendor’s authorized connection screen.
Documented connection steps
- Create a security key pair from the API Keys area in Postscript.
- Use the private key for the Alia connection, as specified by the vendor guide.
- In Alia’s Integrations area, connect Postscript and supply the key.
- Select a keyword. Alia’s guide distinguishes the role of that keyword when Postscript Onsite Opt-In is enabled.
Verify the entire signup path
Submit a fresh test contact through the published popup. Confirm that the contact reaches the intended account, retains the expected consent state and enters the intended welcome sequence. Record the timestamp so you can distinguish the test from an earlier subscription.
Confirm whether your popup uses Onsite Opt-In before diagnosing where the subscriber should appear. If a contact exists but a message does not arrive, inspect the relevant consent and welcome-flow settings rather than repeatedly submitting the same number.
Identify which opt-in path you are testing
Alia's guide requires selecting a keyword to establish the connection. With Onsite Opt-In, that keyword is not the subscriber store; without it, the selected keyword is the documented destination. Record the popup's actual mode before searching for the test subscriber.
| Checkpoint | What to inspect |
|---|---|
| Connection approval | Correct Postscript account and private key, followed by keyword selection |
| Popup submission | The phone number you control and the actual opt-in path presented |
| Subscriber destination | Where the selected opt-in mode should place the subscriber |
| Welcome delivery | The contact's state and the relevant automation's entry requirements |
Update flow filters when using Onsite Opt-in
Postscript’s Alia setup guide, checked 6 September 2026, identifies a migration issue: flows using Keyword most recently triggered or Reply Y-specific entry logic need different filters for Onsite Opt-in.
| Flow type | Postscript’s documented filter |
|---|---|
| Welcome Series | Subscriber Opt-in Source equals 3rd Party Onsite Opt-in-Alia |
| Other Automation Flows | Custom Field alia_ooi equals true |
Review each affected flow rather than changing only the integration connection. Postscript warns that leaving the older filters can prevent entry or send subscribers into the wrong welcome path. Apply this guidance to the Onsite Opt-in workflow it describes; it is not a reason to replace every keyword-based flow in your account.
Our suggested acceptance check is to record the old filter, intended audience and expected message before editing. Afterward, use a controlled signup and inspect its source or field value and automation history. Also verify that an unrelated signup does not enter this Alia-specific path.
Troubleshoot without changing several settings at once
If the connection fails, confirm the key type and account before investigating the keyword. If submission succeeds but the subscriber is missing, record the popup mode, test time and expected destination. If the subscriber exists but a message is absent, investigate the follow-up workflow separately from authorization.
Keep a small test log with the campaign, opt-in mode, selected keyword and outcome. Mask the controlled phone number in shared screenshots and omit the private key. A precise report such as “submission accepted, subscriber found, welcome message absent” gives support a clearer starting point than “SMS is broken.”
Repeat the same controlled journey after a correction. Do not infer that every existing subscriber will re-enter a welcome flow from one fresh signup test. The article documents connecting and routing; message eligibility must be checked in the actual workflow.
Avoid duplicate welcome messages
Check whether another popup or signup form still feeds the same automation. Test one controlled path before changing the existing production form. A successful authorization screen does not establish that the downstream marketing workflow is correct.
See all Alia integrations, pricing and plan caveats and the official setup article.
Questions before you decide
Frequently asked questions
Should I use the public or private Postscript key?
Alia’s guide specifies the private key from the security key pair. Enter it only in the integration connection field.
Is a keyword still required with Postscript Onsite Opt-In?
Yes. The guide requires keyword selection to establish the connection, but says it is not the subscriber store when Onsite Opt-In is used.
Where do subscribers go without Onsite Opt-In?
Alia’s documentation identifies the selected keyword as the subscriber destination when the popup does not use Onsite Opt-In. Confirm the popup mode before troubleshooting routing.
Why can a Postscript flow stop after switching to Alia Onsite Opt-in?
The flow may still depend on its old keyword filter. Postscript documents replacement source and custom-field filters for Onsite Opt-in. Review the flow-type table above and verify the test subscriber’s automation history after changing the affected flow.