Home

Aggregate Analytics

Aggregate is headless, AI-ready web analytics. It counts what happens on your websites, not who did it, and keeps the results in your own database as privacy-protected SQL views. Power BI, Tableau or an AI assistant can query those views directly, with the same read-only account, and never see a visitor record. It installs on ordinary PHP hosting from a release ZIP.

The documentation is at subschema-llc.github.io/aggregate

The documentation site is searchable and needs no account. It is built from the Markdown files in the repository, so it describes the current release and is reviewed together with the code. This wiki only points you to the right page.

Find what you need

I want to…	Read
Understand what Aggregate does, and what it deliberately does not do	Overview · Why Aggregate exists
Install it on web hosting from a release ZIP, without SSH	Release ZIP on a web host · Plesk guide
Install it with Docker or on my own server	Deployment guide
Choose and connect a database (MySQL, MariaDB, PostgreSQL, SQL Server, SQLite)	Databases
Add tracking, a consent banner or tags to a website	Setup and drop-ins · Tracker · Tag manager
Know what is stored, and when consent is needed	Privacy and compliance
Connect Power BI or Tableau	Connect BI and AI tools · BI labels and glossary
Let an AI assistant answer questions about my traffic	Connect an AI assistant
Change settings in YAML or the dashboard	Configuration · Custom data model
Update an installation, or roll an update back	Updating
Look up a term	Glossary

Contribute

Aggregate is in public beta, and the most useful help right now is a test report, a fix to a confusing documentation step, a database integration check, or an accessibility improvement.

• Why Aggregate exists: the problem, the principles, and what the project will not do.
• Architecture tour: how an event travels from a web page to a BI report.
• Design decisions: why the main choices were made and what would change them.
• Contributing guide: development setup, branches, privacy rules, tests and pull requests.
• Roadmap: planned work and proposals to explore.

Work happens on branches from development, and pull requests target development.

Get help

• Questions and ideas: GitHub Discussions.
• Bugs and proposals: GitHub issues. Please discuss a larger change in an issue before starting on it.
• Security vulnerabilities: report them privately, as described in the security policy, not in a public issue.
• Community expectations: Code of conduct.

About this wiki

This wiki is published from .github/wiki in the repository, and each publish replaces it, so edits made here on GitHub are lost. To improve a documentation page, use Edit this page at the bottom of that page on the documentation site, which opens a pull request.