How JourneyOS connects to your stack.
JourneyOS reads funnel event data and voice-of-customer artifacts you already have. The current integration surface is intentionally CSV-first; native integrations land as pilot partners need them.
Which integrations JourneyOS supports today.
- CSV and Excel upload
- Always supported. Funnel event exports, voice-of-customer artifacts, and customer attribute samples all ingest cleanly via flat-file upload.
- JSON ingest
- Supported for funnel event data. Most analytics and CDP tools export to JSON; JourneyOS reads the export directly.
- Plain-text ingest
- Reviews, NPS verbatims, and support tickets accepted as plain text or structured plain text (one artifact per row).
How JourneyOS adds native integrations.
Native integrations are scoped per pilot demand. JourneyOS does not maintain a speculative roadmap of named integrations because that pattern almost always misses what real pilot partners actually need.
If a pilot partner is using a specific CDP, marketing automation tool, or analytics product, JourneyOS scopes the native integration on the engagement timeline. The CSV export path keeps the engagement moving while the native integration ships.
Does JourneyOS offer an API?
Not in v1. API access is planned for enterprise engagements. Pilot integrations use CSV export today; the API path opens when a pilot partner requires programmatic ingest.
What data JourneyOS needs to run a simulation.
The simulation runs on three input types. Each is shippable in a few hours of client engineering work.
- Funnel event data
- CSV, JSON, or analytics-tool export. Required: per-event timestamp, event name, and a hashed user identifier so the method can reconstruct per-user step paths.
- Voice-of-customer artifacts
- Plain text or structured plain text. Reviews (Reddit, app stores, on-site), NPS verbatims, and support tickets are all accepted. Volume target: 50 to 500 artifacts per customer segment to clear the minimum coverage level for confidence-scored output.
- Customer attribute samples (optional)
- CSV. Hashed customer IDs paired with optional attributes (vertical category, geography, signup channel). The method can run without attributes; it works on the behavioral signal in the artifacts.
Common integration questions.
These four questions back the FAQPage structured data on this page (per Google FAQPage policy: visible content matches the schema verbatim).
Does JourneyOS integrate with my CDP or marketing automation tool?
JourneyOS does not yet offer named native integrations with specific CDP or marketing automation tools. JourneyOS ingests data via CSV export from any CDP, analytics, or marketing tool today. Native integrations are scoped per pilot demand and added as pilot partners require them.
When will JourneyOS add native integrations?
Native integrations are added as pilot partners require them, not on a speculative roadmap. Clients with a specific integration requirement should mention it in the walkthrough; if the requirement aligns with the active pilot pipeline, JourneyOS prioritizes the integration on the engagement timeline.
What data formats does JourneyOS accept?
CSV and Excel for all data types. JSON for funnel events. Plain text or structured plain text for reviews, NPS verbatims, and support tickets. JourneyOS does not require a specific tool-vendor format; the method reads the underlying signal.
Does JourneyOS offer an API?
Not in v1. API access is planned for enterprise engagements. Current pilot integrations use CSV export.
Contact for integration questions.
Integration questions: [email protected]. JourneyOS responds with the current ingest specification and an estimate of the native-integration timeline if your pilot is in scope.
Last updated: 2026-04-27.