Updated: 7 days ago
ManyChat and Klaviyo Integration: Email Capture, Consent and Welcome Flows
By Trayan Hristov · Thrivelia · Updated 15 November 2026

The difficult part of a ManyChat and Klaviyo integration is usually the handoff. The address arrives, but the contact is not subscribed. Or the contact reaches a list that does not trigger the welcome flow. Or an existing subscriber is promised a new welcome email that will never arrive.
I would build this connection backwards from the expected customer experience. Decide what a new subscriber should receive, prove the subscription route, then connect the Instagram conversation. This walkthrough uses email capture for an ecommerce store. It is not an instruction to subscribe every person who enters your DMs.
For the social side, use the ManyChat Instagram setup guide. For the underlying store integration, start with our Shopify and Klaviyo setup. Platform instructions were checked on 15 November 2026.
1. Choose the subscription route before creating API keys
There are two practical starting points. Route A collects an address in ManyChat and uses its native Klaviyo action. Route B sends the person to a Klaviyo subscribe page, where they complete the email invitation and any confirmation. Pick one for the first release so you can explain and test every state.
The native connection can be convenient, but a contact record, list membership and email subscription status are different things. ManyChat's current Klaviyo integration guide describes a single-opt-in list setting as its fix for contacts arriving as “Never subscribed.” That does not make switching a main list to single opt-in the right decision for every brand.
If your programme requires double opt-in, keep that requirement. Use the hosted subscribe route and test the confirmation, or have a developer implement a supported subscription process. Do not overwrite an unsubscribe or suppression simply to make the test email send.
2. Prepare the list and one test welcome message
In Klaviyo, identify the list intended for new email subscribers and record its exact name and opt-in method. For an existing store, inspect the welcome flow that already uses it. Avoid creating a second general welcome flow that sends alongside the first.
If this is a new build, create a draft welcome flow and one branded message before connecting the form. The list used for subscriber entry must match the trigger. Keep broad sends paused while you test; a successful API connection is not permission to email the whole imported database.
Write the expected result in plain language: “A new subscriber from the FIT conversation confirms email, enters the main welcome flow and receives the promised fit resource.” That gives the implementer and reviewer the same acceptance test.
3. Connect the native integration
For Route A, open Klaviyo's account settings and its API keys area. Create a private key for this connection using the permissions specified in ManyChat's current instructions. Record the public key as well. In ManyChat, go to Settings, then Integrations, enter both keys and connect Klaviyo.
In the automation, add the action named Create or update a Contact in a list. Choose the saved email field and destination Klaviyo list, map the required fields, then save. The integration identifies an existing contact by email and can update mapped properties. These procedural details follow ManyChat's official connection guide.
Give the key a recognisable internal name. Keep it out of customer-facing messages, screenshots and shared briefs. Assign someone to investigate failed transfers and rotate access when ownership changes. A green connection indicator only establishes the account connection; the individual contact action still needs testing.
4. Define the field mapping before adding every available field
Use a small, documented mapping. For example, save the email in the actual email identity field; map first name only if you collected it; and create your own custom properties for the acquisition source, offer and relevant product preference. ManyChat distinguishes Klaviyo special properties from ordinary custom properties in its mapper. Follow that distinction rather than guessing field names.
Suggested custom properties for your own implementation are acquisition_source, acquisition_offer and preferred_fit. These are examples, not fields automatically created by either platform. Set their values deliberately and confirm that the same spelling reaches Klaviyo.
Decide whether each property records first acquisition or the latest interaction. If an existing subscriber asks for a new guide, overwriting their original source will distort acquisition reporting. Keep immutable first-source data separate from a latest-offer field if you need both.
5. Use a Klaviyo subscribe page when it is the clearer route
For Route B, create or review the subscribe page attached to the intended Klaviyo list. Put the brand, actual email promise, privacy link and expected confirmation on the page. Link to it from the appropriate point in the DM. Use source-tagged destination links for analysis.
The advantage is an easier-to-observe subscription experience: the shopper submits on the email platform's page and completes the list's confirmation process. Klaviyo documents the pages involved in its consent-page guide. Check the success page on a phone inside Instagram's browser, including the instruction to check email when confirmation is required.
This route does not automatically transfer every conversation answer. Decide whether the initial version needs only an email subscription and a tagged link. If product preferences must follow, specify and test that data transfer separately. Do not present campaign tags in a URL as if they were automatically saved profile properties.
6. Match the welcome email to what the person requested
A shopper who asked for fit help should recognise that help in the first email. Deliver the resource, explain how to use it and offer a relevant next step. A generic brand story can wait if it delays the promised answer.
Use an existing welcome flow with source-aware content where practical. Do not create an isolated list and duplicate flow for every reel merely to change the first paragraph. Keep the general routing understandable, then branch only where the experience needs to differ.
Klaviyo's welcome-series documentation notes that a list-triggered welcome flow is normally received once. An existing subscriber asking for another resource therefore needs a separately designed fulfilment route. Test it explicitly rather than expecting the general welcome series to restart.
7. Test six contact states
Use controlled test identities and inspect what actually happened. Test a brand-new address, an existing subscribed address, a previously unsubscribed address, invalid input, someone who declines email and someone who does not complete double opt-in.
For each case, record the message shown in Instagram, whether a profile was created or updated, list membership, email subscription status, saved properties and flow activity. Check delivery in the test inbox where a send is expected. A confirmation email is a different message from the welcome email.
For the unsubscribed test, verify that your process respects the chosen resubscription requirements. For the declined case, no marketing subscription should be created. Keep these results with the launch brief so a future tool change can be checked against the same expected behaviour.
8. Diagnose the first failed handoff
If no Klaviyo profile appears, check whether the person reached the integration action, whether the saved email field contains the value and whether the connection reports an error. If the profile exists but is not subscribed, investigate the subscription route and list settings before editing the welcome email.
If someone is subscribed but receives no welcome, inspect the destination list, trigger, message status, recipient activity and previous flow entry. Our welcome-flow troubleshooting guide walks through that diagnostic. A missing send can be correct, for example when the contact already received that list-triggered flow.
Advanced implementation: ordering, repeat requests and recovery
Once the native route is working, write a small data contract. It should explain the identifier, destination, required fields, subscription process and expected message for every entry point. The following is a proposed implementation specification, not a claim that ManyChat automatically creates all these fields.
Data item | Example rule | Acceptance check |
|---|---|---|
Email identity | Use the submitted validated address | Update the intended profile; do not merge different people by guesswork |
First acquisition | Preserve the initial source if already known | A later guide request does not replace it |
Latest request | Record the offer and request time | The fulfilment matches this request |
Preference | Use a documented allowed value | Unknown input gets an unknown route |
Subscription | Use the chosen supported opt-in process | Status and confirmation match the invitation |
Processing reference | Track the intended operation in a custom integration | Retrying does not repeat fulfilment indefinitely |
Make the required data arrive before branching on it
If your welcome branches on the offer or preference, test whether the native action has made those values available when the flow evaluates them. A connection that eventually updates the profile may still be too late for an immediate message.
Where a delay is appropriate, use a deliberate delay and a condition that checks the required field, followed by a useful fallback. Do not treat an arbitrary five-minute wait as proof the data always arrives. If the value is still absent, send accurate general guidance or route the case for repair. Do not send an empty personalisation tag.
For a custom integration, define write order and a processing reference, then implement retry handling on the system that owns the transfer. Do not put a private key in an Instagram message or browser page. Use the current supported platform subscription methods rather than treating a profile-property update as a consent event.
Design repeated resource requests separately
An existing subscriber may want a different resource next month. Model that as a new request with its own fulfilment, not as another first-time subscription. Decide whether a verified event-based journey or an immediate resource link is the better route. The general welcome should not become an unreliable delivery mechanism for every new guide.
Keep unsubscribe and channel preferences authoritative. Someone requesting one resource does not automatically agree to every previously declined channel. Test the intended resubscription route with controlled identities before release.
Give failures somewhere to go
A custom transfer needs an owner, a failure record and a safe replay procedure. Retry transient connection failures deliberately; investigate invalid identifiers, permissions or unsupported consent states rather than retrying them forever. Log only the information needed for diagnosis and keep access restricted.
Reconcile a daily sample from conversation completion to profile update, subscription, list entry and message delivery. For example, if 50 people complete capture but only 35 become confirmed new subscribers, classify the remaining 15 before calling them lost leads. They may be existing subscribers, incomplete confirmations, declined subscriptions or actual failures.
Add this connection to the monthly account review. If the platform or acquisition tool changes, replay the same acceptance cases. Advanced integration quality is the ability to explain and recover the imperfect path, as well as complete the happy path.
Judge the connection by confirmed new subscribers
Reconcile captured addresses against confirmed new subscribers and welcome recipients. Keep an error count and an owner for retries. Retries should update the intended contact, not create duplicate profiles or resend the same promise repeatedly.
Then compare first-purchase behaviour by acquisition source over a stated period. Keep the sample size and offer visible. A conversation that gathers fewer addresses but attracts shoppers who want the product can be more useful than a giveaway that fills the list with low-intent contacts.
Thrivelia can scope the offer, data mapping, welcome journey and launch QA together. Apply to work with us with your existing list, current welcome flow and a sample conversation so we can identify the actual handoff to fix.
Questions before launch
Does the native ManyChat integration automatically handle double opt-in?
Do not assume it does. Verify the current integration behaviour and the resulting Klaviyo status. If confirmation is required and the native action does not perform it as intended, use a tested Klaviyo subscribe-page route or a supported custom subscription process.
Can I use the same list as my website form?
Yes, provided the subscription route, source tracking and welcome experience are designed for it. Check that existing subscribers do not receive a duplicate general welcome and that the promised resource has a fulfilment route.
Should I send SMS because ManyChat collected a phone number?
No. A phone value alone does not establish an SMS subscription. Set up and verify that channel's permission and availability separately before including it in marketing flows.

.png)
Comments