Analytics

Five endpoints: one shop-wide roll-up, one per-placement breakdown, one revenue ranking, one coverage check, and one all-time total.

All paths are relative to https://aov-post-purchase.firebaseapp.com/public-api/v1. Four of the five take start and end — see Date ranges.

⚠️

These five measure different things and are not interchangeable. The two mistakes that produce wrong numbers are adding per-placement rows into a shop total, and comparing an all-time figure with a dated one. Each section below says which is which.

Summary

GET /data/analytics/summary

Shop-wide roll-up for a date range. Matches the Analytics dashboard.

Parameter	Type	Notes
`start`, `end`	date	`YYYY-MM-DD`, inclusive. Max 90 days. Default: last 30 days

Response

Field	Type	Notes
`totalUpsoldValue`	number	Upsold revenue in the range
`totalUpsoldOrders`	number	Orders that accepted an upsell
`totalOrders`	number	Every order your store took in the range
`upsellSuccessRate`	number	`totalUpsoldOrders` ÷ `totalOrders`
`averageUpsoldValue`	number	Upsold value per upsold order
`offerViews`	number	Offer impressions across all four placements
`currency`	string
`appliedWindow`	object	The window actually used, and whether you chose it

upsellSuccessRate is a share of all orders, not a conversion rate against views. For conversion measured against impressions, use conversionRate from Lifetime, or an offer's acceptanceRate from Top offers.

curl -H "Authorization: Bearer $AOV_TOKEN" \
  "https://aov-post-purchase.firebaseapp.com/public-api/v1/data/analytics/summary?start=2026-08-01&end=2026-08-26"

{
  "success": true,
  "data": {
    "totalUpsoldValue": 12480.75,
    "totalUpsoldOrders": 214,
    "totalOrders": 3180,
    "upsellSuccessRate": 6.73,
    "averageUpsoldValue": 58.32,
    "offerViews": 2905,
    "currency": "USD",
    "appliedWindow": { "start": "2026-08-01", "end": "2026-08-26", "source": "merchant" },
    "shopDomain": "acme.myshopify.com"
  }
}

Stats

GET /data/analytics/stats

One row per placement for a date range.

Parameter	Type	Notes
`start`, `end`	date	Max 90 days. Default: last 30 days
`type`	string	One placement. Omit for all four

Response

Field	Type	Notes
`placements`	array	`placement`, `impressions`, `claims`, and `revenue`
`shopOfferCount`	integer	Offers in the store, any status
`currency`	string
`appliedWindow`	object

⚠️

Do not add these rows into a shop total. They are separate measurements. Post-purchase counts impressions and claims on its first upsell only, while its revenue spans every slot — the columns do not share a denominator. For a shop-wide figure use Summary.

Two absences are deliberate:

Coupon offer rows carry no revenue. A coupon rewards a future order the app cannot attribute back, so the field is omitted rather than reported as 0, which would read as a problem.
shopOfferCount is there to disambiguate zeroes. All-zero rows in a store with 12 offers mean something very different from all-zero rows in a store that has never created one.

Top offers

GET /data/analytics/top

Offers ranked by revenue earned in a date range.

Parameter	Type	Notes
`start`, `end`	date	Max 90 days. Default: last 30 days
`limit`	integer	How many rows. Default `3`
`order`	string	`highest` (default) or `lowest`

Response

Field	Type	Notes
`offers`	array	Offer rows with `revenue`, `claims`, `acceptanceRate`
`shopOfferCount`	integer	Offers in the store, any status
`currency`	string
`appliedWindow`	object

Three things follow from this being built on claim history rather than the offer list:

An offer that earned nothing in the range is absent, not ranked last. To reach those, call /data/offers?sort=revenue_low.
A top earner can be an already-deleted offer. Those rows carry isDeleted: true and no url.
claims and acceptanceRate are facts about that row, not a second ranking. order=lowest still ranks by revenue — and only among offers that earned something.

curl -H "Authorization: Bearer $AOV_TOKEN" \
  "https://aov-post-purchase.firebaseapp.com/public-api/v1/data/analytics/top?limit=5&order=highest"

Coverage

GET /data/analytics/coverage

Which placements have an active offer, and which have nothing running.

Parameter	Type	Notes
`start`, `end`	date	For the revenue column. Default: last 30 days

Response

Field	Type	Notes
`placements`	array	`placement`, `hasActive`, `activeCount`, `totalCount`, `recentRevenue`
`currency`	string
`appliedWindow`	object

totalCount alongside activeCount is what separates "nothing created here" from "offers exist but none are active" — activeCount is 0 in both, and they call for completely different actions.

Coupon offer rows carry no recentRevenue, for the same reason as in Stats.

{
  "success": true,
  "data": {
    "placements": [
      { "placement": "Post-purchase upsell", "hasActive": true, "activeCount": 4, "totalCount": 7, "recentRevenue": 8210.4 },
      { "placement": "Order status page upsell", "hasActive": false, "activeCount": 0, "totalCount": 0, "recentRevenue": 0 }
    ],
    "currency": "USD",
    "shopDomain": "acme.myshopify.com"
  }
}

This endpoint does not enforce the 90-day cap, because its counts are current-state rather than windowed. Only recentRevenue uses the range.

Lifetime

GET /data/analytics/lifetime

All-time totals. No parameters. Matches the Statistics card on Home.

Field	Type	Notes
`totalRevenue`	number	All-time upsold revenue
`offerViews`	number	All-time impressions
`upsoldOrders`	number	All-time orders that accepted an upsell
`conversionRate`	number	`upsoldOrders` ÷ `offerViews` — measured against views
`revenuePerVisit`	number	`totalRevenue` ÷ `offerViews`
`currency`	string

⚠️

These are all-time figures with no window. Never subtract them from a dated result, and never label them as a month or a quarter — the difference between an all-time total and a 30-day total is not "the rest of the time", it is two different measurements.

Because there is no range, this is the endpoint to cache most aggressively. It is also the only way to see beyond 90 days.

Offers Products

Analytics

Summary

Stats

Top offers

Coverage

Lifetime

Related