Skip to main content

​
Important Note

Applies to flow campaigns built on Extole’s upgraded Flow Builder (look for the flow icon next to the campaign name on the Programs page).

​
What you’re trying to do

You want a reward to be issued only when the triggering event carries certain data — for example, only reward when the purchase event includes product_id = SKU-123, or only when product_type = subscription. In Extole this is done with a data-comparison rule that reads a parameter off the incoming
event and compares it to a value. You attach that rule to the reward (or to the business event
that drives the reward) so the reward only issues when the data matches.

​
How rewards and rules fit together

A reward in Flow Builder fires through a chain:
So “trigger a reward on data” means adding a data condition somewhere in that chain. You have a few places to put it, and the choice matters: Event Data Comparison is a Trigger Rule. Reward Rules gate the payout, but they offer no event-data comparison of their own, so the data condition belongs in the reward’s Trigger Rules (Option A). Put it on the business event only when you don’t want the event recorded at all (Option B).
The event is still recorded, and only this reward depends on the data. This is also how you handle one event that can produce more than one reward, where the data decides which reward fires.
  1. If the reward is new, add it from the business event first so it stays attached. Follow How to Add a New Reward. Confirm the new reward appears on that event before you add a data comparison. A data comparison filters events that already reach the reward; it is not the connection to the event.
  2. Go to the Programs page and click the Manage Flow icon for your campaign.
  3. Select the Reward in the flow.
  4. Add a rule under the reward’s Trigger Rules and choose Event Data Comparison.
  5. Configure the comparison:
    • Event Parameter — the business-event data name as it arrives on the event, using underscores instead of spaces (a Product ID is referenced as product_id).
    • Comparison — one of: Equals, Does not equal, Is blank, Is not blank, Contains, Does not contain, Matches Regex, Does not match Regex.
    • Value — the value (or regex) to compare against, e.g. SKU-123.
  6. Give the rule a descriptive name like Trigger only for SKU-123 so it’s easy to read in troubleshooting.
  7. Click Apply to save.
If the reward’s trigger rule fails, this reward does not fire, and other rewards on the same business event — each with their own trigger rule — still can. That is how you route different data values to different rewards on one event.
A reward built before Trigger Rules existed on rewards shows a Reward Entries section in its place, and Reward Entries hold reward entries rather than rules. If the reward you opened has Reward Entries and no Trigger Rules, its routing condition was configured outside Flow Builder — contact Extole support before you change how that reward is triggered.
The parameter must exist as business-event data on the outcome event. If it isn’t there yet, add it first: click into the outcome event → + New Data → Business Event Data, and name it to match the field you send. Then reference it in the reward’s trigger rule as the Event Parameter (spaces → underscores).

​
Example: two rewards on one event, routed by product

  • Reward A → Trigger Rule: Event Data Comparison, Event Parameter product_id, Equals, SKU-123
  • Reward B → Trigger Rule: Event Data Comparison, Event Parameter product_id, Equals, SKU-999
The conversion event fires the matching reward based on the product id it carries.

​
Option B — Suppress the event entirely with a Trigger Rule

Use this when you don’t even want to create the business event unless the data matches (e.g. only record a conversion at all when product_type = subscription).
  1. Programs → Manage Flow → open the business event step (e.g. Converted).
  2. Turn on the advanced filter to reveal Trigger Rules. A business event hides its Trigger Rules until the advanced filter is on; a reward shows its own Trigger Rules either way.
  3. Click to add a Trigger Rule → Event Data Comparison.
  4. Configure Event Data Parameter, Comparison, and Value exactly as in Option A.
  5. Apply.
If the incoming event fails the trigger rule, Extole does not create the business event, so no downstream reward, email, or reporting step happens for it.

​
Prerequisite: the data must actually be on the event

A data rule can only compare a parameter that is sent on the event. Before configuring the rule, confirm your integration includes the field:
  • JS tag / API: include the parameter in the event data, e.g. { "event_name": "conversion", "data": { "product_id": "SKU-123", "cart_value": "129.00" } }.
  • Batch file: include a column for the parameter and map it to event data.
The Event Data Parameter name in the rule must match the parameter name you send, exactly
(names are case/spelling sensitive). If the field isn’t present, Equals will fail and
Is blank will pass.

​
Troubleshooting

  • Reward never issues, even for matching data. Check that the parameter name in the rule matches the parameter you send (spelling/case), and that the value matches the comparison type (e.g. Equals is exact — capitalization and punctuation must match).
  • Reward issues for everything. The data rule may not be on the reward — confirm it’s listed under that reward’s Trigger Rules, not on a different reward or event.
  • Event isn’t even recorded. A Trigger Rule on the business event suppresses the event itself. If you meant to stop only this reward, move the rule to the reward’s Trigger Rules.
  • The reward has no Trigger Rules section. It has Reward Entries instead, which is the older shape described in Option A. Contact Extole support to change how that reward is triggered.
  • List/array field never equals. Switch Equals to Contains or Matches Regex.