---
title: "Success Criteria"
canonical: "https://help.uxarmy.com/space/UT/89554947/Success%20Criteria"
format: markdown
---
On UXArmy platform, Success Criteria helps you measure whether participants successfully completed a task.
## **Types of Success Criteria**
There are **3 types of Success Criteria** available on UXArmy:
1. Destination
a. Goal Screen URL (Website & URL-based Prototype Testing),
b. Goal Screen
2. Task Completion Time
3. Answer
(Note: If **No Criteria** is selected, the task will not be marked as Pass or Fail in the test reports. This option is useful when you want participants to freely explore a website, mobile app, or prototype without evaluating task success.)
## **1a. Goal Screen URL (Website & URL-based Prototype Testing)**
Use the **Success URL** criteria for assessing the ability to find specific pages on a website or prototype.
- You can add **multiple Success URLs** in one task
- Helps understand which navigation paths users take
- Supports:
- Exact URL Match
- Partial URL Match
*Goal Screen URL for Prototype*
*Goal Screen URL for Website*
### **Exact URL Match vs Partial URL Match**
| | | |
| --- | --- | --- |
| | **Exact URL Match** | **Partial URL Match** |
| **Use Case** | When you want to test if participants land on the exact page you expect | When there are multiple possible navigation paths |
| **Your chosen Success URL** | [https://www.example.com/products/mobile-app-testing](https://www.example.com/products/mobile-app-testing) | [https://www.example.com/products/](https://www.example.com/products/) |
| **What the platform will mark as Success** | [https://www.example.com/products/mobile-app-testing](https://www.example.com/products/mobile-app-testing) | [https://www.example.com/products/mobile-app-testing](https://www.example.com/products/mobile-app-testing)
[http://www.example.com/products/usability-testing](http://www.example.com/products/usability-testing)
[http://www.example.com/PRODUCTS/reporting-and-analysis](http://www.example.com/PRODUCTS/reporting-and-analysis) |
| **What the platform will mark as Failure** | [https://www.example.com/products/mobile-app-testing/pricing](https://www.example.com/products/mobile-app-testing/pricing)
[http://www.example.com/products/usability-testing](http://www.example.com/products/usability-testing) | [https://www.example.com/ux-services/ux-design](https://www.example.com/ux-services/ux-design) |
### **Exact Match**
Use this when you want to check whether participants landed on a **specific page**.
- Add the exact page URL
- Task is marked **Success** only if participants end the task on that exact page
**Example: Exact URL Match**
For example, if your task is to find women’s jeans on the H&M website, you can copy and paste the exact URL of the page.
Example URL: “[https://www2.hm.com/en_my/ladies/shop-by-product/jeans.html”](#)
- Success - If participants end the task on this exact page
- Failure - If participants end the task on any other page
**Prototype Tip:**
Disable navigation beyond the goal screen to avoid incorrect marking of task Success.
### **Partial Match**
Use this when there are **multiple valid pathways** to complete a task.
- Add a partial URL (e.g., `/products/`)
- Any page containing this string will be marked as Success
This helps you:
- Understand user navigation behavior
- Identify preferred paths
- Evaluate task completion flexibility
**Example: Partial URL Match**
For example, if your task is to add women’s jeans to the cart, there can be multiple valid pages (different products).
In this case, you can use a partial URL.
Example URL:
/ladies/jeans
- Success - If participants land on any page that contains “/ladies/jeans”
- Failure - If they land on unrelated pages like “/men/” or “/kids/”
### **How to Get Webpage URL**
*Website URL *
1. Open the page you want users to reach
2. Copy the URL from the browser
3. Paste it into the Success URL field
## **B. Goal Screen (Figma & Marvel Prototypes)**
In Figma prototype testing, you define success using a **Goal Screen (End Screen)** instead of URLs. You first select a **Starting Screen** (where the task begins) and an **End Screen (Goal Screen)** (where participants should reach).
There are two ways to define success using the Goal Screen.
### **1. End Screen Matching**
In this method, you only define the starting and end screen. Participants can take any path within the prototype.
Success - If participants reach the selected end screen
Failure - If participants do not reach the end screen
This is useful when the final outcome matters and multiple navigation paths are acceptable.
*Defining the starting and end screen.*
### **2. Navigation Path Matching (Path Criteria)**
In this method, you define one or more specific paths (sequence of screens) that participants are expected to follow. These paths are created using screens, not URLs.
*Setting Navigation Path*
### **Types of Success in Path matching:**
1. **Direct Success**
- Participant follows the **exact path you defined**
- Reaches the **Goal Screen**
2. **Indirect Success**
- Participant **does not follow the defined path**
- Takes a different route
- But **still reaches the Goal Screen**
3. **Failure**
- Participant **does not reach the Goal Screen**
- Ends the task on a different screen
### **Why Use Path Matching?**
- Helps you understand if users follow the **intended navigation flow**
- Identifies **alternative navigation behaviours**
- Provides deeper insights beyond just reaching the final screen
**Example**
Task: *Find and view a product in the app*
- **Defined Path:** Home - Category - Product List - Product Page
Results:
- Participant follows the defined path to view the product - **Direct Success**
- Participant searches and reaches product page - **Indirect Success**
- Participant never reaches product page - **Failure**
You can create multiple valid paths to capture different expected user journeys. This helps you understand whether users follow the intended flow or take alternative routes while still completing the task.
## **2. Task Completion Time**
Use this to check if users are able to complete the task in the expected time duration.
- Enter time in **seconds**
- Task is marked:
- Success - Completed within time
- Failure - Not completed within time
Participants are allowed to continue even after exceeding the time that was set.
*Set Task completion time*
## **3. Present Answer**
Use this when participants must **input a specific answer**. This is useful in case your research wants to ensure whether participants can find a piece of information on the desired screen / page but the multiple screens / pages have the same URL.
- Supports:
- Text input
- Number input
- Task is marked:
- Success - Answer matches
- Failure - Answer does not match
**Note:**
Answers are case-sensitive.
*Preset Answer Criteria*
## **Success Criteria Availability by Test Type**
| | |
| --- | --- |
| **Test Type** | **Available Options** |
| **Website Testing** | No Criteria, Success URL, Task Completion Time, Answer |
| **Prototype **
Public URL-based prototyping tools e.g. ProtoPie, Figma Make, etc. | No Criteria, Success URL |
| **Prototype **
UXArmy fully integrated prototyping tools i.e. Figma and Marvel | No Criteria, Goal Screen (End screen matching and Navigation path matching) |
| **Mobile App Testing (iOS/Android)** | No Criteria, Task Completion Time |
## **Note**
Available success criteria options may vary depending on the test type and integration.