Skip to main content

Section 1: Introduction

Welcome to the comprehensive user guide for Auxia Console. This manual provides detailed documentation of every feature, workflow, and configuration option available in the Console.

About This Guide

This comprehensive manual is designed for:

  • Marketers who want deep understanding of all Console features
  • Power users who need reference documentation
  • New team members learning the full system
  • Admins configuring Console for their organization

Estimated reading time: 2-3 hours (full read) or use as reference


1.1 About Auxia

What is Auxia?

Auxia is an agentic marketing platform that enables personalized customer experiences at scale. Using AI and machine learning, Auxia helps businesses deliver:

  • The right message - Content tailored to each user
  • To the right person - Based on user attributes and behavior
  • At the right time - When users are most receptive
  • In the right place - On the optimal channel and surface

Key Capabilities

CapabilityDescription
Treatment OrchestrationCreate, manage, and deliver personalized messages
Journey ManagementCoordinate treatments into cohesive journeys
Real-time PersonalizationDeliver experiences based on live user context
AI-Powered OptimizationAutomatically improve performance using ML
Multi-Channel DeliveryReach users via push, in-app, email, and more
Advanced AnalyticsMeasure impact with uplift analysis

How Auxia Works

User Activity

[Auxia Platform]
├── Receives user context (attributes, behavior, location)
├── Evaluates guardrails
├── Selects optimal treatment using ML
└── Delivers personalized experience

User Sees Treatment

Action Tracked → Analytics Updated

1.2 Auxia Console Overview

What is Auxia Console?

Auxia Console is the web-based administration interface for the Auxia platform. It's where marketers and admins:

  • Create and manage treatments (personalized content)
  • Organize treatments into journeys
  • Analyze performance and measure business impact
  • Configure delivery channels and targeting rules
  • Manage users and permissions

1.3 System Requirements

Browser Support

Auxia Console is optimized for modern web browsers:

BrowserMinimum VersionRecommended
Google Chrome90+Latest
Mozilla Firefox88+Latest
Microsoft Edge90+Latest
Safari14+Latest

Screen Resolution

ResolutionExperience
1920x1080Optimal
1366x768Good
1280x720Minimum recommended
Below 1280May require scrolling

Network Requirements

  • Stable internet connection
  • HTTPS access to Console URL
  • No specific bandwidth requirements (standard web application)

Accessibility

Auxia Console supports:

  • Keyboard navigation
  • Screen reader compatibility
  • Configurable color themes

1.4 Core Concepts & Terminology

Understanding these concepts is essential for using Auxia Console effectively.

Treatment

A treatment is a single piece of personalized content delivered to a user.

Examples:

  • Push notification with personalized offer
  • In-app banner with product recommendation
  • Email with tailored content
  • Modal with special promotion

Key attributes:

  • Belongs to a journey
  • Has a treatment type (format)
  • Appears on specific surfaces
  • Contains customizable content
  • Can have guardrails

Journey

A journey is a coordinated set of treatments working toward a common goal.

Types:

TypeDurationUse Case
EvergreenOngoing (no end date)Always-on engagement
BurstTime-limitedPromotions, limited-time offers

Goal

A goal is a measurable business outcome you want to achieve.

Examples:

  • Increase purchases
  • Boost app engagement
  • Reduce churn
  • Drive sign-ups

Surface

A surface is a location in your application where treatments can appear.

Examples:

  • Home screen
  • Product detail page
  • Checkout page
  • Search results
  • Push notification tray

Treatment Type

A treatment type defines the format and structure of a treatment.

Examples:

  • Banner (horizontal strip)
  • Modal (overlay popup)
  • In-app message (notification style)
  • Push notification
  • Email

Guardrail

An guardrail defines conditions that determine which users can receive a treatment.

Example rules:

  • User signed up in the last 7 days
  • User is in the "Premium" tier
  • User has items in cart
  • User is located in specific region

Data Field

A data field is a variable containing user or contextual information used for personalization and targeting.

Types:

  • User attributes: Demographics, preferences, status
  • Behavioral signals: Actions, history, patterns
  • Contextual data: Time, location, device

Destination

A destination is a delivery channel configuration (e.g., Braze for multi-channel delivery, Salesforce Marketing Cloud for email).


1.5 User Roles & Permissions

Auxia Console uses role-based access control. Common roles include:

Standard Roles

RoleCapabilities
ViewerView treatments, journeys, analytics
EditorCreate and edit treatments and journeys
AnalystFull analytics access, Agent and AI Insights
AdminAll capabilities plus user management

Note: Your available features depend on your assigned permissions. Contact your admin for access changes.


1.6 Navigation Overview

Top Navigation

ElementFunction
Project SelectorSwitch between projects
Language SelectorChange interface language
User MenuProfile, settings, logout

The sidebar provides access to all Console sections:

├── Home
├── Treatments & Journeys
│ ├── Treatment Portfolio
│ ├── Journey Portfolio
│ └── QA & Testing
├── Analytics
│ ├── Goal Analytics
│ └── Journey Analytics
├── Agent and AI Insights
├── Configuration
│ ├── Data Management
│ ├── Experience Delivery
│ ├── Company
│ └── UI Layout
├── Admin
│ └── Users & Roles
└── Migration Assistant
├── Onboarding
└── Treatment Migration

1.7 Getting Help

In-Console Help

  • Info Icons: Click for contextual tooltips
  • Agent and AI Insights: Ask questions about your data
  • Onboarding Center: Guided tours and videos (if enabled)

External Resources

  • Auxia representative Manager: Your primary Auxia contact
  • Support: Contact via your Auxia representative
  • Documentation: docs.auxia.io (technical documentation)

Next Sections

Continue to the next sections for detailed coverage of each feature area: