Reward Transactions Table Overview
The Transactions section in Ambassador 3 is your command center for everything reward-related — from the moment a reward is created all the way through fulfillment, redemption, and expiration. This article explains how the table works and what every status means. 💰
Where to Find It
Navigate to Rewards & Payments → Transactions in your Ambassador admin.
What's in the Transactions Section?
The Transactions section has atleast 3 tables:
Rewards — A table of every reward created in your program, showing its current status, the advocate it belongs to, the campaign it's tied to, and the fulfillment method used. This is where you can manually approve, deny, or fulfill rewards.
Redemptions — A log of every attempt by an advocate to redeem an approved Storefront, Portal, or Tango Choice Product reward. Each line item shows what they tried to redeem, which vault it came from, and whether it succeeded.
Ledger — A full audit trail of every action taken on a reward after it's been fulfilled. Each entry in the Ledger represents a status change, creating a complete timeline of the reward's lifecycle.
If you have Loyalty enabled, you'll find a fourth table for Recognition, which logs your loyalty transactions for tasks and badges.
Reward Status Key
Every reward in the Rewards table has a Status that tells you where it is in its lifecycle:
| Status | What it means |
|---|---|
| PENDING | The reward has been created and is waiting for approval or denial |
| FLAGGED | The reward is flagged because the associated contact is flagged. It can be reverted to PENDING, or moved to APPROVED or DENIED |
| APPROVED | The reward was approved — either manually by a team member or automatically via an Automation |
| DENIED | The reward was denied — either manually or automatically by an Automation or Reward Rule. Can be reverted to PENDING |
| PROCESSING | A temporary status when a bulk update is running or an external system request is taking longer than expected |
| FULFILLED | An approved reward has been sent to the advocate via a fulfillment method. Once fulfilled, a Ledger entry with status POSTED is created |
| EXPIRED | A Portal or Storefront reward expired before the full balance was redeemed |
| FULFILLMENT FAILED | A fulfillment attempt failed due to a Payment Vault policy, insufficient inventory (e.g., coupon codes), or an external system error (e.g., insufficient Tango funds) |
Redemption Status Key
For Storefront, Portal, and Tango Choice Product rewards, each redemption attempt by an advocate creates a line item in the Redemptions table:
| Status | What it means |
|---|---|
| PROCESSING | A temporary status while the system awaits a response from the vendor or payment vault |
| CANCELLED | The redemption was cancelled by the advocate or a company user before it completed |
| FAILED | The redemption attempt failed — due to a Payment Vault policy, insufficient inventory, insufficient funds, or another requirement not being met. Click the line item to see the specific error message |
| COMPLETED | The redemption was successful |
Tip: To find the redemption status for a Storefront, Portal, or Tango Choice Product reward, look for the Ledger Status column in the Rewards table, or click into the reward line item and select the Redemptions tab.
Ledger Status Key
Once a reward is fulfilled, the Ledger table begins tracking every subsequent action. Each entry has a Ledger Status:
| Status | What it means |
|---|---|
| POSTED | The initial entry created when a reward is fulfilled |
| REDEEMED PARTIAL | A portion of the reward's balance has been redeemed |
| REDEEMED FULL | The full balance has been redeemed |
| EXPIRED PARTIAL | Some of the reward balance expired before redemption (Storefront and Portal Rewards only) |
| EXPIRED FULL | The full reward balance expired before being redeemed |
| REVOKED | A fulfilled reward was revoked before it was redeemed |
| REDEEM REVERSED | A previously completed redemption was reversed |
Note: Rewards fulfilled via Direct Payment or External Fulfillment are automatically logged with a Ledger Status of REDEEMED FULL since there is no separate redemption step to track.
Good to Know
- You can manually approve, deny, or fulfill individual rewards directly from the Rewards table — or use bulk actions and CSV imports for larger updates.
- Automations can handle all of these status changes automatically — approving rewards when triggers fire, fulfilling them with a specific method, and sending communications in the same workflow.
- If a fulfillment fails (FULFILLMENT FAILED), check the Rewards table line item for the error details and address the root cause (e.g., refill your Tango balance or upload new coupon codes) before retrying.
- Related articles: Fulfillment Methods Overview, Reward Rules Overview & Setup, Payment Vault Overview & Setup, Automations Overview