Skip to main content
Configuration settings control how Auxia Console operates for your organization. This section covers Data Management, Experience Delivery, Company Settings, and UI Layout.

9.1 Configuration Overview

What Can Be Configured?

Accessing Configuration

  1. Click Configuration in the sidebar
  2. Select the configuration area you need

Who Can Configure?

Configuration typically requires admin-level permissions. If you need to change settings, contact your Console administrator.

9.2 Data Management

Data Management controls how user data flows into and is used within Auxia.

Data Fields

See Data Fields in Product Concepts for an overview.
Viewing Data Fields:
  1. Go to Configuration > Data Management
  2. Select Data Fields
  3. Browse available fields
Data Field Properties:

Data Pipelines

See Data Fields in Product Concepts for an overview of data pipelines.
Pipeline Status: Monitor pipeline health:
  • Active: Running normally
  • Warning: Potential issues
  • Error: Data flow interrupted

Data Import

For batch data updates:
  1. Go to Data Management > Import
  2. Upload data file
  3. Map columns to fields
  4. Validate and import
Note: Data pipeline and import configuration is typically handled by technical teams. Contact your admin for data-related changes.

9.3 Experience Delivery

Experience Delivery configures how treatments are delivered to users.

Surfaces

See Surfaces in Product Concepts for an overview.
Viewing Surfaces:
  1. Go to Configuration > Experience Delivery
  2. Select Surfaces
  3. See all configured surfaces
Surface Properties:

Treatment Types

See Treatment Types in Product Concepts for an overview.
Treatment Type Properties: Content Field Configuration: Each treatment type specifies required fields:

Destinations

See Destinations in Product Concepts for an overview.
Destination Properties:
Note: Destination configuration requires technical setup. Contact your admin to add or modify destinations.

9.4 Company Settings

Company settings configure organization-level options.

Goals

Configuring Goals: Goals are business goals tracked in Console:
  1. Go to Configuration > Company
  2. Select Goals
  3. View or manage goals
Goal Properties:

9.5 UI Layout

UI Layout allows customization of Console appearance and screens.

Custom Screens

Some organizations configure custom screens:
  • Dashboard widgets
  • Report views
  • Quick actions

Layout Configuration

Note: UI Layout configuration is advanced and typically handled by admins or during implementation.

9.6 Understanding Your Configuration

Viewing Current Configuration

To understand what’s configured: Data Fields:
  • Configuration > Data Management > Data Fields
  • See all available personalization and targeting options
Surfaces:
  • Configuration > Experience Delivery > Surfaces
  • Know where treatments can appear
Treatment Types:
  • Configuration > Experience Delivery > Treatment Types
  • Understand available formats

Configuration Documentation

Ask your admin for:
  • List of configured data fields and their meanings
  • Available surfaces and their locations in your app
  • Treatment types and their requirements
  • Active integrations and destinations

9.7 Requesting Configuration Changes

What Marketers Can Request

How to Request Changes

  1. Document the need
    • What do you want to accomplish?
    • Why is current configuration insufficient?
  2. Contact your admin
    • Explain the business requirement
    • Provide specific details
  3. Follow up
    • Configuration changes may require technical work
    • Allow time for implementation

Change Request Template


9.8 Configuration Best Practices

For Marketers

Know Your Configuration:
  • Understand available data fields
  • Know your surfaces and treatment types
  • Document what’s available to your team
Work Within Constraints:
  • Use existing configuration when possible
  • Request changes only when necessary
  • Plan ahead for new journeys
Communicate Needs Early:
  • Configuration changes take time
  • Notify admins well before journey launches
  • Provide business context

For Admins

Document Everything:
  • Maintain list of data fields with descriptions
  • Document surface locations
  • Keep treatment type specifications current
Regular Reviews:
  • Audit unused configurations
  • Remove obsolete items
  • Update based on business needs
Change Management:
  • Test configuration changes
  • Communicate changes to users
  • Train team on new capabilities

9.9 Common Configuration Questions

”I need a data field that doesn’t exist”

Steps:
  1. Check if a similar field exists
  2. Document your need
  3. Request from admin/technical team
  4. Data pipeline may need updates

”I want to show treatments in a new location”

Steps:
  1. Verify surface doesn’t already exist
  2. Describe the location in your app
  3. Request surface configuration
  4. Technical integration may be needed

”I need a different treatment format”

Steps:
  1. Review existing treatment types
  2. Describe the format you need
  3. Request from admin
  4. May require template development

”How do I know what data is available?”

Options:
  1. Check Data Fields in Configuration
  2. Ask your admin for documentation
  3. Review existing treatment personalization

9.10 Integration Overview

Common Integrations

Integration Status

Check integration health:
  1. Configuration > Company
  2. View integration status
  3. Green = healthy, Red = issue

Troubleshooting Integrations

If delivery seems broken:
  1. Check integration status
  2. Verify API keys are valid
  3. Contact admin for technical investigation

Next Section

Continue to Section 10: Admin for user and permission management documentation.