placement() ·
show().
Pass useCase: 'rewardUsers' on every reward placement. A placement without it is a
'reduceChurn' placement, whose claim waits for
redeem()
(The Claim Flow). A claimed result carries the offer,
the campaign, the advertiser’s name, and, when its write succeeded, the transactionId that
carries attribution:
Placement ids and options
The placement id is attributed on the offers request. The second argument carries the per-presentation options:placement().
Restyling the sheet beyond this is advanced configuration, covered in Advanced UI.
Results are not conversions
Aclaimed result means the presentation succeeded and the user claimed an offer. Advertiser
completion happens later, asynchronously, and is verified on Encore’s side. Never gate real
access on a client-side result.
Optional: get notified when the conversion lands
Because the conversion is verified later and on Encore’s side, the browser never learns about it. If your server needs to react (grant a reward, credit a balance, mark a task done), you can have EncorePOST an offer_completed event to a URL you own the moment a
completion is verified.
This is entirely optional. Nothing above depends on it, and a Web SDK integration is
complete without it. Add it only when you have server-side work to do on completion.
userId is the value you passed to
identify(), echoed back verbatim (the usr_…
above is just a sample placeholder, not a shape Encore imposes), so call identify() or the
id won’t resolve to a user in your database. And delivery is at-least-once: a failed
delivery is retried up to five times over roughly nine hours, so credit the user once per
transactionId and return 2xx only once the credit is committed.
Full contract (headers, payload, signature verification, delivery guarantees):
Offer Completed Webhook.
Don’t confuse this with
Webhook Ingestion, which runs the
opposite direction: there, you POST your own subscription lifecycle events into
Encore for incrementality measurement. This section is about Encore calling your server.
Next steps
- Configure Analytics: forward your subscription events so Encore can measure offer impact
- Post-Purchase Placements: per-call headline and subheadline copy for a reward moment
- Reduce Churn at the Paywall: the other use case, a save attempt at a paywall
- Integration Patterns: handling results in app code
- Offer Completed Webhook: optional server-side notification when a completion is verified
- SDK Reference: every method’s contract