Target Actions
A Target Action is the specific behavior a treatment is designed to drive. It is defined at the treatment level and represents the intended user interaction — the action you want the user to take in response to seeing the treatment.
Target Actions vs. Goals
Target Actions and Goals are related but operate at different levels:
| Concept | Level | Example |
|---|---|---|
| Target Action | Per treatment | "Click the CTA to view the offer details" |
| Goal | Per journey | "Increase purchases" |
A Goal defines the outcome you want to achieve across an entire Journey. A Target Action defines what a specific treatment is asking the user to do. Multiple treatments with different Target Actions can all contribute to the same Goal.
How Target Actions Are Used
When you create a treatment in the Auxia Console, you can optionally specify a Target Action. This tells Auxia what user behavior to associate with that treatment when measuring performance.
Target Actions are used to:
- Report treatment-level engagement — The Analytics dashboards surface how often users completed the Target Action for each treatment.
- Inform model training — When a user completes the Target Action, it is logged as a signal that the treatment was effective for that user.
Defining Target Actions
Target Actions are typically defined as events — the same events that are ingested as Data Fields. For example:
| Treatment | Target Action Event |
|---|---|
| "Complete your profile" banner | profile_completed |
| "Explore new arrivals" CTA | product_page_viewed |
| "Upgrade to premium" modal | subscription_upgraded |
| "Finish your purchase" push notification | purchase_completed |
Related Concepts
- Goals — the higher-level outcome that a journey optimizes toward
- Treatments — the content unit that has a Target Action
- Journeys — the container that links treatments to a goal
- Data Fields — the events used to define and measure Target Actions
- Analytics — where Target Action performance is reported
How-to guides: Managing Treatments