Website visit to paid customer
Install the tracker, connect a payment provider, then confirm the sale carries its source and landing page.
Grometrics help center
Get tracking live, connect revenue, understand a report, or find the setup guide for your stack.
The shortest path
Install the web tracker or a mobile SDK, then confirm your first session in Realtime.
Start tracking 02Bring in purchases, renewals, refunds, and trials from the payment provider you already use.
Connect revenue 03Turn pages, screens, goals, and transactions into a conversion path you can improve.
Create a funnel 04Trace a source, campaign, page, screen, or transaction back to the visitor journey behind it.
Explore visitorsGuided workflows
These sequences connect setup, reporting, and the decision you are trying to make.
Install the tracker, connect a payment provider, then confirm the sale carries its source and landing page.
Track the first app open, preserve install context, identify the customer, and connect RevenueCat lifecycle events.
Keep campaign naming consistent, connect spend, and compare acquisition cost with payment-backed revenue.
Define the meaningful milestones, inspect the drop-off, then open the visitors behind the weak step.
Help by topic
Choose the right installation path and verify that Grometrics can see real activity.
Move from the revenue headline into the report that answers the next question.
Connect payment outcomes to the source, campaign, page, or screen that earned them.
Understand which acquisition work creates customers and what it costs.
Find the milestone or journey step that blocks activation, conversion, or purchase.
Keep a trustworthy person-level history across anonymous, signed-in, web, app, and server activity.
Connect installs, screen journeys, app identity, and subscription revenue in one workflow.
Automate reporting, connect growth tools, and send the right alerts to your team.
Keep sites and apps separate, configure reporting defaults, and manage access safely.
Recently added
Engagement signals and coordinated crawler detection keep unreliable traffic out of source reports.
MobileHosted app links retain campaign and destination context through first install.
VisitorsSpot visitors completing multiple goals, notify your team, and export complete event histories.
IdentityKeep browser, app, and trusted server events attached to the same customer.
ReportingAnalytics, Sources, Pages, Realtime, Devices, and Visitors now speak the right platform language.
FunnelsModel property filters, alternative steps, grouped milestones, and saved activation metrics.
Common questions
Home-screen opens, app-switcher returns, Spotlight, ATT opt-outs, and opens without referral context are legitimately Direct. Managed links and supported ad integrations recover source context when evidence exists.
Read mobile attributionThe payment needs a visitor, session, customer, or supported attribution key that can be joined to earlier activity. Check identity linking and the provider setup before changing the attribution model.
Check revenue matchingSources explores acquisition traffic and its breakdowns. Attribution applies a model to revenue and compares the commercial result, including sales, CAC, ROAS, and recent customers.
Compare attribution modelsIdentify after sign-in or when a trusted customer ID becomes available. Reset before sign-out so the next person on a shared browser or device starts with a separate anonymous identity.
Read identity guidanceYes. A combined workspace can report Web, App, or All views while keeping platform-specific concepts such as pages, screens, bounce rate, app versions, and install sources clear.
See combined analyticsIt uses request evidence, engagement signals, known automation patterns, and coordinated cloud-traffic behavior. Legitimate visits stay protected because distributed filtering requires the full suspicious pattern.
Read traffic filtering