> ## Documentation Index
> Fetch the complete documentation index at: https://docs.auxia.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing Treatments

> For a conceptual overview of Treatments, see [Treatments](/concepts/treatments) in Product Concepts.

## 5.1 Treatment Portfolio

The Treatment Portfolio is your central hub for managing all treatments.

### Accessing Treatment Portfolio

1. Click **Treatments & Journeys** in the sidebar
2. Select **Treatment Portfolio**

### Portfolio View

The portfolio displays:

| Column | Description |
| - | - |
| **Name** | Treatment name |
| **Journey** | Parent journey |
| **Type** | Treatment type (banner, modal, etc.) |
| **Status** | Live, Paused, Draft |
| **Created** | Creation date |
| **Modified** | Last modification date |

### Filtering Treatments

Use filters to find specific treatments:

| Filter | Options |
| - | - |
| **Status** | Live, Paused, Draft, All |
| **Journey** | Select specific journey |
| **Type** | Filter by treatment type |
| **Search** | Search by name |

### Quick Actions

From the portfolio, you can:

* **Click** a treatment to view details
* **Edit** using the edit icon
* **Pause/Activate** using status toggle
* **Preview** using the preview icon

***

## 5.2 Creating a Treatment

Treatment creation uses a 5-step wizard.

### Starting Creation

1. Navigate to Treatment Portfolio
2. Click **+ Create Treatment**

### Step 1: Select Journey

**Purpose:** Every treatment must belong to a journey.

**Fields:**

| Field | Description | Required |
| - | - | - |
| **Journey Type** | Evergreen (ongoing) or Burst (time-limited) | Yes |
| **Journey** | Select existing journey(s) | Yes |

**Selecting Journeys:**

For **Evergreen journeys:**

* Select one or more Evergreen journeys
* Treatment will run continuously within those journeys

For **Burst journeys:**

* Select a single Burst journey
* Treatment inherits the journey's start/end dates

**Validation:**

* At least one journey must be selected
* For Burst, expired journeys are filtered out

> **Tip:** If you need a new journey, create it first via Journey Portfolio.

### Step 2: Basic Information

**Purpose:** Define what the treatment is and where it appears.

**Fields:**

| Field | Description | Required |
| - | - | - |
| **Name** | Descriptive name | Yes |
| **Description** | Purpose and details | Recommended |
| **Target Action** | Desired user action | Yes |
| **Treatment Type** | Format/template | Yes |
| **Surfaces** | Where treatment appears | Yes |

**Name Best Practices:**

* Be descriptive: "Welcome Back - Home Banner v2"
* Include surface or type: "Checkout Modal - Free Shipping"
* Add version or date: "Holiday Sale 2026 - Push"

**Description Tips:**

* Explain the purpose
* Note the target audience
* Include any A/B test context

**Target Action:**
Select the desired user action:

* View product
* Make purchase
* Complete profile
* Open feature
* etc.

**Treatment Type:**
Select from configured types:

* Banner
* Modal
* In-app message
* Push notification
* Email
* etc.

> **Note:** Treatment types are configured by admins. Contact yours if needed type is missing.

**Surfaces:**
Select one or more surfaces where the treatment can appear:

* Home screen
* Product page
* Checkout
* etc.

Multiple surfaces = treatment can appear in multiple locations.

### Step 3: Content

**Purpose:** Define what users actually see.

**Fields vary by treatment type but commonly include:**

| Field | Description | Required |
| - | - | - |
| **Language** | Content language | Yes |
| **Title** | Headline/header | Usually |
| **Body** | Main message text | Usually |
| **Image** | Visual treatment | Depends |
| **CTA Text** | Button text | Usually |
| **CTA Action** | What happens on click | Usually |

**Using Personalization:**

Insert data fields to personalize content:

```
Hello `${user_first_name}`!
```

**How to insert:**

1. Go to **Configuration > Data Management > Data Fields** to find available field names
2. In the content field, manually type the variable in `${field_name}` format

**Available data fields are listed on the Data Fields page. Contact your admin if you need access.**

**Image Requirements:**

* Provide a URL to a hosted image
* Ensure the image is publicly accessible
* Check resolution requirements for your treatment type
* Test image loading in preview

**CTA Configuration:**

| CTA Action | Result |
| - | - |
| Open URL | Opens web link |
| Open Screen | Navigates in app |
| Dismiss | Closes treatment |
| Custom | App-specific action |

### Step 4: Guardrails & Scheduling

**Purpose:** Control who sees the treatment and when.

**Guardrails:**

Define eligibility rules that must be true for a user to receive the treatment:

