Journeys & orchestration — found from sitemap — Customer.io

Cited by

Facts read from this source

• Journeys tab Report an error

  “You can follow each person's history through an automation like the deliveries they've received, conversions, and when they entered/exited. You can find them in the Journeys tab of an automation.”

• Journeys immediate start no filters Report an error

  “If your automation doesn’t have filter conditions, the journey starts immediately when a person matches your trigger criteria.”

• Journeys legacy segment trigger filters Report an error

  “For legacy segment-triggered automations, a journey starts as soon as a person matches the automation’s trigger conditions. If they don’t match the filter conditions, they’ll wait to continue your workflow until they meet these conditions or exit after a period of time.”

• Journeys filter retry window Report an error

  “If the person does not meet the filter conditions when we receive the event, we will retry for up to 30 minutes.”

• Journeys manual end Report an error

  “You can end a journey for a person from the Journeys tab of an automation or a person.”

• Wait before continuing Report an error

  “Turn on Wait before continuing journey. The journey waits up to 24 hours before continuing”

• Wait setting complements rate limiting Report an error

  “This setting complements rate limiting in your automation. If you want to make sure people receive your messages before moving forward in a rate-limited automation, then you should enable this setting.”

• Automations support triggers Report an error

  “For automations triggered by an event, object, relationship, date or form, a journey starts after the trigger conditions AND filter conditions are met.”

• Journeys manual end label Report an error

  “The journey will update to “Exited early.” And you’ll see this as the reason: “The person was manually removed from the automation.””