Destinations
Auxia supports two integration patterns:
- Pull-based: Your application calls Auxia's APIs or SDKs in real time when a user visits a surface. Auxia selects and returns the appropriate treatment for that request.
- Push-based: Auxia initiates decisions based on triggers or scheduled jobs, then delivers treatments to users without a real-time request from your application.
For pull-based integrations, you interact directly with Auxia APIs or SDKs.
For push-based integrations, Auxia delivers treatments through Destinations. A Destination is a delivery channel configuration that connects Auxia to the system responsible for sending treatments (for example, email, push notifications, or SMS).
Destinations are intended for out-of-product channels. They should not be used for in-product surfaces.
Destination Properties
| Property | Description |
|---|---|
| Name | Identifier for the destination |
| Channel | The delivery channel this destination uses (e.g., push, email, SMS). This is a property of the destination itself — it is separate from Treatment Types, which define the content fields and surfaces for a treatment. When you associate a destination with a treatment type, the treatment type's configuration determines what content fields are required for that delivery channel. |
| Status | Whether the destination is ACTIVE or INACTIVE in the console |
| Configuration | API credentials, webhook URLs, and channel-specific settings |
Destination Configuration
Destinations require technical setup involving API keys and integration configuration. They are managed in Configuration > Experience Delivery > Destinations and require admin permissions.
For integration-specific setup guides, see:
Destination → Treatment Type Workflow
The standard workflow is:
- Create a Destination in Configuration > Experience Delivery > Destinations — configure the delivery channel (credentials, endpoint, etc.)
- Associate the Destination with a Treatment Type in Configuration > UI Layout > Treatment Types — this links the delivery channel to the content structure that treatments will use
After creating a destination, you associate it with one or more treatment types. This association is what enables Auxia to know both what content to send (defined by the treatment type) and where to send it (defined by the destination).
Examples
| Destination | Channel | What It Delivers |
|---|---|---|
| Auxia Push Notification Service | Push | Mobile push notifications (Auxia-native) |
| Auxia Email Service | Rich HTML emails (Auxia-native) | |
| Braze | Multi-channel | Push notifications, email, SMS |
| Customer.io | Rich HTML emails | |
| Salesforce Marketing Cloud | Rich HTML emails | |
| Webhook | Any | A generic HTTP callback mechanism — not a specific platform. Webhooks can be used to connect Auxia to any custom system or destination not listed above. |
Related Concepts
- Treatments — treatments are delivered via a destination
- Treatment Types — treatment types are associated with destinations to define content structure per channel
- Surfaces — the surface defines where the treatment appears after delivery
How-to guides: Configuration · Delivery Integrations