Setting Up Postscript Onsite Opt-In (OOI) with Alia
Alia integrates directly with Postscript Onsite Opt-In (OOI) to create a faster, higher-converting SMS signup experience — without sending shoppers off-site or requiring them to send a text message.
Instead of submitting a phone number and replying “Y” via SMS, shoppers receive a 4-digit verification code directly inside the popup. With a single tap, they’re opted in.
The result:
No keyword replies
No off-site friction
No compliance tradeoffs
Up to 3× more SMS subscribers
Part 1: Setting Up Onsite Opt-In
1. Enable the Postscript Integration
First, make sure your Postscript integration is enabled inside Alia.
You will still need to select a keyword during setup, but the keyword will not actually be used once OOI is enabled.
2. Open Your Popup Editor
Open the popup you want to configure and navigate to the Phone Submission step.
3. Enable Onsite Opt-In
Click on the SMS submit button inside your phone step.
Then navigate to:
Integration Settings → Postscript Settings → Enable “On-site opt in”
Important:
OOI is enabled per phone step, not globally across the popup
If your popup contains multiple phone collection steps, OOI must be enabled on each one individually
4. Set Your Welcome Message
Because OOI removes keywords from the signup flow, your welcome message is now configured directly inside Alia.
Inside the SMS submit button settings, you’ll see a Welcome Text field.
A typical welcome message looks like:
Thanks for subscribing! Here’s your coupon for discount_amount off: discount_code Shop here: link_to_apply_discount
You can dynamically insert:
Discount amount
Discount code
Discount link
using Alia’s expression variables.
Important:
Do not use the
{{ shop_name }}variable from Postscript templatesIf migrating from an existing keyword-based flow, do not copy the preview/mock phone link shown inside Postscript. Instead, use the brand’s actual homepage URL when configuring links
5. Add the Verification Step
OOI requires a verification step where shoppers enter their 4-digit code.
To add it:
Click the + Add Step button
Under Collection, select Verification
Place this step between:
the Phone step
and the View Code step
Your flow should look like:
Phone Step → Verification Step → View Code Step
6. Add a Branch for Existing Subscribers
If a shopper is already subscribed to SMS, they should skip the verification process entirely.
On the Phone step:
Click the SMS submit button
Under When form is submitted, add a branch:
If “Postscript user SMS already subscribed” → Go to “View Code” step
Part 2: Updating Your Postscript Flows
Keywords Are No Longer Used
With OOI enabled:
Keywords are completely removed from the opt-in process
Subscribers are instead attributed under:
Third-Party Onsite Opt-In
This means:
No Reply-Y flows
No keyword-triggered opt-ins
No keyword-based segmentation for Alia popup subscribers
Update Your Welcome Series & Automation Filters
If your current Postscript flows rely on:
keyword filters
popup keywords
Reply-Y logic
those filters must be updated.
What Needs to Change
Anywhere you currently use:
“Keyword most recently triggered”
Reply-Y conditions
Keyword-based popup segmentation
you should remove those filters.
If you still want to specifically segment or identify Alia popup subscribers, we recommend adding a custom property on email/SMS submission and using that property for automation filtering instead.
Part 3: Compliance Requirements
OOI introduces stricter compliance requirements that must be followed before publishing.
Required Compliance Rules
To remain compliant:
✅ SMS consent text must appear above the submit button
✅ Consent text must be clearly visible and sufficiently contrast against the background
✅ Consent text must be at least 10px in size
✅ Terms of Service and Privacy Policy links must:
Be bolded
Be UPPERCASE
Be underlined
Use a contrasting color from the surrounding consent text
Editing Compliance Styling
All compliance styling can be edited directly inside the Alia Popup Editor, including:
Consent text placement
Font size
Text color
Link styling
Terms & Privacy formatting
No custom code is required.
Part 4: Testing & Publishing
Test Your Popup
Before publishing:
Open the popup preview
Test the full OOI flow
Verify:
verification code functionality
existing subscriber logic
welcome message delivery
consent visibility
Publish or Mark as Ready
When publishing an OOI popup, Alia automatically runs compliance validations and screenshot checks.
This process includes:
Mobile & desktop screenshots
Consent visibility analysis
Compliance validation checks
Internal logging for audit purposes
If validation fails, you’ll be prompted to correct the issue before publishing.
Part 5: Additional Setup Notes
Enable Opt-In Tracking
To properly track net SMS opt-ins:
Navigate to:
Settings → Enable “Show opt-ins”
If the Postscript SDK Is Missing
OOI requires the Postscript SDK to be installed on your storefront.
If it is not installed, you may see an error message preventing OOI from functioning correctly.
You can install the SDK using Postscript’s developer documentation.
Message Analytics
Analytics for the OOI welcome message live inside Postscript:
Postscript → Data & Insights → Messages → Message Analytics
Here you can track:
Sends
Deliverability
Engagement
Revenue attribution
Summary
Postscript Onsite Opt-In with Alia delivers:
A faster SMS signup experience
Higher conversion rates (up to 3× more subscribers)
No keyword replies
No off-site friction
Fully compliant onsite verification flows
Once configured, everything can be managed directly inside Alia and Postscript without requiring manual setup assistance from the Alia team.