Reporting

Reporting API returns a partner-level report as a flat array of rows. Each row represents one combination of your requested grouping dimensions (an offer, a day, or both), with the metric columns requested attached to it. For technical details you can refer to the API reference.

​

Metrics reference

Columns fall into three families.

• Engagement metrics: plain counts and totals.
• Retention: Cohorted data (Resets per window).
• ROAS: Cohorted data (Cumulative).

​

Engagement

​

Retention (Resets per window)

​

ROAS (Cumulative)

​

Cumulative vs. resetting

The two windowed families look alike — both come in day 1/3/7/14/30 flavors — but read them differently when reporting or charting. ROAS is cumulative Each window includes every prior one. day_30_roas already contains the revenue counted in day_1_roas, day_7_roas, and so on — it’s running total ÷ spend, measured further and further out. Later windows are always greater than or equal to earlier ones for the same cohort. day_1: 0.12 → day_7: 0.31 → day_30: 0.50 Retention is not cumulative Each window is an independent snapshot: the share of the cohort that came back on that specific day, not the share that came back at any point up to it. day_30_retention does not include the users counted in day_1_retention — it can be lower, higher, or unrelated. day_1: 0.42 → day_7: 0.18 → day_30: 0.09