Skip to content

Introduction

SimpleStats is a streamlined analytics tool tailored for Laravel applications, transcending mere counts of views and visits. It offers precise insights into user origins and behaviors. With default tracking and filtering via UTM codes, you gain detailed analysis of marketing campaigns, identifying which efforts drive revenue. Effortlessly evaluate campaign ROI, discover cost-effective user acquisition channels, and pinpoint the most effective performance channels. SimpleStats ensures full GDPR compliance and a minimalistic and straightforward installation process.

How to set up SimpleStats in just a few minutes

Are you a visual learner? Here you can learn how to set up SimpleStats in just a few minutes.

How does it work?

API Communication

Basically all we do is provide a composer package, which allows you to simply define and set your User and Payment model and Login event in the package config file. Then we listen if a new user or payment gets created or a login event occurs, and we send an API call to our service.

Data Visualisation

We collect this data in a GDPR-compliant way, aggregate it and make it filterable and visible for you on our nice looking dashboard at https://simplestats.io. This allows you to see how your campaigns and users perform during a selected time period filtered by UTMs, referrers and countries!

Teams, Projects and Instances

You can invite co-workers to your team and assign roles, such as Administrator, Editor, Viewer to them. Furthermore, if you like and want to, you can create multiple projects and multiple instances per project. For example, in a SaaS application, you might have different environments like “Environment A,” “Environment B,” etc. This allows you to view and analyze each instance separately or get an aggregated overview at the project level.

Server-Side vs Client-Side Tracking

Ad blockers and other privacy tools have a significant impact on the effectiveness of client-side analytics. Estimates suggest that up to 30-50% of tracking data can be blocked when using client-side analytics due to these tools. This can lead to incomplete datasets, skewed metrics, and ultimately, inaccurate insights.

On the other hand, server-side analytics like SimpleStats are largely unaffected by ad blockers since the data collection occurs on the server rather than the user’s device. This method ensures more accurate and comprehensive data collection, as it bypasses the limitations imposed by client-side tracking methods.

Furthermore, server-side tracking offers enhanced data security and privacy since it does not rely on third-party cookies and is less vulnerable to browser restrictions and privacy settings. This makes it a more reliable choice for collecting accurate data and maintaining compliance with data protection regulations like GDPR.

In summary, while client-side analytics are easier to implement, server-side analytics provide more accurate and comprehensive data, unaffected by ad blockers and privacy tools, making them a better choice for businesses needing reliable metrics.

KPIs

On our dashboard, we provide you with the following KPIs.

INFO

Don't worry if you do not understand the list below immediately. It's easier to understand it when you see it in action on the dashboard.

KeyShortDescription
VISITORSUnique VisitorsNumber of unique visitors for the selected period.
REGRegistrationsNumber of new registrations for the selected period.
CRConversion RatePercentage of unique visitors who registered at the selected period.
NETNet revenueNet revenue for the selected period.
FEEFeeFee for the selected period.
GROSSGross revenueGross revenue for the selected period.
ARPDAUAverage revenue Per DAUThe average revenue per DAU.
ARPUAverage revenue Per UserThe average revenue per User (how much is a user/lead/reg worth in money).
ARPVAverage revenue Per VisitorThe average revenue per Unique Visitor (how much is a unique visitor worth in money).
NAUNew Active UsersNumber of users who returned at the selected period to the app (=2nd login) after the registration (=1st login).
NAPUNew Active Paying UsersNumber of users who did their first payment at the selected period.
PUPaying UsersNumber of users who did at least one payment over lifetime.
ARPPUAverage revenue Per Paying UserThe average revenue per paying User.
DAUDaily Active UsersNumber of users who logged in at the selected period (without 1st login = registration).
DAPUDaily Active Paying UsersNumber of users who logged in or registered at the selected period and did at least one payment over lifetime (including the selected period)
DAAPUDaily Active Active Paying UsersNumber of users who logged in or registered during the given period and did at least one payment in the last 20 days (including the selected period)
WAUWeekly Active UsersNumber of users who logged in at the selected period (without 1st login = registration).
WAPUWeekly Active Paying UsersNumber of users who logged in or registered at the selected period and did at least one payment over lifetime (including the selected period)
WAAPUWeekly Active Active Paying UsersNumber of users who logged in or registered during the given period and did at least one payment in the last 20 days (including the selected period)
MAUMonthly Active UsersNumber of users who logged in at the selected period (without 1st login = registration).
MAPUMonthly Active Paying UsersNumber of users who logged in or registered at the selected period and did at least one payment over lifetime (including the selected period)
MAAPUMonthly Active Active Paying UsersNumber of users who logged in or registered during the given period and did at least one payment in the last 20 days (including the selected period)
REG2DAUReg. to DAUPercentage of registered users who become DAUs
REG2WAUReg. to WAUPercentage of registered users who become WAUs
REG2MAUReg. to MAUPercentage of registered users who become MAUs
REG2PUReg. to PayPercentage of registered users who become paying user.

Help

Do you have a question? Feel free to reach out to us if you need some help.