Flows

flows is in beta and will be released feburary 2026 aiq flows let you automate customer journeys based on real events and behaviors a flow is made of connected nodes (triggers, actions, delays, splits, integrations) personas enter a flow when they match the trigger criteria, and each node determines what happens next you can start from scratch with a trigger based flow or from a prebuilt flow template timing differences traditional audiences vs flows traditional docid\ iozbp0zvnf1nixucqornl are not updated in real time and typically become available after an overnight capture audience based campaigns can only message customers once this overnight process completes flows process events and traits more frequently than traditional audiences, allowing for faster follow up in many cases however, timing varies by trait type messaging & opt in–related traits (e g submitted signup form, opt in status change) typically available within 5–20 minutes custom attributes / rest api traits typically available within 5–20 minutes sales related traits (e g purchases, transaction data) follows traditional audience capture persona attributes ( e g name, phone number, email used for targeting) follows traditional audience capture note trigger and split conditions created in flows will not be added to the audiences list and is isolated to just that flow how to create a flow option 1 trigger based flow choose a trigger that determines which personas enter the flow and when each trigger includes configurable parameters common trigger types signup form → persona submits a form audience events → persona enters or exits an audience abandoned cart → based on available integrations purchased → product, brand, or category based behavioral events → viewed but didn’t buy (depends on integration) points events → earned points, redeemed, unlocked discount campaign events → opened, clicked, received, didn’t open lifecycle → birthday, inactive, x days since last order option 2 flow templates flow templates give you a starting structure categories may include welcome series abandoned cart win back repeat purchase encouragement retention opt in messaging select a template → load it into the builder for customization flow builder basics the flow builder uses a drag and drop interface nodes must be connected, no standalone or disconnected nodes key builder functions zoom in/out via floating controls save as draft, duplicate, archive edit details (name, tags, dates, budget) switch between edit and analytics modes back button returns to flow table (warns if unsaved changes) once you start building, each node must be configured before the flow can launch node types nodes define the actions taken as personas move through the flow there is no limit to how many nodes a flow can contain trigger defines how personas enter the flow set during creation multiple triggers are allowed per flow message (campaign) send a message through all of our available channels (excluding loops) select a template or create a new landing page all within the flows builder a minimum of one message/template is required to launch your flow campaigns created in flows do not appear in the general campaigns list give discount attach a discount to personas moving through the sequence select an existing discount or create a new one discounts created in flows do appear in the main discounts list gift points grant a fixed number of loyalty points time delay pause the flow before moving to the next step minimum delay 30 minutes maximum delay 1 year messaging triggered after a delay will still follow quiet hours, tcpa, 10dlc, and unsubscribe rules split route personas into yes or no based on an audience create or select an existing audience multiple splits are allowed per flow you can start your flow with a split ai splits ai evaluates a yes/no condition and routes personas accordingly must be a yes/no question must end in a question mark see docid\ h5ax klzalzypq ke9nvz for examples and how to structure your prompt integration node ( coming soon) node representing events from external systems launching & editing flows launch rules a flow cannot be launched if any node is unconfigured all sends follow tcpa, quiet hours, 10dlc, opt in and unsubscribe handling, persona frequency caps editing rules for live flows once a flow is live only time delay nodes can be edited you cannot change the trigger you cannot reorder nodes you cannot alter logic campaign content can be edited; personas who haven’t reached the campaign node will receive the updated version how to edit flow details when you go to save or launch a flow for the first time, you will be prompted to fill out the flow details you can also access these settings in the flow builder, click on the ( ) more menu > edit details name the internal name of the flow this name is used for identification and reporting and is not visible to your customers tags tags help you organize and manage your flows tags are shared globally across aiq features, including campaigns, making it easier to filter and group related assets start date / end date optionally set a start and end date to control when the flow is active if no dates are set, the flow will run continuously until paused or disabled daily max credits optionally set a daily spend or credit limit for the flow if this limit is reached, the flow will automatically pause for the remainder of the day and resume the following day lifetime max credits optionally set a total lifetime spend or credit limit for the flow once this limit is reached, the flow will be disabled and will not resume unless manually updated flow attribution window sets the attribution window used to measure conversions and revenue for all nodes within this flow the default attribution window is configured in settings → company account → account settings, but can be overridden at the flow level if needed docid\ wwpt3ssmqzl1o0yypspmp if re entry is enabled, they may enter the flow again later (after completing the entire flow) if they meet the trigger conditions again flow cooldown when re entry is enabled, a cooldown period (in days) is required this determines how long a customer must wait before they can enter the flow again only certain traits qualify for re entry see docid\ wwpt3ssmqzl1o0yypspmp for more info flow analytics + reporting aiq provides two ways to view flow performance, depending on the level of detail you need for step by step, node level analytics within a flow, see docid\ ye ifcvfjkiimh9y g1yw for aggregate performance reporting across all flows, see docid\ amutasfexbbnw pzegp5f settings & configuration the default attribution window for flows can be configured in docid\ gm4c2cqxhyhtwwwrycd1i edit per flow attribution windows and additional details (start/end date, credit limits, etc ), see docid\ bcrbfcoetju7 goim0yue best practices avoid using opt ins as triggers in re entry flows do not use opt in status as a trigger when flow re entry is enabled for example, using a trigger like email opt in = true can cause personas to repeatedly re enter the flow because opt in status rarely changes this can unintentionally create looping behavior instead, trigger the flow using an actual event or behavior, then use a split inside the flow to check opt in status and route personas to the appropriate channel use multi channel splits for better reach customers are not always reachable through a single channel use splits within your flow to check available channels and route personas accordingly, such as email if email opt in is available sms if sms opt in exists push notification if app push is enabled or fall back to another channel when one is unavailable this ensures more customers receive your messaging instead of being excluded from the flow trigger flows on actions, not static traits flows perform best when triggered by customer actions or events , such as purchase made cart abandoned signup completed loyalty points earned reward redeemed avoid triggering flows on static profile traits that rarely change, as this can cause unintended re entry or low relevance messaging add delays to prevent message overload use delays between steps to avoid overwhelming customers with multiple messages in a short time spacing messages improves engagement and reduces opt outs keep flows focused on a single goal each flow should have one clear purpose, such as welcome new customers win back inactive customers encourage repeat purchases promote loyalty engagement avoid combining too many objectives in one flow, as this makes performance harder to measure and optimize troubleshooting flow won’t launch a flow can only launch if all nodes are fully configured and valid check the following one or more nodes are unconfigured configure each node until alerts disappear the trigger setup is incomplete personas aren’t entering the flow (no entrants) if your flow shows zero entrants, the issue is almost always related to triggering or data availability possible causes trigger conditions have not been met (e g no one has submitted the signup form) fix check the analytics for that trigger (audience, signup form, etc ) audience logic is too restrictive fix for audience based triggers, overly narrow filters may match zero personas preview the audience → check how many personas qualify personas are stuck / not moving to the next node if a persona enters the flow but stops progressing, check the following time delay has not elapsed yet delays are strict delays also respect quiet hours, which may postpone sends until compliant windows split conditions are still pending this occurs if ai needs more information or an audience assignment is still processing integration node is waiting for an external event if the flow expects an event such as “order created,” the persona remains paused until that event occurs and is sent to aiq from the respective partner discount or points node validation failed if a discount is expired or misconfigured, delivery can’t proceed they qualify for certain nodes earlier in the flow, but not ones later in the flow for example, they might complete the email node (because they are opted in to that channel), but get stuck at the text node later in the flow (because they are not opted in) and then cannot move past that node use conditional splits with opt in traits to fix this issue discount or points are not applying discount may be expired if the discount expires after launch, personas can get stuck faqs once i launch a flow, can i make edits? partially you can only edit time delay nodes in a live flow you cannot edit triggers, campaigns, discounts, gift points, splits, or any other node type once the flow is active if you need to change anything other than a time delay, duplicate the flow , make updates, and launch the new version do flows save automatically? no flows follow the same pattern as our campaign builder, where you can manually save as draft and if you try to close the builder with unsaved changes, a confirmation modal will appear do messages in flows show in the main campaigns list? no messages created inside flows are not standard campaigns they only contain content (no campaign level settings) and inherit rules from the flow itself do discounts created or used in flows appear in the main discount list? yes all discounts created or attached in flows are available in the normal discounts list do messages in flows have their own attribution window settings? no attribution is set at the flow level, not per message (aka campaign) can i have multiple splits in a single flow? yes you can add as many split or ai split nodes as needed can i have multiple triggers in a single flow? yes multiple triggers are supported can i use campaign level settings like intelligent timing (aka personalized send time) inside flows? no campaigns inside flows do not use campaign level features all sends follow the flow’s logic and global compliance rules can i ab test flows? not in this version a/b testing will be considered for a future release is there a node limit in flows? no you can have as many nodes as you want is there a time delay limit in flows? yes the time delay cannot exceed 365 days, or 1 year how are flow audiences different from traditional aiq audiences? traditional aiq audiences are evaluated during an overnight processing cycle, meaning customers may not become eligible until the next day flows evaluate triggers and traits more frequently, allowing customers to enter a flow much sooner after an action occurs see https //support alpineiq com/flows#drvcs can i use an existing audience in a flow? yes, use the is in audience(s) to select from your existing list my ai condition / prompt is not working as expected, how can i fix it? see docid\ h5ax klzalzypq ke9nvz can a customer / persona enter the same flow more than once? (can they go through multiple times) yes, but with limations you can enable re entry with optional cooldown periods for flows which start with certain triggers for more information, check out docid\ wwpt3ssmqzl1o0yypspmp this allows retailors to enable "ongoing" or recurring flows what if i need to check something in the future or send follow up actions? use delays and conditions within the same flow if you need to wait for a future event or evaluate a condition at a later time, add a delay step followed by the appropriate condition customers will continue moving forward through the flow as those steps are reached do i need to add “email opt in = true” as a trigger for email flows? no if your flow contains email steps, messages will only be sent to customers who are opted in to email customers who are not opted in will simply not receive the message however, if the flow continues to other steps after an email node, customers who cannot receive that email may stop progressing through the flow unless you add splits or alternate paths what happens if a customer isn’t opted into a channel used in the flow? if a customer reaches a step for a channel they are not opted into, they cannot proceed past that step unless you add a conditional split or alternate path example flow step order wallet message → sms customer not opted into wallet customer never reaches sms because the flow is linear to avoid this, add a split or alternate path around channel specific steps can i send an sms containing a contact card in a flow? no contact cards are not supported in this version of flows we are considering it for a future version i created a flow, but i do not see my persona list entering the initial trigger? if you have a start date set on your flow, this will prevent aiq from analyzing your trigger until that date/time occurs check back after the flow flips to live can i edit my max credits after launching my flow? yes, after you launch your flow, you can edit both your daily and lifetime max credits