> For the complete documentation index, see [llms.txt](https://corvane.gitbook.io/getting-started/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://corvane.gitbook.io/getting-started/getting-started-with-journey.md).
# Getting Started with Journey
### Journeys
A Journey is a behavioral research tool that lets you watch a user’s "flight path" through your website or prototype.
While a survey asks people what they *think*, a Journey shows you what they actually *do*. It records the specific steps a person takes to get from Point A (starting the task) to Point B (finishing it).
### In Plain English: It’s a "Stress Test" for your Website
If your website is a maze, a Journey is the bird’s-eye view that shows you exactly where people are hitting dead ends.
#### What it tracks:
* The Path: Did they use the menu, the search bar, or a button you didn't think they'd click?
* The Friction: Where did they pause? Where did they click "Back" because they got confused?
* The Success Rate: Out of 100 people, how many actually reached the goal (like the "Thank You" page)?
* The Time: Does it take 30 seconds to find the "Help" center, or 3 minutes?
***
### Why you’d use it
* Checkout Audit: Find out if people are dropping off because your "Shipping Info" page is too complicated.
* Homepage Testing: See if users can find your "Pricing" page within two clicks.
* Prototype Validation: Before you spend money coding a new feature, test a Figma prototype to see if users even understand how it works.
* Mobile vs. Desktop: Prove that your mobile site is harder to use than your desktop site (or vice versa) with hard data.
***
#### 1. Introduction & Configuration
Define the foundation of your study. This is where you set the "rules of engagement" for your testers.
* Identify the Core: Name your project and describe the specific behavior you are analyzing (e.g., "Mobile Checkout Friction Audit").
* Select Test Type: Choose between a Live Website, a Prototype (Figma/InVision), or a Card Sort.
* Device Targeting: Optimize for the platform that matters most—select Mobile, Desktop, or Both.
#### 2. Select Audience
Just like with *Swipe* projects, targeting the right people is critical for representative data.
* Database Distribution: Send your journey to your entire tester database with one click.
* Targeted Segments: Use specific focus groups to see how different demographics navigate your site differently.
* Representative Swiping: Ensure the users "walking the path" actually reflect your real-world customers.
#### 3. Define Tasks
This is the "meat" of the Journey. You aren't just asking questions; you are setting missions.
* Mission Scripting: Provide clear instructions (e.g., *"Find the returns policy in the footer and click it"*).
* Success Mapping: Input a Starting URL and a Goal URL. The system automatically tracks who reaches the destination and who gets lost along the way.
* Multi-Step Paths: Add multiple tasks to test an end-to-end experience from homepage to conversion.
#### 4. Overview & Quality Check
Before going live, review your entire setup to ensure the logic holds up.
* Goal Verification: Double-check that your "Success URL" is correct so your data stays clean.
* Flow Review: See the journey from the participant’s perspective to ensure instructions are crystal clear.
#### 5. Publish & Collect
Launch your project and start watching the data roll in.
* Real-Time Tracking: Watch as participants complete tasks and see your "Success Rate" update instantly.
* Save as Draft: Not ready to launch? Use the Save as Draft feature in the top right at any stage to keep your setup secure while you refine your objectives.