Pick your install path, let Xenia learn your business, connect a data source, and ship your first journey.
Getting to a live journey takes four things: an installed workspace, a business context Xenia can reason about, at least one connected data source, and a journey that passes approval. This page walks the whole path and links to the detail page for each step.
1. Install Xenia
Install the app from the Shopify App Store. It runs embedded in your Shopify admin, the store connects during install, and billing goes through Shopify. See Shopify app.
2. Let Xenia learn your business
The first time you open a new workspace, Xenia runs an onboarding wizard that builds your business context: what you sell, who you sell to, your brand voice, and the KPIs you care about. Everything the AI later writes or plans is grounded in this context, so it is worth doing properly.
Step one offers three ways to provide it:
Research runs as a live feed you can watch, then you land on a review screen to correct anything before activating. On the Shopify install this step is a single tap, because the storefront URL already comes from the verified session.
Onboarding is resumable. The workspace tracks which context cards are still missing and keeps showing them on your Workspace dashboard until they are complete.
3. Connect a data source
Xenia cannot segment what it cannot see. Connect at least one source of customer data before building audiences. Shopify, HubSpot, and Klaviyo are the three that unlock the built-in audience templates.
Connectors are configured per environment, so a credential added in Development does not exist in Production. See Connectors.
You also need at least one delivery channel connector, an email or SMS provider, before a journey can send anything.
4. Build your first journey
Start from a template
Open Journey Library and import a pre-built journey. This is faster than a blank canvas and shows how the node types fit together. See Journey Library.
Set the trigger
Pick what enrolls people: a Shopify event, a schedule, an inbound webhook, or a platform event such as a Meta lead form submission. See Journey Orchestrator.
Write the message
Author the email, SMS, web block, or popup in
Content Studio, or write the copy inline in the
channel node using {{variable}} tokens for upstream values.
Add a briefing
Every journey needs a briefing before it can go to review. It is the plain language description reviewers read to judge risk, so state the audience, the channel, and the intent.
Simulate it
Run the journey in Simulation with a test payload and confirm every node reaches the state you expect. Nothing reaches a real customer here.
Send for approval and publish
Move the journey to Review on the Journey Manager board. An Admin or Manager approves it in Approvals, then it publishes and goes live.
5. Verify it worked
Open Analytics and confirm the journey shows executions and, once conversions land, attributed revenue.
Events flow through a streaming pipeline before they are queryable, so a conversion you just triggered typically takes a few minutes to appear. An empty chart seconds after a test is normal.
Where to go next
- Connectors for the full integration catalog
- Audiences to turn customer data into segments
- Journey Orchestrator for the complete node reference
- Workspaces and access to invite your team