What Activity is

Reward Activity is a row-per-send log of every reward delivery in the workspace. It covers both webhook sends (delivery type Reward connection) and manual rewards (delivery type Manual by team), so you have one place to answer “what fired, what failed, what still needs to go out.”

The page header reads Reward Activity with the strapline Track automated sends and complete manual rewards here.

Each row carries the columns When, Reward, Recipient, Delivery, Status, and Response.

The stats row

Four stat cards sit above the table:

• Total: every reward attempt in the current filter set.
• Delivered: the count of sends that ended successfully (or manual rewards that were marked completed).
• Needs fulfillment: manual rewards waiting for the team to mark them completed.
• Failed: webhook sends that the endpoint rejected or did not acknowledge.

The numbers update as you change filters, so they always describe the slice in front of you. An empty workspace shows zeroes across all four cards along with the empty-state row No reward activity yet.

Filtering and search

The filter controls let you narrow the log in several ways.

• Status tabs: All, Needs fulfillment, Delivered, Failed. Tabs are mutually exclusive and sit directly above the table.
• Search: the input in the page header reads Search activity... and matches against reward name, recipient name, recipient email, campaign name, and the response text from the endpoint.
• Delivery: the All delivery dropdown filters to one connection or to Manual by team.
• Date: the Any date dropdown supports Last 7 days, Last 30 days, Last 90 days, plus a custom range.

Sort order: the When, Reward, Recipient, and Status columns are sortable. Click a header to sort, click again to reverse.

Retrying failed sends

Webhook sends that fail can be retried.

• Per-row retry. Each Failed row has an inline Retry action.
• Bulk retry. When failures exist in the current filter set, a Retry all failed (N) button shows above the table. It re-fires only the rows currently visible (so filter first if you only want to retry a subset).

Retries use the snapshotted reward values, not the current catalog. If the reward’s amount has changed since the original attempt, the retry still sends the original amount. The connection URL used is the snapshot too. See Snapshot and history.

Marking manual rewards completed

Rewards with delivery type Manual by team do not fire to a webhook. They appear in Activity with status Needs fulfillment and an inline Mark completed action. Once your ops team has actually sent the swag or unlocked the feature, click the action and the row moves to Delivered.

You can also mark completed from the detail drawer (next section), which is handy when you want to leave a note about how the reward was delivered.

The detail drawer

Clicking any row opens a side drawer with the full record of the send.

The drawer shows:

• Identity: reward name, recipient name and email, status badge.
• Context: campaign, submission, connection (or Manual by team), created at, delivered at, attempt count.
• Payload: the exact JSON that was sent (for webhook sends) or the resolved reward values (for manual rewards).
• Error: the response code and body returned by the endpoint, when the send failed.
• Actions: Retry (for failed webhook sends), Mark completed (for manual rewards).

The drawer is URL-addressable. The browser address bar updates with the send id, so you can paste the link to a teammate and they will open the same drawer.

How soon things show up

A new send shows in Activity within seconds of the submission being approved. Manual rewards show up the moment the approval lands, since there is no webhook step in between.

If you do not see a send you expected:

• The submission may not be approved yet. Activity only logs after the reward triggers, which is after approval.
• The campaign’s reward may be detached. Open the campaign and confirm the platform has a reward attached.
• The reward may not match the platform that produced the submission. Each platform on a campaign attaches to its own reward.

What Activity does not do yet

• No over-time charts. Activity is a row log, not a dashboard. Sends-per-day and cost-by-campaign are out of scope for this version.
• No CSV export. Rows can be sorted and filtered in the UI but not exported.
• No per-recipient deduplication. Each fire creates its own row.

These are intentional scope choices. They may come back as small additive changes if real demand shows up.

Related docs

• Reward catalog: the source of every reward Activity logs.
• Connections: where to repair a connection that keeps failing.
• Snapshot and history: why retries always send the original values.