How tamil43/customer_revenue_anlaytics works
This repository describes an e-commerce customer revenue analytics and targeting workflow: historical transactions are cleaned, analyzed and transformed into customer features, then used for segmentation and predictive revenue targeting. The README documents the major stages, but the supplied source index contains no application source files, so implementation details and internal call relationships cannot be verified. Directory paths identify the documented subsystem areas; workflow edges reflect the README sequence.
Main entry points: 01_customer_revenue_analysis Cleaning And Validation · 02_customer_purchase_prediction Purchase Prediction
Components 10
Revenue Analysis
- Cleaning And Validation
01_customer_revenue_analysis - Transaction Revenue
01_customer_revenue_analysis
Customer Insights
- Customer Features
01_customer_revenue_analysis - Behavioral Segments
01_customer_revenue_analysis
Prediction And Targeting
- Purchase Prediction
02_customer_purchase_prediction - Basket Value
02_customer_purchase_prediction - Expected Revenue
02_customer_purchase_prediction - Revenue Tiers
02_customer_purchase_prediction - Targeting Framework
02_customer_purchase_prediction
Other components
- Raw Transactions
Connections 9
- Raw Transactions → Cleaning And Validation: feeds
README.md - Cleaning And Validation → Transaction Revenue: precedes
README.md - Transaction Revenue → Customer Features: precedes
README.md - Customer Features → Behavioral Segments: precedes
README.md - Behavioral Segments → Purchase Prediction: precedes
README.md - Purchase Prediction → Basket Value: precedes
README.md - Basket Value → Expected Revenue: informs
README.md - Expected Revenue → Revenue Tiers: precedes
README.md - Revenue Tiers → Targeting Framework: informs
README.md