Analytics

Use Analytics in the sidebar to see how your screens perform on your live site: how many people saw each screen, how many tapped a purchase button and how many bought. For onboarding screens and surveys it also shows which buttons people pressed and which answers they chose.

The numbers come from events that the Web SDK sends from your visitors' browsers. Anyone with Viewer access to the project can read the page.

FiltersCopy Anchor Link

Two controls sit at the top right. They are saved in the page address as ?paywall= and ?days=, so you can share a view.

While new numbers load, the last numbers stay on screen, dimmed.

• The range is the last 7, 30 or 90 times 24 hours up to now. The daily chart shows that many UTC days ending today, so its first day may be only partly counted.
• How far back your data goes depends on your plan: 30 days on Free and Indie, 90 days on Pro and Team. See Plans and billing.

Empty statesCopy Anchor Link

• No views in the range: No views yet, or No views for NAME yet when a screen is selected, with an Install the SDK button. The text reminds you that the SDK reports views, buy taps and purchases on its own once your site shows a screen from a placement or paywall ID, and that if checkout finishes on another page you call reportPurchase() there.
• Loading fails: an error with a Retry button.

The four numbersCopy Anchor Link

The strip at the top counts unique visitors over the whole range.

What this means in practice:

• A visitor is a random ID the SDK keeps in the browser (not a person or an account). The same person on two browsers is two visitors, and someone who clears their data becomes a new visitor.
• A view is one screen shown. Each screen of a multi-screen flow is a view. Views are also what your plan's monthly limit counts. Previews from the dashboard, and visitors skipped by a frequency limit, an audience set to Nothing or a holdout, are not views.
• Tapped buy is recorded when a visitor taps a purchase button. Bought is recorded when your onPurchase finishes without returning false, or when your site calls reportPurchase(). If Bought stays at zero, your site is not reporting purchases.
• Each number counts visitors that have that kind of event in the range. They are counted separately, so a visitor whose view fell before the range but who bought inside it counts under Bought only.
• Events reach the page within a few seconds. The SDK sends them in batches about every 2 seconds and when the visitor leaves the page.

Visitors per dayCopy Anchor Link

A column chart of Visitors for each UTC day. Use the chart to spot a launch, a drop after a release, or a quiet weekend.

• The y-axis maximum is rounded up to 1, 2 or 5 times a power of ten (at least 2). Gridlines mark the maximum, half and zero.
• A day with no visitors draws a thin line so the day still shows on the timeline.
• Hover or focus a column for a tooltip: the day, N visitors · N bought.
• Show table switches to a table with the columns Day, Visitors and Bought, newest day first. Show chart switches back.
• A day's Visitors counts distinct visitors that day, so the daily numbers do not add up to the strip's total (a person who returns on three days counts once in the total and once per day).

Button pressesCopy Anchor Link

Shown when any "Run your code" button was pressed in the range. Use it to read completion on onboarding screens, permission prompts and surveys.

Rows are sorted by Visitors, and the table shows at most 50 rows.

AnswersCopy Anchor Link

Shown when visitors answered questions on a screen that has questions (single choice and multiple choice). There is one card per question, sorted by the number of people who answered.

Each card shows the Field ID (and the screen name when the filter is All screens), N answered, and one row per answer: the Answer ID, a bar, the share and the number of visitors, for example 42% · 128.

• N answered is the number of distinct visitors who answered that question, once, even if they chose several options.
• A share is visitors who chose this option divided by N answered. For a multiple choice question the shares can add up to more than 100%.
• Only chosen options are counted. Text typed into a Text field is never sent to Miniwall, so it never appears here. Your site receives it in answers. See Answers in the SDK.
• An option is counted when the visitor moves on, closes, buys or presses a button, once per visitor per option.
• The page shows up to 200 answer rows across all questions, most chosen first.

By screenCopy Anchor Link

With All screens selected, a table lists each screen that had events in the range, most visitors first.

By published versionCopy Anchor Link

With one screen selected, this table breaks it down by published version (v1, v2, newest first) with the same columns. Use it to see whether a new publish helped. Events that arrived without a version number show as Unknown.

What is not hereCopy Anchor Link

• A/B test and holdout comparisons live on the placement's Results tab, because they need the placement's own groups.
• Revenue is not shown. Miniwall does not process payments, so it never sees an amount. It counts purchases your site reports.

RelatedCopy Anchor Link

• Placement results
• Events and privacy in the SDK
• Purchases in the SDK
• Guide: collect survey answers
• Plans and billing