Skip to main content
Analytics helps you understand app performance after the SDK and App Store integration are connected.

​
Analytics sections

SectionWhat it shows
OverviewHigh-level app performance for the selected date range.
ClicksAcquisition click activity.
InstallsApp installs recorded by PNLight.
RevenueRevenue from purchases and subscriptions.
SpendAcquisition spend.
New trialsTrial starts during the selected period.
New subscriptionsNew paid subscriptions.
Trial cancellationsTrials where renewal was canceled.
Trial conversionsTrials that converted to paid access.
ARPPUAverage revenue per paying user.
RebillsSubscription renewals after the first payment.
CohortsRevenue and ROAS for users registered in a chosen window.
App EventsEvent volume, users, trends, and recent event samples for SDK events.
Remote UIRequests and shows over time for a Remote UI placement.
FunnelConversion steps across the app and purchase flow.

​
Use filters

Use date, ad network, and campaign filters to answer specific questions:
  • What happened after a campaign launch?
  • Which 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?
The Rebills and Cohorts sections also support a country filter, so you can isolate performance for a single geo.
Compare analytics only after you confirm the SDK token, App Store integration settings, and campaign settings belong to the same project.
For raw event debugging across all users, use Events. Analytics focuses on trends and aggregates.

​
App Events analytics

The App Events section charts SDK events sent with logEvent. 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 time window for the chart and table.
  • View by — controls the chart bucket size.
  • Ad campaign — restricts events to users attributed to a campaign.
  • Event names — choose which events appear on the chart.

​
Metrics

MetricDefinition
Event countTotal events with that name in the selected period.
% of eventsShare of all selected-period events represented by that event name.
UsersUnique users who sent the event.
Events per userEvent count divided by users.
DeltaChange compared with the previous equivalent period.
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

MetricDefinition
RequestsUnique users who requested the placement in each bucket.
ShowsUnique users who received a config that could be shown in each bucket.
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 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:
MetricDefinition
Total usersAll users registered in the cohort window.
ARPPUAverage revenue per paying user (revenue divided by paying users).
RevenueTotal revenue after store commission, up to the last payment date.
ROASReturn on ad spend, calculated as Revenue ÷ Spend.
Autorenewal ONUsers whose subscription has autorenewal enabled.
Active subscriptionsUsers whose latest rebill succeeded.
SpendThe ad spend used in the ROAS calculation.
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 at 1.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.