Each journey drawn as the Iterable Journey Builder canvas you will actually build, tile by tile. Every tile below exists in the palette, and every trigger uses an event already live in Iterable.
Abandoned quote sits outside the lifecycle fan. It fires on live intent rather than on a stage, and is the fastest of the four to pay for itself.
All gated on User ID ≠ none, so anonymous browsing never arrives. brand is always access-hire, so it carries no segmentation value. Personalisation comes from each contact's own view and lead history.
Confirm the exact label for the profile and list tiles against your palette. The screenshot cuts off below Attribute split, so Update user profile and Remove from list may be named slightly differently in your instance.
Triggered the moment a customer record is created in NetSuite. The UID is not needed to send this, only to enrich it later with what they browsed before signing up.
Trigger on ns_customer_created. The event itself carries only brand, but almost every new customer enquired first, so their last generate_lead supplies branch, industry and contact_type for personalisation.
onboarding_01_welcomeonboarding_02_how_we_helponboarding_03b_fleet_overviewonboarding_04_your_branch_contactWhat the UID adds later. Today this journey starts from scratch at the moment the customer record is created, so email 1 cannot reference anything they did before that. Once identity stitching lands, the pre-signup browsing attaches to the same person and emails 1 and 3 can open with the machine they were actually looking at. Build it now without that, enrich it later.
Check what creates the record. If ns_customer_created fires on any NetSuite account setup rather than on a genuine first customer, this journey will welcome people who are not new. Confirm the trigger conditions with the NetSuite team before going live.
Same shape repeats five times: send, wait, check engagement, exit anyone who responded. Only the fully silent reach the end.
No email open and no email click in 12 months · still subscribed · sent at least 3 marketing emails in that window · no generate_lead, add_to_cart, view_item, view_item_list, select_item or ns_activitySet in 90 days.
sunset_01_still_theresunset_02_sms_checksunset_03_what_you_misssunset_04_sms_finalsunset_05_removing_youSet the profile field before removing from the list. If the list removal runs first, the contact can drop out of the journey before the field is written, and you lose the record of why they were suppressed.
One Attribute split at the top does the work. Three lanes, each with its own message set, all exiting on the same event.
No generate_lead in 90 days · at least one generate_lead ever · marketingStatus ≠ sunset.
dormant_hot_01_still_need_itdormant_hot_02_sms_repdormant_warm_01_saw_you_lookingdormant_warm_02_get_a_ratedormant_cold_01_whats_newdormant_cold_02_sms_nudgedormant_cold_03_still_youHot: add_to_cart in the last 90 days with no generate_lead after it.
Warm: view_item, view_item_list or select_item in 90 days, no add_to_cart.
Cold: no site activity at all. These feed Sunset later if nothing lands.
Journey-level exit beats a split after every message. Set generate_lead as an exit criterion on the journey itself rather than adding yes/no splits between each tile. Three lanes with splits everywhere becomes unmaintainable fast.
The only one triggered by a custom event rather than a segment, so it fires in real time.
Trigger on add_to_cart. The first delay and split do the qualifying, so nobody who converts gets a chase email.
cart_01_still_need_itcart_02_sms_repcart_03_alternativesAdd a re-entry rule. A customer who carts three machines in a week should not get three chase sequences. Set the journey to allow re-entry only once every 14 days, and confirm whether select_item fires on the same click as add_to_cart before going live.
Captured now so nothing is lost. Each will get a full canvas like the three above as it comes up the queue.
Chase enquiries NetSuite already knows went cold. Probably the highest value journey on this list.
Three or more views of the same category with no enquiry. Shows what they want before they ask.
Same product page twice in 14 days. Narrow audience, high intent.
Recommend adjacent equipment using real product names rather than URL slugs.
A six-line enquiry is a project, a one-line enquiry is a job. Different message, different owner.
Company quiet versus contact quiet. Sends the contact to a rep instead of a win-back email.
Finer than branch for routing replies to the right team.
Separate copy for civil, mining, events and other.
A quote request and a Contact Us enquiry should not get the same email.
Not a journey. A profile field every journey reads, built from view and enquiry history.
Let people choose frequency instead of leaving. Feeds Sunset by reducing who reaches it.
High intent and completely invisible today. No page-view event reaches Iterable at all.
Route to that branch's rep. Browse events carry no branch, and the branch page view is not pushed.
Tells you fleet gaps and earns a "we can source it" reply. No search event exists anywhere.
Hard bounce triggers an SMS to collect a working address. Needs SMS consent coverage first.
Product-led, no brand intro. Needs order and product data flowing and validated.
Feedback ask, then review request or service recovery. Follows Onboarding and Hire.
Extend or re-hire before the machine goes back. Needs hire dates from NetSuite.
Time the approach to each customer's own hire cadence rather than a fixed window.
Customers who hire the same gear every year, contacted ahead of their season.
Fires against a customer's own baseline, well before they hit 90 days quiet.
A different problem to a lapsed repeat customer, and worth its own treatment.