Laravel Analytics: Traffic, Revenue & Attribution United | Mohamed Said [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://www.msaied.com) [ Home ](https://www.msaied.com) [ Projects ](https://www.msaied.com/projects) [ Articles ](https://www.msaied.com/articles) [ Certificates ](https://www.msaied.com/certificates) [ Contact ](https://www.msaied.com#contact-section) [ ](https://github.com/EG-Mohamed) [ Home ](https://www.msaied.com) [ Projects ](https://www.msaied.com/projects) [ Articles ](https://www.msaied.com/articles) [ Certificates ](https://www.msaied.com/certificates) [ Contact ](https://www.msaied.com#contact-section) [ home ](https://www.msaied.com) [ articles ](https://www.msaied.com/articles) The Analytics Stack for Laravel: Traffic, Revenue and Attribution in One Place On this page 1. [ The Three-Tool Problem Every Laravel SaaS Knows ](#the-three-tool-problem-every-laravel-saas-knows) 2. [ Why the Join Never Works ](#why-the-join-never-works) 3. [ A Single Server-Side Chain Instead ](#a-single-server-side-chain-instead) 4. [ What the Unified Stack Covers ](#what-the-unified-stack-covers) 5. [ Traffic Analytics ](#traffic-analytics) 6. [ Subscription Metrics ](#subscription-metrics) 7. [ Campaign Profit ](#campaign-profit) 8. [ Retention by Channel ](#retention-by-channel) 9. [ AI Assistant and MCP Server ](#ai-assistant-and-mcp-server) 10. [ Installation ](#installation) 11. [ Key Takeaways ](#key-takeaways) ![The Analytics Stack for Laravel: Traffic, Revenue and Attribution in One Place](https://cdn.msaied.com/448/2b223c7182f017965be95780b9839e2b.png) [ Laravel ](https://www.msaied.com/articles?category=laravel) [ Composer Pacakge ](https://www.msaied.com/articles?category=composer-pacakge) #Laravel #Analytics #SaaS Metrics #UTM Attribution #Server-Side Tracking The Analytics Stack for Laravel: Traffic, Revenue and Attribution in One Place ================================================================================ 15 Jul 2026 4 min read ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said Table of contents 11 sections 1. [ 01 The Three-Tool Problem Every Laravel SaaS Knows ](#the-three-tool-problem-every-laravel-saas-knows) 2. [ 02 Why the Join Never Works ](#why-the-join-never-works) 3. [ 03 A Single Server-Side Chain Instead ](#a-single-server-side-chain-instead) 4. [ 04 What the Unified Stack Covers ](#what-the-unified-stack-covers) 5. [ 05 Traffic Analytics ](#traffic-analytics) 6. [ 06 Subscription Metrics ](#subscription-metrics) 7. [ 07 Campaign Profit ](#campaign-profit) 8. [ 08 Retention by Channel ](#retention-by-channel) 9. [ 09 AI Assistant and MCP Server ](#ai-assistant-and-mcp-server) 10. [ 10 Installation ](#installation) 11. [ 11 Key Takeaways ](#key-takeaways) The Three-Tool Problem Every Laravel SaaS Knows ----------------------------------------------- Most Laravel SaaS applications end up with the same analytics setup: a **traffic tool** (Google Analytics, Plausible, or Fathom), a **subscription-analytics tool** (ChartMogul, Baremetrics, or ProfitWell), and an **ad pixel** (Meta or Google tag). Each does its job in isolation. None of them talk to each other. The result is three dashboards, three definitions of a "customer", and a quarterly spreadsheet where someone manually tries to join them. The numbers that actually drive budget decisions — which campaign brings customers who *stay*, what a newsletter subscriber is worth over 12 months, whether a campaign was profitable after churn — live in the gaps between the tools, not inside any one of them. ### Why the Join Never Works Each tool identifies users differently: - The traffic layer uses a **client-side cookie** - The revenue layer uses a **Stripe customer ID** - The ad pixel uses its **own anonymous ID** Reconciling those three identifiers is manual, lossy, and stale the moment it's done. Add the fact that 30–50% of client-side events are swallowed by ad blockers, and you're making budget decisions on incomplete data. A Single Server-Side Chain Instead ---------------------------------- [SimpleStats](https://simplestats.io/) takes a different approach. Rather than watching one slice from the outside, it tracks the entire customer journey as one connected chain, server-side, from inside your Laravel app: ``` visitor → registration → login → payment ``` Because all four events are captured in the same place and linked to the same visitor ID, every downstream metric inherits the acquisition context automatically. A payment isn't just a payment — it's a payment from the visitor who arrived via `utm_campaign=spring-sale` from Germany six weeks ago. Nothing needs reconciling after the fact. Running server-side also means no cookie banner for analytics, no ad-blocker blind spots, and GDPR compliance out of the box. What the Unified Stack Covers ----------------------------- ### Traffic Analytics Unique visitors, sources, campaigns, countries, devices, and conversion rate — the privacy-first web analytics layer you'd expect from Fathom or Plausible, but filterable by every revenue dimension below it. ### Subscription Metrics MRR and ARR, MRR movements (new, expansion, contraction, churn, reactivation), Net and Gross Revenue Retention, Quick Ratio, and LTV — the full ChartMogul-style dashboard, with every metric filterable by acquisition channel. ### Campaign Profit Enter ad spend per campaign and get ROAS, CAC, net profit, LTV:CAC, and CAC payback per channel — computed from revenue that is already attributed to the campaign that earned it. ### Retention by Channel Cohort retention filtered by channel, so the question shifts from "do users come back?" to "which channel brings the users who come back?" AI Assistant and MCP Server --------------------------- SimpleStats ships a built-in AI assistant that runs real queries against your connected dataset. You can ask natural-language questions like: - *"Which channel brought the customers still active after 90 days?"* - *"What's the MRR of everyone who came in through the newsletter?"* Because the underlying data is already joined, the assistant can answer questions that would be unanswerable on a fragmented three-tool stack. It also ships a hosted MCP server for use inside Claude Code, Cursor, or Claude Desktop: ```bash claude mcp add --transport http simplestats https://simplestats.io/mcp \ --header "Authorization: Bearer API_TOKEN_HERE" ``` Installation ------------ There is no three-way integration to wire up. Install one Composer package: ```bash composer require simplestats-io/laravel-client ``` Point it at your existing `User` and payment models, and the full stack — traffic, subscriptions, campaign profit, retention, and the AI assistant — fills in from the same server-side data. Stripe, Paddle, and Lemon Squeezy are all supported. Key Takeaways ------------- - Three separate analytics tools create unbridgeable identity gaps that make channel-level ROI impossible to calculate reliably. - Server-side tracking eliminates ad-blocker data loss and removes the need for a cookie consent banner on the analytics layer. - Linking visitor, registration, login, and payment events under one ID means every revenue metric is automatically attributed to its acquisition channel. - A single Composer package replaces the traffic tool, the subscription dashboard, and the ad-pixel attribution layer. - An AI assistant and MCP server integration are only as useful as the dataset underneath — a joined dataset is the prerequisite. --- *Source: [The Analytics Stack for Laravel: Traffic, Revenue and Attribution in One Place](https://laravel-news.com/the-analytics-stack-for-laravel-traffic-revenue-and-attribution-in-one-place) — Laravel News, July 15, 2026* Found this useful? [ ](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.msaied.com%2Farticles%2Fthe-analytics-stack-for-laravel-traffic-revenue-and-attribution-in-one-place&text=The+Analytics+Stack+for+Laravel%3A+Traffic%2C+Revenue+and+Attribution+in+One+Place) [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.msaied.com%2Farticles%2Fthe-analytics-stack-for-laravel-traffic-revenue-and-attribution-in-one-place) Frequently Asked Questions ---------------------------- 3 questions Q01 Why can't I just join data from Plausible, ChartMogul, and my ad pixel manually? Each tool uses a different identifier — a client-side cookie, a Stripe customer ID, and the pixel's own anonymous ID. Reconciling them is manual and lossy, and 30–50% of client-side events are blocked by ad blockers before they even arrive, making the resulting data incomplete and unreliable for budget decisions. Q02 How does server-side analytics in Laravel avoid ad-blocker data loss? Server-side tracking fires from within your Laravel application on incoming requests rather than from a browser script, so ad blockers have no opportunity to intercept the events. This means visitor and conversion data is complete, which is the prerequisite for every downstream metric being trustworthy. Q03 What does the SimpleStats Laravel package actually track? After running `composer require simplestats-io/laravel-client` and pointing the package at your User and payment models, it tracks visitors, registrations, logins, and payments as one connected chain. This single dataset powers traffic analytics, subscription metrics (MRR, churn, LTV), campaign profit (ROAS, CAC), and cohort retention — all filterable by acquisition channel. Continue reading More Articles --------------- [ View all ](https://www.msaied.com/articles) [ ![DDD Value Objects and DTOs in Laravel Without the Bloat](https://cdn.msaied.com/450/41688537085b86f102fd8c219a35319f.png) laravel ddd php ### DDD Value Objects and DTOs in Laravel Without the Bloat Learn how to implement domain-driven value objects and data transfer objects in Laravel using PHP 8.3 readonly... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 21 Jul 2026 1 min read Read ](https://www.msaied.com/articles/ddd-value-objects-and-dtos-in-laravel-without-the-bloat) [ ![Laravel + Python FastAPI: Image OCR Demo](https://cdn.msaied.com/447/5f3d87146fbf19957973cbc88c6c0155.png) Laravel Python FastAPI ### Laravel + Python FastAPI: Image OCR Demo Learn how to call a Python image OCR script from Laravel using FastAPI as the bridge. This premium tutorial wa... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 20 Jul 2026 3 min read Read ](https://www.msaied.com/articles/laravel-python-fastapi-image-ocr-demo) [ ![Scaffold Laravel Packages with the `laravel package` Command in Installer v5.31.0](https://cdn.msaied.com/449/522e744d3c7bae1f214c179a83ae5b88.png) Laravel Installer Package Development CLI ### Scaffold Laravel Packages with the `laravel package` Command in Installer v5.31.0 Laravel Installer v5.31.0 introduces a `laravel package` command to scaffold packages from the CLI, automated... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 20 Jul 2026 3 min read Read ](https://www.msaied.com/articles/scaffold-laravel-packages-with-the-laravel-package-command-in-installer-v5310) [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://www.msaied.com)Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow. Explore - [Home](https://www.msaied.com) - [Projects](https://www.msaied.com/projects) - [Articles](https://www.msaied.com/articles) - [Certificates](https://www.msaied.com/certificates) - [Contact](https://www.msaied.com#contact-section) Connect - [ hello@msaied.com ](mailto:hello@msaied.com) - [ +20 109 461 9204 ](tel:+201094619204) © 2026 Mohamed Said. All rights reserved. [ ](https://github.com/EG-Mohamed) [ ](https://www.linkedin.com/in/msaiedm/) [ ](https://wa.me/201094619204) [ ](mailto:hello@msaied.com) [ ](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view)