> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-automate/18.latest/add-ons/engage/triggers.md).

# Triggers

The Engage add-on contributes the following triggers.

## A/B Test Triggers

| Display Name           | Alias                              |
| ---------------------- | ---------------------------------- |
| A/B Test Saved         | `umbracoEngage.abTestSaved`        |
| A/B Test Scheduled     | `umbracoEngage.abTestScheduled`    |
| A/B Test Started       | `umbracoEngage.abTestStarted`      |
| A/B Test Stopped       | `umbracoEngage.abTestStopped`      |
| A/B Test Variant Saved | `umbracoEngage.abTestVariantSaved` |

## Session and Pageview Triggers

| Display Name        | Alias                             |
| ------------------- | --------------------------------- |
| New Session Started | `umbracoEngage.newSessionStarted` |
| Pageview Extracted  | `umbracoEngage.pageviewExtracted` |

## Personalization and Segment Triggers

| Display Name                  | Alias                                       |
| ----------------------------- | ------------------------------------------- |
| Applied Personalization Saved | `umbracoEngage.appliedPersonalizationSaved` |
| Segment Saved                 | `umbracoEngage.segmentSaved`                |
| Segment Deleted               | `umbracoEngage.segmentDeleted`              |

## Customer Journey Triggers

| Display Name                              | Alias                                                   |
| ----------------------------------------- | ------------------------------------------------------- |
| Customer Journey Group Saved              | `umbracoEngage.customerJourneyGroupSaved`               |
| Customer Journey Step Scored              | `umbracoEngage.customerJourneyStepScored`               |
| Customer Journey Step Explicitly Assigned | `umbracoEngage.customerJourneyStepExplicitScored`       |
| Customer Journey Step Assignment Removed  | `umbracoEngage.customerJourneyStepExplicitScoreRemoved` |

## Persona Triggers

| Display Name                | Alias                                       |
| --------------------------- | ------------------------------------------- |
| Persona Group Saved         | `umbracoEngage.personaGroupSaved`           |
| Persona Scored              | `umbracoEngage.personaScored`               |
| Persona Explicitly Assigned | `umbracoEngage.personaExplicitScored`       |
| Persona Assignment Removed  | `umbracoEngage.personaExplicitScoreRemoved` |

## Goal and Campaign Triggers

| Display Name               | Alias                                   |
| -------------------------- | --------------------------------------- |
| Goals Saved                | `umbracoEngage.goalsSaved`              |
| Custom Goal Completed      | `umbracoEngage.customGoalCompleted`     |
| Client-Side Goal Completed | `umbracoEngage.clientSideGoalCompleted` |
| Campaign Group Saved       | `umbracoEngage.campaignGroupSaved`      |

{% hint style="info" %}
Each Engage trigger emits details about the entity it fired on. Inspect a real run in the **Runs** view to see the exact field names, then use the binding picker to reference them in downstream steps.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.umbraco.com/umbraco-automate/18.latest/add-ons/engage/triggers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.