Revenue per user
GET /publisher-dashboard/user-analytics
See where your revenue per user comes from: by day, new and returning users, usage, ad load, country, signup week, and your own user tags. Every publisher can call this route.integer
default:"30"
The number of days to look back, from 1 to 365. Or send
start_date and end_date (YYYY-MM-DD).string
Comma-separated ISO country codes, or
unknown. At most 20 countries.string
Comma-separated:
new, returning.string
Comma-separated usage groups:
under_10, 10_24, 25_49, 50_99, 100_plus (requests per active day).Each segment row has
segment, users, user_days, impressions, clicks, ctr, arpu, arpdau, and revenue_share.Request
Agreement statements
These routes return the monthly statement of a qualifying-request agreement. They exist only for publishers on that kind of agreement. For any other key, they return404.
Both take month (any date in the month, YYYY-MM-DD; the default is the current month) and tz (an IANA time zone, default UTC). A bad month or tz returns 400. A future month returns 404. Amounts that end in _microdollars are in millionths of a dollar.
GET /publisher-dashboard/qualifying-requests
Get the qualifying requests, rate, tier, and earnings of one month.accrued_minimum_microdollars is the minimum for the days of the month that the agreement covers, not a full month. earned_month_to_date and earned_today are in dollars.Response
GET /publisher-dashboard/proven-ad-value
Get the Publisher Attributable Value (PAV) of one month, by conversion event. Gravity uses the same calculation for the monthly reconciliation. This route is available only when your agreement shows PAV to you.types always lists every conversion event of the agreement’s rate card, in the agreement’s order, including events with a zero value. provisional is true until the month is over, because conversions can still arrive.Response