Create the working funnel.
Start from Funnels. A funnel is a merchant-controlled recommendation journey with its own identity, shopper steps, result configuration, visual presentation, and publication state.
Funnel title
The merchant name used in the builder and on the shopper-facing experience where shared title copy is enabled. The first successful publication derives the permanent shopper-link slug from this title; later title changes do not replace the published slug.
- Use it for: a clear internal and shopper-facing identity.
- Review before publish: title accuracy and its initial spelling.
Shopper description
Supporting funnel copy that can frame the purpose of the recommendation experience for the shopper.
- Use it for: the reason to begin the journey.
- Review before publish: product and outcome claims.
Draft or Publish
Drafts can be saved while content, products, and plans are incomplete. Publishing is a stronger state: every recommendation plan requires at least one plan feature before Flow will allow a public shopper link.
- Draft: private work in progress; no shopper link.
- Publish: creates or refreshes the customer-facing funnel.
Variant A / Variant B
The workspace includes a selector for working between variant labels. Keep the selected variant and its surrounding configuration aligned with the test or comparison you intend to run.
- Use it for: controlled merchant iteration.
- Review before publish: the active version and all customer-facing copy.
Builder Preview
Preview opens the Flow-hosted working experience. It is intentionally separate from the public shopper URL used after publication.
- Use it for: review before sharing.
- Do not share it as: the merchant-domain funnel link.
Arrange the shopper journey.
The Flow journey is ordered: an optional Intro, any number of shopper steps, and one mandatory Result reveal. Shopper steps can be reordered by drag-and-drop; the Result reveal remains the final destination.
Optional Intro
The Intro is the entry screen before the first question. It supports an introduction without forcing every funnel into the same opening structure.
- Title and supporting copy: explain the journey.
- Begin button text: name the first action.
- Consent sentence and policy links: provide merchant-approved notice before the journey starts.
Shopper steps
Every added step sits between the Intro and Result reveal. Drag and drop changes the order. Each step has its own type-specific fields, response handling, and optional next-step rule where supported.
- Use it for: collecting only information that changes the recommendation or provides needed checkout context.
- Review before publish: question order, required states, and all answer labels.
Mandatory Result reveal
The Result reveal is the final recommendation screen. It is not removable because it is the required end point for the shopper journey.
- Contains: display type, plan layout, plan tiers, product mappings, and any supported offer configuration.
- Publication guard: every visible plan needs at least one clear feature.
Shared question language
Question title, helper text, question label, and Continue text are configured with the corresponding step. The shopper sees those settings in the chosen presentation layer.
- Use it for: concise prompts that can be answered without interpretation.
- Review before publish: required language and button text for the actual action.
Choose the response control that fits the decision.
Flow supports distinct step types rather than making every decision a generic form field. Use the smallest useful question, not the largest possible questionnaire.
Single choice
Present a defined set of answer choices. The question can be required. With shopper auto-advance enabled, a single selected answer can move the shopper forward without a Continue click.
Fields: question copy, answer choices, required state, question label, Continue text, optional answer-routing rule.
Multi-select
Allow more than one selected option. The shopper continues manually after making selections.
Fields: question copy, answer choices, question label, Continue text, optional answer-routing rule.
Image choice
Use a visual answer grid where an image carries meaning the text alone cannot. Choice images can be uploaded after the funnel is saved as a draft, or referenced with a secure image URL.
Fields: answer label, PNG/JPEG/WebP choice image up to 1 MB, secure image URL, question copy, required state, question label, Continue text, optional answer-routing rule.
Slider
Collect a position on a defined numeric range.
Fields: minimum, maximum, default value, question copy, question label, Continue text.
Text input
Collect a merchant-defined text response. Use checkout mapping only when the answer has a legitimate cart or customer context.
Fields: required state, Continue text, checkout field label, no mapping / cart attribute / cart note mapping.
Rating
Collect a five-point rating response.
Fields: question copy and the fixed five-point scale.
Yes / no
Provide the built-in Yes and No choices for a binary decision.
Fields: question copy, built-in Yes/No choices, question label, Continue text, optional answer-routing rule.
Date picker
Collect a date when it matters to the merchant’s recommendation context or cart record.
Fields: required state, Continue text, checkout field label, no mapping / cart attribute / cart note mapping.
Agreement scale
Collect a five-point strongly-disagree to strongly-agree response.
Fields: question copy and the fixed agreement scale.
Email capture
Collect an email only where the merchant has a valid, explained reason to do so. It can map to the shopper email or to a cart record.
Fields: required state, Continue text, checkout field label, no mapping / cart attribute / cart note / shopper email mapping.
Brand note
Insert merchant-authored context, education, or reassurance between questions. This is not a customer-review generator and must not be used to present invented testimonial content.
Fields: title, supporting content, Continue text.
Loading
Use a timed transitional step when the merchant wants to frame the move into the recommendation.
Fields: 3, 4, 5, 6, or 8-second duration; up to four progress messages; ready title; ready description; ready CTA.
Route useful answers and map only necessary checkout context.
Conditional answer routing
A rule can route a chosen answer from an option-bearing step to another shopper step or straight to Result reveal. This lets a journey omit irrelevant questions rather than force every shopper through the same sequence.
- Start point: a selected answer from a supported option-bearing step.
- Destination: another shopper step or Result reveal.
Checkout mapping
Text input, date picker, and email capture can retain a response as merchant-controlled checkout context. A supplied checkout field label identifies the value in its destination.
- Destinations: no mapping, cart attribute, cart note.
- Email capture also supports: shopper email mapping.
Consent text and policy links
Intro consent content is merchant-authored. Add only the links and statements that are accurate for the store and the type of information requested.
- Fields: consent sentence; multiple link labels and destinations.
- Merchant review: policy wording, links, and applicable legal requirements.
Set the customer-facing interface.
Presentation controls apply to the shopper experience. They are separate from the recommendation logic so a merchant can establish the visual and behavioural standard for the full journey.
Merchant review: check contrast, logo legibility, action labels, consent language, policy destinations, and the appearance of the experience on the device types your shoppers use.
Define what the shopper receives at the result.
The Result reveal combines a display model with one to three plan tiers. Flow requires each plan to contain at least one feature before publication so the shopper is not sent to a blank recommendation promise.
Recommendation display
Choose the result model that corresponds to the product decision.
- Single product
- Product + subscription
- Product alternatives
- Bundle / routine
Plan layout
Control the structure of the resulting plan cards.
- Two-column: side-by-side plan cards.
- One-column: stacked plan cards.
Plan tiers
Use up to three plans when a result requires a comparison or tiered choice.
- Fields per plan: tier name, description, price label, required feature list, CTA text, optional CTA support text.
- Publication rule: add at least one plan feature to every published plan.
Product content source
Where supported by the selected result mode, choose Shopify product content or a merchant-written recommendation summary.
- Shopify source: carries the product content chosen in Shopify.
- Recommendation summary: lets the merchant explain why this is the selected next step.
Map the recommendation to the right Shopify action.
Product and variant selection
Map the recommendation plan to a Shopify product and an available variant. Confirm the selected item is active, available, correctly priced, and suitable for the recommendation.
- Fields: Shopify product and available variant.
- Merchant review: availability, product content, price-related copy, and customer suitability.
Collection mapping
Map a Shopify collection where the result experience uses collection-led recommendation behaviour.
- Field: Shopify collection.
- Merchant review: the collection contents and product eligibility.
Subscription connection
Select the purchase context used by a subscription-oriented plan.
- Options: one-time purchase, Shopify Subscriptions, Recharge, or Bold Subscriptions.
- Provider setting: provider plan ID for supported subscription connections.
Bundle / routine
Build a result from multiple products when the merchant intends to show a considered routine rather than one recommendation.
- Limit: up to four mapped products in a bundle / routine plan.
- Merchant review: compatibility, inventory, discount presentation, and required purchase terms.
Native quantity offers
Configure a same-product Buy X Get Y pattern when the connected Shopify installation and permissions permit the native offer path.
- Configurations: 1:1, 2:1, or 2:2.
- Offer source: use an eligible Shopify automatic offer or create a matching native automatic offer.
- Merchant review: eligibility, stackability, pricing, final shopper terms, and Shopify discount behaviour.
Turn an approved draft into a stable shopper link.
Save the draft
Save while content, product mapping, plan features, and presentation are under review. Drafts may remain incomplete and are not shareable shopper funnels.
Publish the result
Before publish, make sure every result plan contains at least one plan feature and the merchant-reviewed content is accurate. The first successful publish creates the stable title-based slug.
Copy the public link
Return to Funnels and use Copy link on the published card. The URL uses the merchant primary storefront domain, the approved Shopify app-proxy path, and the persistent slug.
Expected published pattern
https://merchant-store.com/apps/flow/quiz/everyday-routineBuilder Preview is different. It remains a Flow-hosted work surface. The copied link is the merchant-domain shopper route. A funnel published before merchant links were introduced receives its slug when it is successfully published again.
Resolve the common publishing and delivery checks.
Publication says: “Add at least one plan feature … before publishing.”
Open the affected result plan and add a truthful feature that explains the plan to the shopper. Drafts can remain without features; published plans cannot. Flow does not add a feature automatically because this is merchant-controlled customer-facing copy.
A published funnel shows “Publish again to create this funnel’s shopper link.”
The funnel predates stable merchant links. Review the content, save and publish once, then return to Funnels. The first successful publish after the change creates the permanent slug.
A published card does not show Copy link.
Reload Flow from Shopify Admin first. Confirm the funnel is published and the Flow installation has the required app-proxy permission. If the card asks to publish again, resolve the plan feature requirement and republish.
The copied URL opens the wrong surface.
Use Copy link from the published Funnel card, not the Builder Preview control. The shopper URL should begin with the merchant storefront domain and include /apps/flow/quiz/; Preview is intentionally Flow-hosted.
Products, pricing, or offers changed after publication.
Update the merchant-controlled configuration in Flow and Shopify, then review the shopper experience and publish the revised funnel. Do not rely on an older result card to describe changed product availability, pricing, subscription terms, or discount conditions.
An image or logo will not upload.
Save the funnel as a draft first. Use PNG, JPEG, or WebP, keep the file at or below 1 MB, and confirm it is the intended merchant-owned visual.
Support route
A public support contact will be added after the support operating model is approved. Until then, use the agreed private support route for the Flow installation. Never send Shopify credentials, API keys, HMAC values, Admin session URLs, or other secrets in a support request.