7c1db78050
## Database Schema Enhancements ### Migration 19 - Fixed - Removed invalid composite index on session(visitor_id, user_id) - visitor_id column doesn't exist in session table - Fixed migration to only create valid indexes ### Migration 20 - New Constraints (with rollback support) - Added websiteId foreign key to UserMapping table - Added foreign key constraint to Website table for referential integrity - Added composite index on UserMapping(websiteId, userId) for query performance - Added composite index on Session(websiteId, userId) for join optimization ### Schema Updates - Updated UserMapping model with websiteId field - Added foreign key relationship: UserMapping -> Website - Added userMappings relation to Website model - Added composite indexes for better query performance ## Files Changed ### Modified - prisma/schema.prisma - Added foreign keys and composite indexes - prisma/migrations/19_add_user_id_mapping/migration.sql - Fixed invalid index ### New - prisma/migrations/20_add_user_mapping_constraints/migration.sql - Forward migration - prisma/migrations/20_add_user_mapping_constraints/rollback.sql - Rollback script ## Benefits - ✅ Referential integrity enforced at database level - ✅ Optimized queries for Umami sync operations - ✅ Better join performance on Session table - ✅ Rollback capability for safe schema changes ## Breaking Changes - UserMapping table now requires websiteId field - Existing data will be migrated to use first available website_id ## Migration Notes Run the migration with: ```bash npx prisma migrate deploy ``` To rollback if needed: ```bash psql -d umami -f prisma/migrations/20_add_user_mapping_constraints/rollback.sql ``` |
||
|---|---|---|
| .github | ||
| .husky | ||
| cypress | ||
| db | ||
| docker | ||
| podman | ||
| prisma | ||
| public | ||
| scripts | ||
| src | ||
| .dockerignore | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .gitignore | ||
| .prettierignore | ||
| .prettierrc.json | ||
| .stylelintrc.json | ||
| app.json | ||
| cypress.config.ts | ||
| docker-compose.upgraded.yml | ||
| docker-compose.yml | ||
| Dockerfile | ||
| jest.config.ts | ||
| LICENSE | ||
| netlify.toml | ||
| next-env.d.ts | ||
| next.config.ts | ||
| package.components.json | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| postcss.config.js | ||
| README.md | ||
| rollup.tracker.config.js | ||
| tsconfig.json | ||
| tsconfig.prisma.json | ||
| tsup.config.js | ||
Umami
Umami is a simple, fast, privacy-focused alternative to Google Analytics.
🚀 Getting Started
A detailed getting started guide can be found at umami.is/docs.
🛠 Installing from Source
Requirements
- A server with Node.js version 18.18 or newer
- A database. Umami supports PostgreSQL (minimum v12.14) databases.
Get the Source Code and Install Packages
git clone https://github.com/umami-software/umami.git
cd umami
pnpm install
Configure Umami
Create an .env file with the following:
DATABASE_URL=connection-url
The connection URL format:
postgresql://username:mypassword@localhost:5432/mydb
Build the Application
pnpm run build
The build step will create tables in your database if you are installing for the first time. It will also create a login user with username admin and password umami.
Start the Application
pnpm run start
By default, this will launch the application on http://localhost:3000. You will need to either proxy requests from your web server or change the port to serve the application directly.
🐳 Installing with Docker
To build the Umami container and start up a Postgres database, run:
docker compose up -d
Alternatively, to pull just the Umami Docker image with PostgreSQL support:
docker pull docker.umami.is/umami-software/umami:postgresql-latest
🔄 Getting Updates
To get the latest features, simply do a pull, install any new dependencies, and rebuild:
git pull
pnpm install
pnpm run build
To update the Docker image, simply pull the new images and rebuild:
docker compose pull
docker compose up --force-recreate -d
🎯 First8 Marketing Integration
This is a customized version of Umami Analytics integrated into the First8 Marketing Hyper-Personalized System. This implementation extends the standard Umami installation with:
Enhanced Features
- PostgreSQL 17 with Apache AGE - Graph database capabilities for advanced relationship tracking
- TimescaleDB Integration - Time-series optimization for analytics data
- Extended Event Tracking - Comprehensive WordPress and WooCommerce event capture
- Real-time Data Pipeline - ETL integration with the recommendation engine
- Multi-dimensional Analytics - Contextual, behavioral, temporal, and journey tracking
System Architecture
This Umami instance serves as the data collection layer for the First8 Marketing hyper-personalization system:
WordPress Site → Umami Analytics → Recommendation Engine → Personalized Content
Data Flow:
- Collection: Umami captures all user interactions, page views, and WooCommerce events
- Storage: Events stored in PostgreSQL with TimescaleDB for time-series optimization
- Graph Analysis: Apache AGE enables relationship mapping between users, products, and behaviors
- ETL Pipeline: Real-time synchronization with the recommendation engine
- Personalization: ML models use analytics data to generate hyper-personalized recommendations
Integration Components
This Umami installation works in conjunction with:
- First8 Marketing Track Plugin - WordPress connector for seamless event tracking
- Recommendation Engine - Proprietary ML-powered personalization backend
- First8 Marketing Recommendation Engine Plugin - WordPress connector for displaying personalized content
Database Enhancements
PostgreSQL Extensions:
- Apache AGE 1.6.0 - Graph database for relationship mapping
- TimescaleDB 2.23.0 - Time-series optimization for analytics queries
- Prisma 6.18.0 - ORM for database management
Custom Schema Extensions:
- User journey tracking tables
- Product interaction graphs
- Session behavior analysis
- Purchase pattern storage
Configuration for First8 Marketing
Environment Variables:
DATABASE_URL=postgresql://username:password@localhost:5432/umami
NODE_ENV=production
PORT=3000
Required PostgreSQL Version: 17.x (for Apache AGE compatibility)
Usage in First8 Marketing System
Event Tracking:
- All WordPress core events (page views, clicks, form submissions)
- WooCommerce events (product views, add to cart, purchases, checkout steps)
- Custom events via First8 Marketing Track plugin
- User journey and session tracking
Data Access:
- Real-time analytics dashboard via Umami UI
- ETL pipeline for recommendation engine
- Graph queries via Apache AGE for relationship analysis
- Time-series queries via TimescaleDB for trend analysis
Deployment Notes
This instance is configured for standalone deployment with:
- PostgreSQL 17 database server
- Apache AGE graph extension
- TimescaleDB time-series extension
- Node.js 18.18+ runtime
- Reverse proxy (Nginx/Apache) for production
Credits
Original Software:
- Umami Analytics - Created by Umami Software
- Licensed under MIT License
- Original repository: github.com/umami-software/umami
First8 Marketing Customization:
- Integration & Enhancement - First8 Marketing
- PostgreSQL 17 + Apache AGE + TimescaleDB integration
- Extended event tracking for WordPress/WooCommerce
- ETL pipeline for recommendation engine
- Custom schema extensions for hyper-personalization
🛟 Support
Original Umami Support:
First8 Marketing Integration Support:
- For integration-specific issues, contact First8 Marketing
- For core Umami issues, use the official Umami support channels above
📄 License
This project maintains the original MIT License from Umami Software.
Original Authors: Umami Software Integration & Customization: First8 Marketing