Iterable

For an onboarding journey that waits for a purchase, distinguish the waiting tile from the journey's exit rule. Iterable's Hold Until tile reacts to events or profile changes after someone enters that tile. A journey exit rule can instead watch across the journey. An event that happened before the waiting step is therefore a reason to consider the broader exit condition.

Hold Until can wait up to 30 days and route people according to whether its conditions were met. Editing a live Time Delay affects new entrants; people already waiting keep their original delay. Check both groups when changing the cadence of a running sequence.

An exit is not always immediate. Someone in a Time Delay leaves within 48 hours of the qualifying event or profile change, or before their next tile, whichever happens first. A message already scheduled through Send Time Decisioning can still send after exit. These details matter when the follow-up must end after a customer acts. Iterable's sales route provides a pricing estimate and integration discussion.

For a new team member, an administrator opens Settings > Organization > Organization Members, creates the member, assigns a project and sends an invitation. The member confirms the email address to activate access. Sign-in can use the organization's single sign-on, Google or a password; use the login address for the account's US or EU data centre. After signing in, Messaging contains journeys and campaigns, while Audience holds lists and customer profiles.