Triggers are a type of Rule within the Loyalty platform. Triggers are used to monitor changes to a Loyalty Member, and to execute a specific action when a specific condition is satisfied.
Triggers contain three main components: the trigger definition, the condition, and the action.
The trigger definition indicates what the platform should monitor. The possible trigger definitions are:
Member performs an activity,
Change in a Member's reward points, or
Change in the Member's tier
When the trigger definition occurs, the platforms checks the condition, which is represented as a logical expression. The trigger action is invoked only if this condition is satisfied.
The action specifies what the platform should do with the condition is met, such as a send a message, grant a Reward, or update a Member Attribute, for example.
Triggers are typically organized into Trigger Groups, which are used to control which Triggers are executed. The platform supports two different types, or "strategies," of Trigger Groups:
Execute only first application rule: Once a Trigger in this Trigger Group is executed, all other Triggers are skipped. For example, if you're using Triggers to send messages, you could put them in the same Trigger Group to avoid sending multiple messages to the same Member.
Execute all applicable rules: All Triggers in this Trigger Group can be executed.
Note: Triggers that execute within one Group have no impact on Actions in another Group.
For more details on how to define a Trigger Group, please see Trigger Action Settings.
To access the Triggered Actions screen, select Rules from the Main Navigation Menu, then select Triggered Actions from the Sub-Category menu.
Within the Triggered Actions screen, all of the Triggers are displayed beneath a sub-heading that indicates the Trigger Group. This sub-heading displays the Trigger Group name, description, and strategy (see above).
The Triggered Actions screen provides the following features:
Searching and Sorting SearchThe search feature allows you to search for a specified text string anywhere within the Trigger's Display Name or Internal Name.
Expand / CollapseWithin the Triggered Actions screen, all of the Triggers are displayed beneath a sub-heading that indicates the Trigger Group. Optionally, you can expand / collapse a Trigger Group by clicking the minus-sign or plus-sign icon next to the Trigger Group name. |
The steps for creating a new Trigger are described below.
Create a New Trigger To create a new Trigger:
Activity ProcessedActivity Processed
Note: If you specify both a new and an old tier, then both options must be satisfied to execute the Triggered Action. If neither option is specified, the platform will execute the Triggered Action upon all tier changes.
Next, you need to define the logical conditions for the Trigger, identify the resulting action that the platform should take when the conditions are met, and set the Trigger's status and effectivity period. See below for more information on these processes. |
Define Trigger Condition The "condition" is used to express the business rules for executing the Trigger . The condition for each Trigger is displayed within the "Condition" column on the Triggered Action screen. To define or edit a condition:
Note: It's important to distinguish which "add" button you want to use (Add Rule or Add Rule Group), and also where the button is located. The smaller plus-sign icon is used to add a single new logical condition. If you have a group within your Triggered Action, you'll see an Add Rule button at the parent level, and also within the group, so be sure you click the right one, depending on where you want to add the new condition. The larger plus-sign icon with a square around it is used to add a new group. This button is available at the parent level, and also within the group (allowing you to create a nested group).
Note: The "condition" for a Trigger consists of only one Rule (potentially with multiple logical conditions contained within it). Unlike when building Segment logic, a Trigger can't have more than one Rule. Attribute TypesThe available attribute types when setting up a Trigger condition are described below. Member Profile -- AttributeMember Profile -- Attribute Compare a Member profile attribute with a specified value (or values) using a mathematical operator. Examples:
Member Profile -- PreferenceMember Profile -- Preference Compare a Member profile attribute with a specified value (or values) using a mathematical operator; includes the ability to handle multiple value preferences. Examples:
Note: The "contains" (and "does not contain") operator behaves differently depending on whether the preference is a single value preference or a multiple value preference. Single value preferences are strings and the "contains" operator does a string contain; that is, it checks if the value is a substring of the preference value. Multiple value preferences are lists and the "contains" operator checks if the list of specified preferences includes the specified value (that is, one of the preference values equals the specified value).
Member FunctionsMember Functions Member Functions provide a mechanism to encapsulate common vertical or program specific expressions into an easy-to-use and understand abstraction. Examples:
Member Metric: ChangeMember Metric: Change Compare the change value for a specified metric. The condition can be specified using one of the following change types:
Examples:
Activity History: FrequencyActivity History: Frequency Compare the count of a specified activity type over a specified time period. Example
Activity History: AggregateActivity History: Aggregate Similar to count but allows an aggregation on a field. To define an aggregate as part of a Segment rule, you must define the following additional information:
Example
|
Define Trigger Action When the conditions of a Trigger are satisfied, the platform will execute the action, or event, associated with the Trigger. To identify what action the platform should execute:
Note: Only one action can be assigned to a Trigger. If you need the platform to perform multiple actions, you need to define separate Triggers for each one. You can then use Trigger Groups to control the relationship between those different Triggers. |
Set Status and Effectivity Period To set the Trigger's status and effectivity period:
Define a New Recurring ScheduleDefine a New Recurring Schedule
To define a new recurring schedule for this item's effectivity:
|
Features relating to managing your existing Triggers are described below.
Deploy Triggered Action Metadata After you've created a Trigger, you must deploy the Triggered Action metadata. If you have changed Triggers in your account that haven't yet been deployed, a warning message is displayed at the top of the Triggered Action screen. In a multi-user account, you could have Triggers created by different users. When you deploy the Triggered Action metadata to the server, the process automatically deploys the metadata for ALL modified Triggers, so you should always verify what Triggered Actions will be deployed before you run the deployment process.
Note: You can deploy metadata immediately, but the best practice is to validate the Triggered Actions logic before deploying metadata to ensure no incorrect expression code gets deployed to the server that could cause issues.
Note: You can also deploy Triggered Action metadata by selecting "Deploy Trigger Rules Metadata" from the "Actions" drop-down menu. |
View Deployed Triggered Action Metadata To see the details of what Trigger metadata has been deployed:
|
Rearrange Triggers The sequence in which the Triggers appear within a Trigger Group controls the sequence in which the platform executes the Trigger. For example, if you have five Triggers within a Group, and that Group is configured to use the "Execute only first applicable rule" strategy, the platform will interrogate the first Trigger in the Group. If that condition fails, the platform will move on to the second Trigger, and so forth. To rearrange the Triggers:
Note: You can't drag-and-drop a Trigger into a different Trigger Group. To change a Trigger's inclusion in a Group, you must edit its properties (see below for more details on this process). |
Edit Trigger Properties To edit the properties of a Trigger:
|
Delete a Trigger To delete a Trigger:
|
Evaluate Expression |
Download JSON To download the underlying JSON code for all Triggers:
|
You can configure triggered actions to send messages via Marigold Engage when processing activities, metric changes, or tier changes. The action "Send Message via Marigold Engage" can be used to configure triggered actions to send messages via Marigold Engage. The trigger will send any configured data that is a part of personalization details of the trigger in a request to Engage to create or update the Engage profile associated with the Loyalty member email address, and leverage the data configured in the trigger to personalize the message sent via Engage.
You can configure personalization details such as member values, metrics, or other activity details in messaging triggers used by Marigold Engage+ without the need for scripting. Users can configure personalization details using selectors as the default process which simplifies and speeds up the configuration process. Users may still use scripting if desired for these messaging triggers by using the Advanced mode.
Personalization details for the below actions include new a new configuration settings dropdown for Type that include Attribute, Metric, Content Token, and Advanced options:
Note: Existing triggers will default to the Advanced Type, and the Name and Value Elements will not be changed.
Last Updated: October 2024