Section 5: Treatments
Treatments are the core building blocks of your marketing in Auxia. This section covers everything you need to know about creating, managing, and optimizing treatments.
5.1 What is a Treatment?
A treatment is a personalized message or experience delivered to a user. Each treatment consists of:
- Content: What the user sees (text, images, CTAs)
- Format: How it's displayed (treatment type)
- Placement: Where it appears (surface)
- Targeting: Who sees it (guardrails)
- Context: When it's shown (journey assignment)
Treatment Examples
| Treatment | Type | Surface | Goal |
|---|---|---|---|
"Welcome back, ${name}!" | In-app message | Home screen | Re-engagement |
| "Items in your cart" | Push notification | Mobile | Cart recovery |
| "New arrivals just for you" | Inbox | Purchases | |
| "Complete your profile" | Modal | Profile page | Activation |
5.2 Treatment Portfolio
The Treatment Portfolio is your central hub for managing all treatments.
Accessing Treatment Portfolio
- Click Treatments & Journeys in the sidebar
- Select Treatment Portfolio
Portfolio View
The portfolio displays:
| Column | Description |
|---|---|
| Name | Treatment name |
| Journey | Parent journey |
| Type | Treatment type (banner, modal, etc.) |
| Status | Active, Paused, Draft |
| Created | Creation date |
| Modified | Last modification date |
Filtering Treatments
Use filters to find specific treatments:
| Filter | Options |
|---|---|
| Status | Active, 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.3 Creating a Treatment
Treatment creation uses a 4-step wizard.
Starting Creation
- Navigate to Treatment Portfolio
- 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
- 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:
- Place cursor where you want the variable
- Look for the "Insert Variable" option or icon
- Select from available data fields
- The placeholder will be inserted
Available personalization options depend on your configured data fields.
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: 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
Creating the Treatment:
- Click Create Treatment
- Treatment is saved in Draft status
- Navigate to activate or continue editing
5.4 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:
- Pause the treatment first (if major changes)
- Make your changes
- Preview the changes
- Reactivate when ready
Version Selector
For treatments with multiple versions:
- Open treatment details
- Look for the version selector dropdown
- Select version to view
- Compare versions if needed
5.5 Treatment Preview
Preview lets you see how treatments will appear before activation.
Accessing Preview
- Open treatment from portfolio
- Click Preview button
- 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.6 Bulk Upload
Bulk Upload lets you create multiple treatments at once via CSV file.
Accessing Bulk Upload
- Go to Treatment Portfolio
- Click Bulk Upload button (or tab)
Bulk Upload Process
Step 1: Download Template
- Click "Download Template"
- Template includes all required columns
- 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
- Click "Upload" or drag-and-drop
- System validates the file
- Review validation results
Step 4: Review & Create
- Review the treatments to be created
- Fix any validation errors
- 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.7 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
- During treatment creation (Step 3)
- Look for the Sparks panel or icon
- Review suggestions
- 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:
- Clicking thumbs up/down on suggestions
- Using the feedback dialog
- Noting which suggestions were helpful
Note: Sparks availability depends on your Console configuration.
5.8 Treatment Status Management
Status Definitions
| Status | Meaning | Visible to Users |
|---|---|---|
| Draft | Created, not activated | No |
| Active | Live, delivering to users | Yes |
| Paused | Temporarily stopped | No |
| Archived | No longer in use | No |
Changing Status
To Activate:
- Open treatment
- Ensure all required fields are complete
- Change status to Active
- Confirm activation
To Pause:
- Open treatment
- Change status to Paused
- Treatment immediately stops delivering
To Archive:
- Open treatment
- Select Archive option
- Treatment moves to archived state
Status Dependencies
For a treatment to actually deliver:
- Treatment status must be Active
- Parent journey status must be Active
- User must meet guardrails
- Surface must be active in the app
5.9 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 |
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:
- Set up QA user with specific attributes
- Trigger the surface where treatment appears
- Verify treatment shows/doesn't show correctly
5.10 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
- Use Preview to check content
- Test with QA users in real app
- Verify on different devices if applicable
- Check personalization renders correctly
Optimization Cycle
- Launch initial treatment version
- Monitor performance for 1-2 weeks
- Analyze metrics (CTR, conversions)
- Iterate based on data
- Repeat the cycle
5.11 Common Treatment Issues
Treatment Not Showing
Checklist:
- Treatment status is Active
- Journey status is Active
- 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 for detailed analytics documentation.