Treatment Types
A treatment type defines the content structure of a treatment and specifies which surfaces it can appear on.
Custom Configured Content Fields by Default
Treatment types are configured by your team to match your product's UI components and delivery channels. They are not a fixed set of platform-defined formats — your admin defines the treatment types that make sense for your application.
What Treatment Types Control
| Aspect | What It Defines |
|---|---|
| Content fields | Which fields are included and the characteristics of those individual fields, including name, maximum length, whether they are optional or required, and whether they are translatable to different languages |
| Surface compatibility | Which surfaces this type can appear on |
Example Treatment Types
Below are examples of Treatment Types that you could configure within Auxia. Note that all Treatment Types are custom configured, unless they are tied to a specific Destination, in which case the Treatment Type is pre-configured as determined by the specific Destination.
In-App Banner
An inline banner that appears on a designated screen surface. All content fields are custom configured.
| Field | Required | Max Length | Translatable |
|---|---|---|---|
title | Yes | 60 chars | Yes |
body | Yes | 120 chars | Yes |
image_url | No | 2048 chars | No |
cta_text | Yes | 30 chars | Yes |
cta_deep_link | Yes | 2048 chars | No |
Compatible surfaces: HOME_SCREEN, PRODUCT_DETAIL_PAGE, SEARCH_RESULTS
In-App Modal
A full-screen or partial overlay that requires user interaction. All content fields are custom configured.
| Field | Required | Max Length | Translatable |
|---|---|---|---|
headline | Yes | 60 chars | Yes |
body | Yes | 300 chars | Yes |
image_url | No | 2048 chars | No |
primary_cta_text | Yes | 30 chars | Yes |
primary_cta_deep_link | Yes | 2048 chars | No |
secondary_cta_text | No | 30 chars | Yes |
Compatible surfaces: HOME_SCREEN, CHECKOUT_PAGE, ONBOARDING
Push Notification (via Auxia Push Notification Service)
A system-level push notification delivered via the Auxia Push Notification Service Destination. The Treatment Type is pre-configured by the Destination.
| Field | Required | Max Length | Translatable |
|---|---|---|---|
title | Yes | 65 chars | Yes |
body | Yes | 240 chars | Yes |
deep_link | No | 2048 chars | No |
image_url | No | 2048 chars | No |
Compatible surfaces: PUSH_NOTIFICATION
Email (via Auxia Email Service)
A rich HTML email delivered via the Auxia Email Service Destination. The Treatment Type is pre-configured by the Destination.
| Field | Required | Max Length | Translatable |
|---|---|---|---|
subject | Yes | 78 chars | Yes |
preview_text | No | 100 chars | Yes |
body_html | Yes | — | Yes |
cta_text | Yes | 50 chars | Yes |
cta_url | Yes | 2048 chars | No |
Compatible surfaces: EMAIL
Configuration
Treatment types are created and managed in Configuration > UI Layout > Treatment Types. This requires admin permissions.
Related Concepts
- Treatments — every treatment has a treatment type
- Surfaces — treatment types define which surfaces they can appear on
- Destinations — some treatment types are delivered via specific destinations
How-to guides: Configuration