| Field | Description |
| - | - |
| **Data Field** | The user attribute or event metric to evaluate |
| **Condition** | Comparison operator (e.g., GREATER\_THAN, EQUALS) |
| **Value** | The threshold or value to compare against |

Multiple rules are combined with AND logic — all conditions must be met.

**Boolean conditions:**

Some conditions use a checkbox instead of a value field. These check whether a data field is set or unset:

| Checkbox state | Meaning |
| - | - |
| ✅ Checked (true) | The field **has a value** (is set) |
| ☐ Unchecked (false) | The field **has no value** (is null / absent) |

> **Example:** To send a treatment only to users who have **never** received it before, add a Boolean rule on `last_timestamp` and leave the checkbox **unchecked**. This targets users where no timestamp record exists for that treatment.

**Scheduling:**

| Field | Description | Required |
| - | - | - |
| **Start Date** | When the treatment becomes eligible to serve | Yes |
| **End Date** | When the treatment stops serving | No (leave unset for no end date) |

> **Tip:** For Burst journeys, the treatment's schedule must fall within the journey's start and end dates.

### Step 5: Review & Create

**Purpose:** Verify everything before creation.

**Review checklist:**

* [ ] Correct journey selected
* [ ] Name is descriptive and accurate
* [ ] Treatment type matches intended format
* [ ] Correct surfaces selected
* [ ] Content is complete and spell-checked
* [ ] Personalization variables are correct
* [ ] CTA action is appropriate
* [ ] Guardrails are correctly configured
* [ ] Schedule start/end dates are correct

**Creating the Treatment:**

1. Click **Create Treatment**
2. Treatment is saved in **Draft** status
3. Navigate to activate or continue editing

***

## 5.3 Editing Treatments

### Accessing Edit Mode

**Option 1:** Click treatment name in portfolio, then **Edit**
**Option 2:** Click edit icon directly in portfolio

### What You Can Edit

| Field | Editable | Notes |
| - | - | - |
| Name | Yes | Update anytime |
| Description | Yes | Update anytime |
| Content | Yes | Changes go live immediately if active |
| Journey | Yes | Can reassign |
| Treatment Type | Limited | May require recreation |
| Surfaces | Yes | Update anytime |

### Versioning

Auxia Console tracks treatment versions:

* Each save creates a version
* You can view version history
* Previous versions are preserved

### Editing Active Treatments

> **Warning:** Editing an active treatment updates what users see immediately.

**Best practice:**

1. Pause the treatment first (if major changes)
2. Make your changes
3. Preview the changes
4. Reactivate when ready

### Version Selector

For treatments with multiple versions:

1. Open treatment details
2. Look for the version selector dropdown
3. Select version to view
4. Compare versions if needed

***

## 5.4 Treatment Preview

Preview lets you see how treatments will appear before activation.

### Accessing Preview

1. Open treatment from portfolio
2. Click **Preview** button
3. Or use preview icon in portfolio list

### Preview Modes

| Mode | Shows |
| - | - |
| **Visual Preview** | Approximate rendering of treatment |
| **Content Preview** | All content fields and values |
| **JSON Preview** | Raw treatment data |

### Limitations

Preview is approximate:

* Actual rendering depends on your app's implementation
* Personalization shows placeholder or sample values
* Some interactive elements may not work

> **Tip:** For accurate testing, use QA Testing with real QA users.

***

## 5.5 Bulk Upload

Bulk Upload lets you create multiple treatments at once via CSV file.

### Accessing Bulk Upload

1. Go to Treatment Portfolio
2. Click **Bulk Upload** button (or tab)

### Bulk Upload Process

**Step 1: Download Template**

1. Click "Download Template"
2. Template includes all required columns
3. Open in Excel or Google Sheets

**Step 2: Fill Template**

Required columns vary but typically include:

| Column | Description |
| - | - |
| name | Treatment name |
| journey\_id | ID of parent journey |
| treatment\_type\_id | ID of treatment type |
| surface\_ids | Comma-separated surface IDs |
| content\_\* | Content fields (varies by type) |

**Step 3: Upload File**

1. Click "Upload" or drag-and-drop
2. System validates the file
3. Review validation results

**Step 4: Review & Create**

1. Review the treatments to be created
2. Fix any validation errors
3. Click "Create All" to create treatments

### Validation Errors

Common errors:

| Error | Cause | Fix |
| - | - | - |
| Invalid journey\_id | Journey doesn't exist | Check ID is correct |
| Missing required field | Column empty | Fill in required data |
| Invalid treatment\_type | Type doesn't exist | Use valid type ID |

### Bulk Upload Tips

