Analytics sections
Use filters
Use Date range, Ad network, Account, and Ad campaign to answer specific questions:- What happened after a campaign launch?
- Which ad accounts or campaigns drive paid subscriptions?
- Did a Remote UI change affect subscription conversion?
- Which in-app events changed after a release?
- Are trial starts converting into rebills?
Overview
The Overview section summarizes acquisition, revenue, and subscription performance for the selected date range. Use it when you need a quick read on how users move from ads and installs into paid access. Open it from Analytics → Overview.Subscription funnels
The User Acquisition group shows conversion funnels for the selected cohort:
PNLight shows the trial and direct subscription funnels only when the selected cohort has users in those paths. Each funnel can show renewals 1 through 5 when those events exist.
Conversion percentages compare each step with the previous step, so you can spot where subscribers drop off after the first payment. On smaller screens, PNLight keeps the funnel readable by showing the earlier renewal steps first. Use a wider screen when you want to compare later renewals side by side.
Funnel metrics
ARPPU
The ARPPU section shows cumulative average revenue per paying user for customers who registered in a selected window. Use it to see how a cohort’s monetization matures after acquisition. Open it from Analytics → ARPPU.Filters
- Registrations — selects the cohort. Date presets set inclusive windows such as 30 days, 3 months, 6 months, or 12 months.
- Purchases until — chooses how long to keep counting revenue after the registration window closes. Follow-up presets add 1, 3, 6, or 12 months.
- Ad network, Account, Ad campaign, and Country — restrict the cohort to a traffic source, ad account, or geo.
- View by — buckets the chart and table by day, week, or month. Available options adapt to the selected span.
- Calculate using — switches between Sales and Proceeds. Sales are gross revenue before commissions. Proceeds are net revenue after store and bank commissions.
- Payer base — controls the ARPPU denominator. Running divides each period by payers counted so far. Final divides every period by all payers in the selected window.
- Refunds — controls whether refunded revenue is subtracted. Refunded customers still count as paying users.
Metrics
ARPPU values are cumulative through each row’s period. The caption below each value shows the change from the previous period.
When revenue stops changing, the chart marks the plateau so you can see when the cohort stopped producing new revenue.
How reinstalls affect analytics
When the same SDK user ID installs the app again, PNLight treats the latest recorded install or reinstall as the start of that user’s current analytics period. Dashboard analytics, campaign reports, and cohorts count only events that happened on or after that latest install. Events from earlier installs remain available in Events and customer timelines for debugging, but they are not included in aggregated analytics for the user’s current campaign or cohort.App Events analytics
The App Events section charts SDK events sent withlogEvent. Use it to compare event names, spot release regressions, and inspect recent payloads without leaving the dashboard.
Open it from Analytics → App Events.
Filters
- Date range — restricts the chart and table to events recorded on the selected dates.
- View by — controls the chart bucket size.
- Ad network, Account, and Ad campaign — restrict events to a traffic source.
- Event names — choose which events appear on the chart.
Metrics
Click an event name to open recent event samples. Each sample shows the user ID, timestamp, payload, and a link to the customer profile.
Remote UI analytics
The Remote UI section plots unique-user Requests and Shows for a single placement over time. Use it to see how often a placement is requested by the SDK and how often a config could actually be shown. Open it from Analytics → Remote UI, or from the Remote UI section in the sidebar.Filters
- Placement — choose which Remote UI placement to chart. The first placement is selected by default.
- Date range — restricts the time window for the chart.
Metrics
If the project has no placements yet, the page prompts you to create one first. See Remote UI placements for setup.
Cohorts
The Cohorts section groups users by registration window and tracks the revenue they generate over time. Use it to judge whether a paid acquisition cohort pays back its spend. Open it from Analytics → Cohorts in the dashboard.Filters
- Registration window — pick the start and end dates for the cohort (the users registered in that range).
- Last payment date — the cutoff used when summing revenue from the cohort.
- Country — restrict the cohort to a single geo.
- Ad network and Account — restrict the cohort to a traffic source or ad account.
- Ad campaign — restrict the cohort to users acquired through a specific campaign, organic users, or all users.
Summary metrics
The summary card reports the following for the selected cohort:
When you select a specific campaign, Spend is auto-detected from that campaign for the registration window. You can override it by typing a value into the Spend field.
Weekly ROAS chart
The chart plots cumulative revenue per week. When Spend is set, it converts revenue into ROAS and adds a dashed breakeven line at1.0x:
- The series is grey before breakeven and green after, so you can see at which week the cohort paid back.
- If breakeven is not reached, the chart shows cumulative revenue only and the subtitle reads “Breakeven not yet reached.”
- If Spend is
0, the chart falls back to plotting cumulative revenue.