Subster.aiSubster.aiSubster.ai
EN

Traffic and analytics

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”.

LogGroup in the “Action” filterWhat gets in
OrganizationTeamadmin added or demoted, access to billing data opened or closed, person removed from the organization or left, ownership transferred
Invitesinvite created, revoked, accepted
Projectsproject created, project deleted
Organizationorganization renamed; list of drop-offs across the organization exported to a file
Paymentsfreeze lifted manually by support after a dispute
ProjectProject teammember added or removed, role changed, project ownership transferred
Invitesproject invite created, revoked, accepted
Projectproject 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
Domainsdomain renewal repeated with a new charge
Paymentsprice 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 “Keep in Stripe”; with “Cancel now” and “Cancel at period end” 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

  • “Period” — 7 days, 30 days or all time. “Action” — one group from the table above.
  • “Member (actor)” — who did it, “Target” — 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” to the right of the “Audit” title exports to CSV everything matching the filters, beyond one page. The file builds in the background: save it when “Download the file” appears.

What changed is in the record details: click a row and they open right below it. 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.

How many installs are linked to a payment

Under the funnel stages, the “Matched N of M installs” line with a share shows how many app installs we linked to paid access. The “?” next to it shows how many are not linked. Only installs count, so payers who never installed the app are not here — the funnel shows them.

A low share 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 line and no “Got access” stage: we do not grant access.

Pass-through funnel

Above the stages, the cabinet names the stage losing the most people: “Biggest drop — “…””.

StageCounted when
1. Clicked the adthe person came via a link with an ad network or partner click id; organic and direct visits skip this stage
2. Opened the funnelthe quiz page or paywall opened
3. Left an emailthe person left an email
4. PaidStripe confirmed payment or your server told us about the purchase
5. Opened the app via linkthe 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 appthe app, your server or the attribution tracker told us about the install
7. Got accesswe 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 “>100%” under it is not an error. Look for post-payment losses at stages 5 and 6.

Drop-off betweenWhat to check
“Opened the funnel” and “Paid”the quiz and the paywall — the “Quiz screen drop-off” 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 at “…”, N” 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 at “Paid””, one who installed bypassing the link does not. “Source” is the A/B test direction, “When” the first-visit time. “Export” above the list exports up to 10,000 rows to CSV, also in the background.

Loops and drop-off by screen

Both tables are collapsed under “More” at the bottom of the tab.

  • “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.
  • “Quiz screen drop-off” — the quiz screen people leave most. It counts sessions, not people. In a project “Audit” with no funnel selected in the filter, the table takes the most visited funnel for the period.

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) and press “Find path”. The “Visitor path” window opens: 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 adminthe organization log and the log of every projectthe whole organization with a “Project” filter; in the project menu — this project
Project owner and admintheir project's logall project traffic
Retention managerdoes not seeall project traffic
Memberdoes not seeonly people who came through quizzes and paywalls they created themselves; a banner above the tab says so

Next