* Test with 2-3 treatments first before large uploads
* Keep a backup of your CSV
* Use IDs (not names) for references
* Check for special characters that might cause issues

***

## 5.6 Sparks (AI Recommendations)

Sparks provide AI-powered recommendations during treatment creation.

### What are Sparks?

Sparks analyze your treatment and suggest:

* Improved headlines
* Better CTAs
* Personalization opportunities
* Content optimizations

### Using Sparks

1. During treatment creation (Step 3)
2. Look for the Sparks panel or icon
3. Review suggestions
4. Click to apply or dismiss

### Spark Types

| Spark Type | Suggestion |
| - | - |
| **Headline** | Alternative title options |
| **CTA** | More effective button text |
| **Personalization** | Where to add data fields |
| **Content** | Copy improvements |

### Providing Feedback

Help improve Sparks by:

1. Clicking thumbs up/down on suggestions
2. Using the feedback dialog
3. Noting which suggestions were helpful

> **Note:** Sparks availability depends on your Console configuration.

***

## 5.7 Treatment Status Management

### Status Definitions

| Status | Meaning | Visible to Users |
| - | - | - |
| **Draft** | Created, not activated | No |
| **Live** | Live, delivering to users | Yes |
| **Paused** | Temporarily stopped | No |
| **Archived** | No longer in use | No |

### Changing Status

**To Activate:**

1. Open treatment
2. Ensure all required fields are complete
3. Change status to Live
4. Confirm activation

**To Pause:**

1. Open treatment
2. Change status to Paused
3. Treatment immediately stops delivering

**To Archive:**

1. Open treatment
2. Select Archive option
3. Treatment moves to archived state

### Status Dependencies

For a treatment to actually deliver:

1. Treatment status must be **Live**
2. Parent journey status must be **Live**
3. User must meet guardrails
4. Surface must be active in the app

***

## 5.8 Guardrails

Guardrails control which users can receive a treatment.

### What Are Guardrails?

Conditions that must be true for a user to see the treatment:

* User attribute conditions
* Behavioral conditions
* Contextual conditions

### Example Rules

| Rule | Who Sees It |
| - | - |
| subscription\_tier = "Premium" | Premium subscribers only |
| days\_since\_signup \< 7 | Users who signed up in the last week |
| cart\_items > 0 | Users with items in cart |
| last\_purchase\_days > 30 | Users who haven't purchased in 30+ days |

### Boolean Conditions

Some fields use a **Boolean condition** — a checkbox rather than a value field. This checks whether the field exists or is absent for a given user.

| Checkbox state | Meaning |
| - | - |
| ✅ Checked (true) | The field **has a value** (is set) |
| ☐ Unchecked (false) | The field **has no value** (is null / absent) |

**Common use case:** Targeting users who have never received a specific treatment. Add a Boolean rule on `last_timestamp` and leave it **unchecked** — this matches users with no timestamp record, meaning they haven't seen the treatment before.

### Configuring Rules

Guardrails are typically configured:

* During treatment creation
* Or by selecting from predefined audience segments

> **Note:** Rule configuration options depend on your Console setup. Contact your admin for available rules.

### Testing Rules

Use QA Testing to verify guardrails:

1. Set up QA user with specific attributes
2. Trigger the surface where treatment appears
3. Verify treatment shows/doesn't show correctly

***

## 5.9 Treatment Best Practices

### Naming Conventions

Adopt a consistent naming pattern:

```
[Surface] - [Content Theme] - [Audience] - [Version/Date]
```

Examples:

* "Home - Welcome Back - Returning Users - v2"
* "Checkout - Free Shipping - New Users - Jan 2026"

### Testing Before Launch

1. Use Preview to check content
2. Test with QA users in real app
3. Verify on different devices if applicable
4. Check personalization renders correctly

### Optimization Cycle

1. **Launch** initial treatment version
2. **Monitor** performance for 1-2 weeks
3. **Analyze** metrics (CTR, conversions)
4. **Iterate** based on data
5. **Repeat** the cycle

***

## 5.10 Common Treatment Issues

### Treatment Not Showing

**Checklist:**

* [ ] Treatment status is Live
* [ ] Journey status is Live
* [ ] User meets guardrails
* [ ] Surface is correctly configured
* [ ] No technical delivery issues

### Content Not Rendering Correctly

* Check image URLs are accessible
* Verify personalization fields exist for user
* Test with QA user to isolate issue
* Check treatment type configuration

### Changes Not Appearing

* Allow time for updates to propagate
* Clear any caching in test app
* Verify you saved the changes
* Check you're looking at correct version

***

## Next Section

Continue to [Section 6: Analytics](/guides/comprehensive/analytics) for detailed analytics documentation.