Skip to main content
A post-action reward turns a moment of accomplishment into a gift. The user just did something worth celebrating (finished a purchase, kept a streak alive, hit a level), and your app says congratulations with a premium brand offer: a real perk a brand funds to acquire customers, presented as part of your celebration screen, and you earn a bounty on each server-verified activation. This page is the canonical description of the use case; the integration walkthrough is the Rewarded Actions guide.

​
The moment

The trigger is an achievement your app already detects:
  • A completed purchase: the checkout success or thank-you screen.
  • A milestone or streak: the user’s 7th consecutive day, a finished course, a cleared level, a savings goal reached.
These moments share three properties that make them ideal reward surfaces: the user is in a positive state, the screen is one your app fully controls, and your own code already fires at exactly the right instant, with no detection machinery needed from Encore.

​
The mechanic

The reward is a premium brand offer, paid for by the brand, never by you. A brand funds the perk (a free trial, a discount) as its cost of acquiring a customer; your app supplies the moment and the audience. You render the offer as part of your congratulations UI (“You did it, here’s something on us”), the user claims it by tapping through, and the brand fulfills it on their side. There is no coupon inventory for you to buy and no reward budget for you to hold.

​
The economics

Revenue from this use case lands in the brandOfferRevenue metric: a CPA bounty, paid per verified activation. Two rules govern how it’s counted:
  • A claim is not a conversion. A claim means the user tapped through to the brand. Nothing pays out on a claim.
  • Activation is server-verified. The bounty is earned only when the brand-side completion is verified on Encore’s servers. Your app never attests to a conversion, which is why the economics survive scrutiny.

​
Integration surfaces

The API is the lead surface for this use case: the moment lives in your code, the reward is fulfilled externally by the brand, and the whole flow (feed, delivered confirmation, tokenized claim) is complete over REST with nothing to install.