Audit

See who changed what in a project or organization, where visitors drop off on the way to the app and what happened to one person — a few minutes per question.

Where to open “Audit”

The “Audit” item is in two menus:

in the project menu — this project's logs;
in “Entire organization” mode — the organization's logs. Switching is covered under “How the cabinet is organized” in Project and team.

Two tabs inside: “Team” (“Project team” in a project) answers who changed what; “Traffic” shows the visitor path.

The cabinet's “project action log” or “team action log” is this tab — “Project team” in the project “Audit”.

Both logs keep records a year, so “All time” is the last twelve months.

Find out who changed what

Open “Team” and pick what you need in the “Action” filter. Organization and project logs do not overlap: everything done inside a project, money included, is only in that project's “Audit”.

Log	Group in the “Action” filter	What gets in
Organization	Team	admin added or demoted, access to billing data opened or closed, person removed from the organization or left, ownership transferred
	Invites	invite created, revoked, accepted
	Projects	project created, project deleted
	Organization	organization renamed; list of drop-offs across the organization exported to a file
	Payments	freeze lifted by support while a dispute is open
Project	Project team	member added or removed, role changed, project ownership transferred
	Invites	project invite created, revoked, accepted
	Project	project renamed; shared cookie consent for subdomains changed; “Money settings changed” — server charges and refunds, subscription management by key, charge caps, trial only once, grace period, “How you take payments”; Adapty or RevenueCat keys changed; Stripe disconnected with subscriptions left; access revoked after the grace period; leads or drop-off list exported to a file
	Domains	domain renewal repeated with a new charge
	Payments	price removed from sale or brought back, subscription refund, subscription cancelled now or at the end of the paid period, charge log exported to a file

Funnel edits and publishing, domain purchases and connecting Stripe are not logged. A Stripe disconnect is recorded only with “Leave them, I will sort it out in Stripe”; with “Cancel the subscriptions now” and “Cancel at the end of the paid period” there is no record.

Money settings and “How you take payments” change on the Payment settings page. The log cannot undo a change — only changing the setting again can.

Filters

“Member (actor)” — who did it, “On whom” — to whom or to what.
“Important only” keeps what changes someone's access or money: roles, removals, ownership transfer, project deletion, money settings, keys, prices, refunds, cancellations, Stripe disconnects. Invites, renames and file exports are excluded.
“Export CSV” exports everything matching the filters, beyond one page. The file builds in the background: save it when “Download the file” appears.

What changed is in “Record details”, opened by a row click. Authorless records are labelled by source: “Stripe event” — a refund or cancellation from Stripe, “System” — access revoked after the grace period. Other authorless records read “Deleted user”.

See where traffic is lost

Open “Traffic”. Funnel analytics counts sessions; this tab counts people and follows each from the ad to access in the app. The period selects people by first-visit date.

A visitor who clicked “Decline” on the consent banner enters the funnel only from payment: we do not record their visits and email.

Match rate and Orphan installs

“Match rate” — the share of app installs belonging to people with paid access (“N of M installs matched”). “Orphan installs” — installs without a pair: the app is installed, but we see no paid access for that person. Both tiles count installs, so payers who never installed the app are not here — the funnel below shows them.

A low Match rate means checking with your developer how the app passes the customer to us: Handoff to a developer. A project taking payments “On your own” has no such tiles and no “Got access” stage: we do not grant access.

Pass-through funnel

Stage	Counted when
1. Clicked the ad	the person came via a link with an ad network or partner click id; organic and direct visits skip this stage
2. Opened the funnel	the quiz page or paywall opened
3. Left an email	the person left an email
4. Paid	Stripe confirmed payment or your server told us about the purchase
5. Opened the app via link	the app opened via a link from the browser and accepted the handoff code; an install through your server or attribution tracker does not set this stage — such people go straight to “Installed the app”
6. Installed the app	the app, your server or the attribution tracker told us about the install
7. Got access	we granted access for the payment — this happens right after it

Test payments are not counted until “Show test payments” under the filters is checked. Testing the funnel with your own test purchase — check it.

Stage numbers are the intended path order, not the marking order. Access (7) is granted at payment (4), before install, so “Got access” nearly equals “Paid”, and “more than prev.” under it is not an error. Look for post-payment losses at stages 5 and 6.

Drop-off between	What to check
“Opened the funnel” and “Paid”	the quiz and the paywall — the “Drop-off by quiz screen” table below and “Analytics”
“Paid” and “Opened the app via link”	payers did not open the app via the link from the browser — check the handoff with your developer. If “Installed the app” has people, stage 5 is not counted as the main drop-off: some people install the app bypassing the link
“Opened the app via link” and “Installed the app”	the app opened, but we were not told about the install — check sending the install event with your developer

Who dropped off

Click a stage — the “Dropped off at stage …” list appears: people with this stage and none later.

“Got access” does not count here — payment sets it: a payer with no link open and no install stays in “Dropped off at stage “Paid””, one who installed bypassing the link does not. “Source” is the A/B test direction, “When” the first-visit time. “Export CSV” above the list exports up to 10,000 rows, also in the background.

Loops and drop-off by screen

“Funnel loops” — the visitor went in circles and never reached the price. Open the named funnel in the editor and check the named screen's rules in the “Logic” window — Build a funnel.
“Drop-off by quiz screen” — the quiz screen people leave most. It counts sessions, not people.

Both tables label screens “Screen N “name””, N being the number in the editor's “Screens” list. An identifier fragment instead of a number means the screen was deleted from the quiz.

Find the path of a specific visitor

Click a row in the drop-off list or enter in “Find by click_id / guid / email” the person's email, the click id from an ad or partner link, or the visitor id (guid). The “Trace” panel opens — the path through the stages with the time of each.

If someone complains “I paid, but have no access in the app”, enter their email and see where the path breaks.

Search covers only what you see: in a project “Audit” — only this project.

Who sees what

Role	“Team”	“Traffic”
Organization owner and admin	the organization log and the log of every project	the whole organization with a “Project” filter; in the project menu — this project
Project owner and admin	their project's log	all project traffic
Retention manager	does not see	all project traffic
Member	does not see	only people who came through quizzes and paywalls they created themselves; a banner above the tab says so

Everyone except a member has the “Member” filter on “Traffic”: it shows traffic of quizzes and paywalls the selected person created.

Funnel analytics — sessions, quiz steps and comparison of ad sources.
Handoff to a developer — what to give the engineer so that payers reach the app.
Project and team — roles and what each can change.
Payment settings — money settings and Stripe disconnects that get logged.

Emails to customers

Open →