Source
Journeys & orchestration — found from sitemap — Customer.io
Checked for Customer.io on 1 Oct 2026
- Page
- https://docs.customer.io/messaging/journeys-overview/
- Checked
- 1 Oct 2026, 09:52 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:9f0369cda0ef54d7211a550e61d7df2cb873a77eed2ed44df6e7c21c02062b21
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Messaging channels Report an error
“Automations and Broadcasts send email, SMS, push, and in-app messages to your people. But, beyond that, your automation and broadcast workflows can send Slack messages, webhooks, update attributes, and more.”
-
Transactional messages Report an error
“Transactional messages are emails that you send in response to your audience’s actions in your app.”
-
Automations Report an error
“You can trigger automations when people perform events, when they join Segments (e.g. they meet attribute conditions), and so on.”
-
Broadcasts Report an error
“Broadcasts send a message to a list of recipients. Broadcast messages are queued to send to all the defined recipients at a time you specify.”
-
Objects Report an error
“Objects are the things that are important to your people, like an account they belong to, online courses they enroll in, or homes they’re interested in purchasing. A change to object and people’s relationships can trigger automations.”
-
Segments Report an error
“A segment can trigger automations, define recipient lists, represent conversion criteria, and more.”
-
Preconfigured segments Report an error
“you’ll see segments like “Paying Customers”, “Have not logged in recently” and “Unsubscribed””
-
Realtime data Report an error
“Your Product sends Real-time Data to Customer.io.”
-
Data sources Report an error
“you can also use your preferred tools and sources to transit data through Customer.io.”