Treat Flow Forms as Eligibility Windows, Not Sent Messages

An email can invite a customer back to a site, but a form placed in a Klaviyo flow is not delivered when the flow reaches that step. The step makes an identified profile eligible to see the form on a later website or app session, subject to targeting rules, a live status, priority, and an expiration window. If Migma supplies the email creative and Klaviyo owns the journey, design the promise in Migma around a possible return visit rather than a guaranteed on-page form.

Marketing Wiki was commissioned by a Migma maintainer. This guide was prepared by Marketing Wiki Research Automation for direct publication without an independent reviewer. The platform behavior below comes from official documentation; the example and test matrix are editorial guidance.

What changed in September#

Klaviyo listed Forms in Flows on September 23, 2026. Its implementation guide says the feature is in Preview and appears only after Klaviyo adds the account. The guide, updated September 15, explains the mechanics more precisely than the release card: a web form requires Klaviyo's onsite JavaScript; an in-app form requires the mobile SDK and push setup. Reaching the Form step creates eligibility, then the form can display on the next qualifying session. The flow advances immediately rather than waiting for the form to display or expire.

That distinction changes the email brief. Suppose a fictional apparel store wants to ask recent buyers about fit preferences before a new collection launch. Migma can prepare an editable on-brand email that invites them to explore the new collection. The email may be exported for use in Klaviyo, with the approved HTML and destination preview checked before sending. The email should not promise “complete the form when you click” unless the landing experience actually guarantees that. In Klaviyo's documented flow model, eligibility alone does not guarantee display on the same session, the next page, or at all.

Model the visit and the flow separately#

Use two clocks. The flow clock begins when the profile reaches the Form step. The visit clock starts only when the identified profile opens a qualifying site or app session. The form expiration window constrains the first clock; site/app identification, targeting, display priority, and the live status determine whether a visit produces an impression.

This state table is an interpretation of the official behavior, not a claim that Migma or Klaviyo automatically builds this report. Klaviyo's guide says eligibility ends after a view, expiration, or returning the step to Draft. If several forms are eligible, display priority decides which is shown; equal-priority order is random. A profile that re-enters the same flow between sessions sees only the most recently triggered version.

Write the email for the actual destination#

In Migma, brief the email with the customer moment, verified collection facts, desired action, and destination URL. Keep the call to action truthful even if the Klaviyo form never displays: “Explore the new collection and share your fit preferences if asked” is a safer specification than promising a guaranteed questionnaire. The exact published copy should still be approved by the brand and legal owners; this sentence is a synthetic example, not a compliance rule.

Use Migma's Email Preflight and a test send for the email itself. After exporting, open the Klaviyo result and check its subject, links, variables, sender, audience, and final render. Migma's email check cannot establish whether Klaviyo identifies a visitor, whether a flow form is live, or whether a competing form wins priority. Give those checks to the journey owner.

Rehearse six outcomes before launch#

Use synthetic test profiles and an unsent or controlled flow. Capture the profile ID, Form-step timestamp, expiration setting, session start, form status, priority, view event, and submission event. Run these cases: a qualifying next session; no return before expiry; form step left in Draft; higher-priority competing form; re-entry before the next session; and a profile merge. Klaviyo documents that a merge can reset eligibility on the destination profile, so the merge case deserves its own record.

Review reports with the right denominator. Eligible profiles are not the same as visitors, viewers, or submitters. Klaviyo documents profile-level viewed, clicked, submitted, and completed events; the last two require an identified profile. A marketer should not blame the Migma-produced email for a low form-submission count until the team has checked clicks, return sessions, eligibility, impressions, and form visibility separately.

Start by confirming Preview access, then run the state table with one test flow and one Migma email draft. Keep the form step in Draft until its display and consent paths have been reviewed. No live Migma or Klaviyo account was operated for this article, and no conversion outcome is claimed.