Skip to main content
Analytics is server-side. These reads use the secret Org-API-Key on your backend only - never ship it in an app or client code. A request with a member token is rejected with 403. See Authentication and Server-side API.
Three read-only endpoints roll up your program’s activity: a program-wide summary, per-offers performance, and a timeseries bucketed over a window. All require the Org-API-Key.

Summary

analyticsSummary() calls GET /v1/analytics/summary and returns program-wide totals plus a redemption status-count breakdown.
curl
number
required
Total members in the program.
number
required
Total points ever minted across the program.
number
required
Total points ever spent across the program.
number
required
Share of redemptions that reached completion.
RedemptionStatusCounts
required
A breakdown of redemptions by status (see below).

Redemption status counts

redemptions counts every redemption by its lifecycle status, plus a total: All values are numbers.

Offers

analyticsOffers() calls GET /v1/analytics/offers and returns one OfferAnalytics row per offer.
curl
OfferAnalytics[]
required
Per-offer performance rows.
Each OfferAnalytics row:

Timeseries

analyticsTimeseries({ from, to, interval }) calls GET /v1/analytics/timeseries and returns buckets over a window. All three query parameters are required.
string
required
Start timestamp of the window (inclusive). The first bucket begins here.
string
required
End timestamp of the window. The last bucket ends here.
string
required
The bucket granularity - how the window between from and to is divided into buckets (for example by day or by hour).
curl
TimeseriesBucket[]
required
One entry per interval bucket across the window.
Each TimeseriesBucket:
from and to are timestamps bounding the window; interval is the bucket granularity that divides it. Omitting any of the three is an error - all are required.

In code

The server client is constructed with the Org-API-Key. analyticsSummary, analyticsOffers, and analyticsTimeseries are all called on it.

Next steps

Members and tiers

The per-member counterpart: profiles, wallet, and redemption counts.

Points and wallet

How pointsMinted and pointsSpent are generated.