Flows

flows is in limited beta 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 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 mobile app events → installed, enabled push, usage milestones 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) 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) selecting an existing campaign duplicates only its content for use inside the 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 with optional expiration date 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 ai splits ai evaluates a yes/no condition and routes personas accordingly must be a yes/no question see docid\ h5ax klzalzypq ke9nvz for examples and how to structure your prompt integration node node representing events from external systems the drawer lists available events based on the connected integration 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 analytics \[tbd] 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 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