Why is my Klaviyo list missing from the Alia picker?

Alia says the picker initially shows ten options. Search the exact list name and confirm that the authorized Klaviyo account is correct.

Why are email signups syncing but phone numbers are not?

The documentation requires a selected destination for each channel. Check the SMS list assignment; selecting an email list alone does not enable phone-number syncing.

Which Klaviyo property identifies an Alia campaign?

Alia documents alia_campaign for the campaign name. Inspect the value on a test profile before using it in flow conditions or segmentation.

How to connect Alia Popups with Klaviyo

This setup summary follows Alia’s Klaviyo documentation, checked 5 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 Klaviyo 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

In Alia’s Integrations area, choose Klaviyo and start the connection.
Confirm the Klaviyo account before approving authorization.
Select the destination list for each channel you collect, then save. The documentation says a channel without a selected list will not sync.
Check that the welcome flow listens to the same destination list.

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.

If the subscriber arrives but no welcome email is sent, inspect the flow entry condition and the contact’s consent state. Keep the list’s opt-in policy consistent with your intended consent process; do not change it just to make a test email arrive.

Troubleshoot the point where the journey stops

Symptom	First check	What to record
Destination list is missing in Alia	Search its exact Klaviyo name; the documented picker initially shows only ten options	Account and intended list name
Email arrives but phone number does not	Check that the SMS destination is selected as well as the email destination	Channel tested and selected destination
Contact exists in another list	Check the campaign's effective destination and any popup-specific override	Campaign, market and actual list
Contact reaches the list but no welcome message arrives	Inspect the flow trigger, eligibility and consent or confirmation state	Test time and the point where entry stopped
Two welcome messages arrive	Check overlapping forms and automations	Both sending flows and their entry conditions

These checks help isolate the failure; they do not establish a guaranteed delivery time. Avoid repeating submissions indefinitely before inspecting the existing profile, because previous subscriptions can complicate the next test.

Document the expected result for each channel

Use a small acceptance checklist rather than treating a green connection indicator as completion:

The destination account and list are the ones approved for this campaign.
The test contact appears with the expected channel and consent state.
Any campaign property needed for segmentation has the expected value.
The welcome flow admits the contact under its intended rules.
The received message and offer match the campaign that collected the contact.

Repeat the checks for each market or popup with a different destination. A successful test of the default account does not verify an override. Keep test addresses you control separate from customer records in your notes and include the timestamp and campaign name when reporting a problem.

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.