Updated: 5 days ago
Alia Setup Guide: Klaviyo, Attentive, Postscript and Omnisend
By Trayan Hristov · Thrivelia · Published 15 November 2026

Alia should do more than collect an address. The popup promise, the saved customer data and the first email or text need to agree. A connection can look healthy while sending the wrong offer, starting two welcomes or losing people between email and SMS.
Still choosing the capture tool? Compare pop-up and quiz platforms. If you are deciding which tool should own each channel, use the email and SMS architecture guide, then apply the relevant setup path below.
This guide covers four common ecommerce setups: Alia with Klaviyo; Klaviyo email with Attentive SMS; Klaviyo email with Postscript SMS; and Omnisend. Start with the routing table, follow your stack's instructions, then run the launch tests. The advanced sections cover reward timing, quiz data and testing the commercial result.
The platform instructions below were checked against the linked official documentation on 15 November 2026. The worked scenarios and recommended checks are our implementation approach, not claims that every account has the same menus, permissions or configuration.
Decide which platform owns each channel
Stack | Email owner | SMS owner | First check |
|---|---|---|---|
Alia + Klaviyo | Klaviyo | Klaviyo, if used | Correct email and SMS lists selected |
Alia + Klaviyo + Attentive | Klaviyo | Attentive | API signup source and linked journey |
Alia + Klaviyo + Postscript | Klaviyo | Postscript | Keyword route or on-site opt-in route |
Alia + Omnisend | Omnisend | Omnisend, if used | Contact status and welcome setting |
This is the intended ownership model for each example. Confirm the actual subscriptions each integration creates. A hybrid stack can legitimately store an email in the SMS platform for identity matching; that must not accidentally launch another email welcome.
Prepare the accounts, an unpublished popup, the exact offer rules and test inboxes or phone numbers controlled by your team. Record the default route and any popup-level overrides. A promotional popup can have a different destination from the evergreen popup, so checking only the account connection is not enough.
Basic path A: Alia with Klaviyo
In Alia, open Integrations and connect Klaviyo. Check the account shown during authorisation. Select the destination email list and, if Klaviyo owns SMS, the SMS list. Save, then confirm any overrides in the individual popup. Alia's Klaviyo setup instructions explain that a blank channel list means that channel is not synced.
Match subscriber entry to the welcome flow's list. Review the list's opt-in process deliberately. Alia recommends single opt-in, but that recommendation does not replace your brand's chosen policy. With double opt-in, verify the confirmation and the later welcome entry rather than promising immediate marketing delivery.
If Attentive or Postscript owns SMS, leave Klaviyo's SMS subscription route unused. Do not enable multiple SMS marketing destinations simply because they are available. Email permission and SMS permission are separate choices, and a phone number saved for identity matching is not the same thing as permission to send through every platform.
Before changing anything else, submit a fresh email and inspect its list, subscription status and welcome activity. Repeat with email only, skipping the phone step. The shopper must still get the email experience you promised.
Basic path B: Klaviyo email with Attentive SMS
Set up the Klaviyo email route first. For Attentive, ask its support team for an API signup source and specify the intended welcome journey. A signup unit intended only for Attentive's own popup is not the same thing.
In Alia's Integrations page, connect the correct Attentive account and enter that signup source ID. Keep single opt-in disabled unless Attentive has approved it. Inspect the popup's Attentive override as well as the account default. The official Attentive connection guide documents this route.
For a confirmation-based SMS experience, the success step should tell the shopper to check their texts and complete confirmation. Verify that the journey sends after the actual subscription is complete. Keep the email offer and SMS offer consistent with what each step promised.
The same guide notes that Alia can send both email and phone information to Attentive and can connect more than one Attentive account. Audit which journeys and subscriptions that creates. In a multi-country setup, test the target account and recipient country explicitly; a successful US test does not establish that a Canadian or UK number is routed correctly.
If the wrong welcome appears, inspect the signup source, journey status and popup override before rewriting the message. Do not fix a routing problem by making several different journeys look identical.
Basic path C: Klaviyo email with Postscript SMS
Create a security key pair in Postscript and use its private key in Alia's Postscript integration. Choose the keyword required by the connection. Keep the key in the integration settings, not in a campaign brief or customer-facing code. The Postscript connection instructions distinguish this private key from the public key.
Next choose the actual signup method. A keyword-based route and Postscript Onsite Opt-In, or OOI, are different builds. Do not assume a keyword-selected welcome will still work after switching the popup to OOI.
For OOI, Alia's setup guide places the verification step between phone collection and code display. Enable OOI on each applicable phone step and configure its first welcome text in Alia. Review existing keyword or Reply-Y conditions because OOI subscribers are attributed to a different acquisition route. Use the documented Alia attributes when distinguishing those subscribers.
Keep the provider's required consent text visible on the phone step and complete its review process. Test new and already-subscribed numbers, successful verification and abandonment before verification. Inspect the actual text delivered, not only the popup preview.
If the OOI welcome already delivers the code, decide what the next Postscript automation should add. Sending the same first text again through another flow is a coordination problem, even when both messages are technically configured correctly.
Basic path D: Alia with Omnisend
In Omnisend's Apps area, find Alia and obtain the integration key. Connect Omnisend in Alia, paste that key and save. Review the integration's welcome-email option. Omnisend's Alia guide describes both the connection and follow-up automation routes.
Inspect the resulting contact's email and SMS statuses separately. Alia's Omnisend data guide documents its source tag, popup/campaign properties and reward-related events. Use the actual profile and event names present in your account when configuring segments and workflows.
Choose one general welcome route. If you add a reward-event workflow to deliver a specific offer, decide whether that replaces part of the general welcome or serves a separate purpose. A contact appearing in Omnisend does not prove that the intended workflow admitted them or that a code was available at send time.
Do not copy Klaviyo's list-trigger instructions into Omnisend. The platforms have different subscriber and automation controls. Test the chosen Omnisend trigger, contact eligibility and message status directly.
Advanced: make the reward available before the email needs it
Consider a hypothetical two-step popup. The shopper submits email, receives an immediate welcome and closes the popup before reaching the reward step. If the reward code is only saved later, the welcome can arrive with an empty code.
Alia documents this timing issue in its Klaviyo property guide. Inspect when the reward property is written, then either save the required reward at form submission or deliberately sequence fulfilment after it is available. Test the abandon-after-email route, not only the perfect completion route.
For Klaviyo, the documented code property is alia_offer. In the editor, insert the actual property using the platform's personalisation controls and preview it with a test profile. Choose a fallback intentionally. Do not invent a static discount code that the store has never created or approved.
When a code is missing, useful recovery may be a support route or a tested delay and recheck. Silently displaying a larger universal discount can change the economics of every failed transfer. Check minimum spend, exclusions, expiry, currency and whether the destination link applies the intended code. Do not assume a link that looks plausible in a preview works through checkout.
The property names differ by destination. For example, Postscript's data guide documents its own reward attributes, while Omnisend documents event and profile values separately. Maintain a destination-specific mapping instead of reusing a Klaviyo merge tag everywhere.
Advanced: use quiz answers as a decision, with an unknown route
Ask one question that changes what you can recommend. A beauty brand might ask whether the shopper wants help choosing a first routine or replenishing an existing product. A footwear brand might ask about fit. Avoid questions that have no consequence in the welcome.
Write the allowed answers, the property or event used and the fallback before building the split. Alia's Klaviyo synced-properties reference explains that quiz answers and reward data can arrive at different points. A missing answer should enter useful general guidance, rather than be guessed from another customer's behaviour.
For a hypothetical beauty build, a beginner sees a three-step routine explanation; a replenisher sees product selection and subscription-management help; an unknown contact sees a category chooser. Use approved product guidance. A preference answer is not a medical diagnosis.
Keep an acquisition snapshot separate from the latest preference where your reporting needs both. A customer can change their answer later. If the current profile value overwrites the old one, do not interpret today's preference as proof of what they selected during the original experiment.
Prevent duplicate forms and duplicate welcomes
Assign ownership of each on-site prompt. Remove or retarget overlapping collection popups after the replacement works, while keeping the tracking needed by the rest of the account. An email popup and an SMS popup should not fight for the same screen.
Also inspect the Shopify-to-email-platform path. Alia's duplicate-welcome diagnostic shows how one signup can reach separate Klaviyo lists through Alia and Shopify, activating both welcomes. Align the routes or use deliberate exclusions. Test an existing subscriber too: the requested offer still needs fulfilment even if the general welcome does not restart.
The launch acceptance test
Test identity or action | Expected observation | Stop launch if |
|---|---|---|
New email, skip phone | Email route works independently | Email promise requires an unintended SMS signup |
Complete both steps | Correct channel statuses and first messages | Duplicate or conflicting offers arrive |
Leave after email | Reward handling matches the promise | Email contains an empty or wrong code |
Already subscribed | Deliberate fulfilment without duplicate welcome | Existing customer receives an unintended new-customer sequence |
Decline or abandon confirmation | Incomplete state stays incomplete | Marketing begins without the required subscription |
Different market | Correct account, destination and offer | Number or currency is routed to the wrong market |
Mobile with keyboard open | Close, skip and submit controls work | Shopper cannot dismiss or complete the popup |
Save the actual profile, event and recipient-activity evidence for the test. Check the live storefront after release; a preview cannot prove theme targeting, conflicting popups or production sync.
Optimise for customer contribution, not only submissions
Keep email submissions, SMS submissions, confirmed new subscribers and purchases separate. Returning subscribers can submit again without representing new list growth. A higher email-plus-SMS total can count one person twice.
For a controlled offer experiment, assign visitors consistently, keep surrounding treatment comparable and compare retained order contribution per eligible visitor over a stated period. Include discounts, returns, fulfilment and channel costs. Do not switch to judging only subscribers after randomisation if the treatment itself changes who subscribes.
Use the Hiro setup guide to connect popup reporting and reconcile definitions. Then review the complete monthly email programme so the list-growth work has a useful next journey.
Thrivelia can scope the offer, integration, welcome creative and release checks together. Apply to work with us with the current stack and one signup you cannot explain.
Questions before connecting
Can Alia connect to Klaviyo and a separate SMS platform?
Yes. Define the intended owner of email and SMS, configure each connection and verify the actual subscriptions and journeys. Storing a contact in two platforms should not produce two unplanned welcome programmes.
Should I turn off double opt-in to improve the signup rate?
Choose the opt-in process deliberately for your programme and markets. A platform recommendation or a lower completion rate is not a sufficient reason to bypass your subscription requirements. Make confirmation understandable and measure confirmed subscribers separately.
Why does the first email have no Alia discount code?
The email may send before the reward property exists, or the shopper may leave before the reward step. Inspect the actual profile and event sequence, configure the reward handoff and test the fallback through checkout.

.png)
Comments