> ## Documentation Index
> Fetch the complete documentation index at: https://docs.extole.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Trigger Events

> A trigger event is the event that starts a business event, reward, or call-to-action in a Flow Builder campaign. Learn where trigger events come from and why each part of a campaign names its own.

# Overview

A trigger event is the event that starts something in a Flow Builder campaign: a business event such as Shared or Converted, a reward, or a call-to-action. Each of these names its trigger event in a setting called **Triggered By**, so you can see at a glance what makes each part of your campaign happen.

Before Triggered By, that connection lived inside trigger rules. To know why a reward fired, or why it didn't, you had to read the rules. Now the answer is on the reward itself.

## Where Trigger Events Come From

* **Your campaign**: shares, share link clicks, sign-ups from the landing page, ambassador applications, and the campaign's own business events. These connect automatically when you create a campaign.
* **Your systems**: events your backend sends to Extole through the API, events you send in a file, and events your website or mobile app produces when it requests a zone or fires a tag. You declare each of these once, and any campaign can then select it.
* **Partner integrations**: trigger events from a partner integration appear alongside your own and are selected the same way.

When you create a campaign, Extole looks for the trigger events it expects among the ones you've declared and selects them for you. Declaring your events before you build a campaign means it's ready to publish on the first try.

## Trigger Events and Trigger Rules

Trigger events and [trigger rules](https://docs.extole.com/guides/flow-campaigns/common-trigger-rules.md) are related but distinct:

* **A trigger event** decides *which* event starts a business event, reward, or call-to-action. For example, a friend's Converted business event starts when your backend reports a `conversion`.
* **A trigger rule** decides *whether* a particular occurrence of that event counts. For example, count the conversion only when it's for a subscription, or only when the friend signed up first.

Together they make each business event, reward, and call-to-action start on the right event and count only the occurrences that qualify.

## Why It Matters

* **See how your campaign is wired.** Every business event, reward, and call-to-action names what starts it, so reviewing a campaign or handing it to a teammate doesn't mean decoding its rules.
* **Connect your own events without a custom build.** Events from your backend, your files, your website, and your app become choices you select, not rules someone has to write.
* **Change what earns a reward by choosing a different event.** Pointing a reward at a different business event is a selection, not a rule edit.
* **Catch gaps before launch.** A campaign won't publish while a business event, reward, or call-to-action that needs a trigger event has none, or points at one that no longer exists. A reward or business event that would never fire is caught before your customers ever see the campaign.

## Good to Know

* **Existing campaigns keep working.** Campaigns created before Triggered By don't show the setting and continue to run as they always have. Contact your Extole team about upgrading one.
* **A reward can be earned by more than one event, with a trade-off.** When a reward lists several trigger events, any of them can earn it, but the reward no longer records which event earned it in dashboard data and no longer creates the advocate–friend relationship. Both require a single trigger event.
* **Some events still use trigger rules.** Events that My Extole sends itself, such as an ambassador's application being reviewed, and events tied to opening a link or page, such as the landing page and share experience, don't show a Triggered By setting.

## Related

* [How to Set Up Triggered By](https://docs.extole.com/guides/flow-campaigns/how-to-set-up-triggered-by.md)
* [Common Trigger Rules](https://docs.extole.com/guides/flow-campaigns/common-trigger-rules.md)
* [Events Overview](https://docs.extole.com/product/product-overview/events/events-overview.md)
* [Javascript SDK and Mobile SDK Extensions](https://docs.extole.com/technical/platform-integrations/extensions/javascript-sdk-and-mobile-sdk-extensions.md)


## Related topics

- [Terms You Should Know](https://docs.extole.com/product/extole-overview/terms-you-should-know.md)
- [Common Trigger Rules](https://docs.extole.com/guides/flow-campaigns/common-trigger-rules.md)
- [Send Event](https://docs.extole.com/api-reference/feature-specific/api-event/send-event.md)
- [Map Partner Events to Business Events](https://docs.extole.com/technical/building-partner-integrations/integration-types/partner-events-map-to-business-events.md)
- [How to Set Up Business Event Rules](https://docs.extole.com/guides/flow-campaigns/how-to-set-up-business-event-rules.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.