Analytics and revenue

Measure delivery, conversions, and purchases.

Analytics show whether an Experience is reaching customers and leading to the result you want. See how often it’s shown, how many Journeys convert, and what happened during individual visits.

You can use these results to decide what to improve next. A paywall that rarely appears has a different problem from one that gets seen but doesn’t lead to purchases.

Experience metrics

Open the published Experience’s Overview and choose a 7-, 30-, or 90-day range. The delivery chart and totals show:

If Journeys are starting but few screens appear, open Journeys and inspect a run to see which path it took, where it waited, or why it ended. If customers see the Experience but few convert, review the offer, the steps before the goal, and any answers they’ve submitted. These point to different changes: delivery may need attention in the first case, while the content or flow may need work in the second.

Choose a goal that represents the behavior you want. For onboarding, that might be starting a workout after finishing setup. Reaching the last screen doesn’t necessarily achieve that goal, and closing the Experience doesn’t close an attribution window that’s still open.

Goals are optional. You can still see presentation, interaction, and execution activity without one. Events and triggers covers event goals, Segment transitions, and attribution windows.

Journeys and responses

Use Journeys to look behind the totals. Open a run to see its customer, outcome, and timeline of when work began, continued, and ended.

Use Responses to read collected answers and compare submitted with abandoned responses. Completing a response collection is separate from converting the Experience. Someone might finish a survey today and reach its subscription goal later in the window.

App events and revenue

Send events when the app action happens, and include properties that help you understand it. An export_completed event, for example, can include the export format. Nuxie records its own system events for SDK and Experience activity.

For a paywall, set a goal that measures a successful purchase of the relevant Product. Use a purchase-button event only when you want to measure interest in the offer. Purchases and subscriptions explains how store and billing connections keep purchase information current.

Restoring a purchase brings back ownership without creating a new sale, and starting a trial differs from a paid renewal. Choose the outcome you want to measure when configuring the goal.

Store totals can include renewals and purchases that happened outside an Experience. Experience conversions count matching outcomes within the configured window. Those numbers can differ without either being wrong. Feature access is another view: it tells you what the customer can use, rather than how much revenue a visit produced.

If you’re reconciling a Nuxie invoice, see Workspace billing. Its revenue report explains the attributed purchases, adjustments, and fee calculation, which are separate from the conversion count on an Experience chart.

Experiments and investigations

Experiments compare variants using unique exposed customers and the test’s saved metric and guardrails. Because that denominator is people, it differs from the presentation-based rate on an Experience chart.

Ask Nuxie to investigate a result with you. Include the app, Experience, and period you want to compare:

Compare onboarding conversions over the last two weeks. Find where people left, then use our connected analytics to show what they did in the app afterward.

Nuxie can combine Journey history with connected data and use the findings to prepare a screen change or Experiment.