How ahsanka667-ai/tracker works
TG Tracker captures ad clicks, associates them with Telegram activity, evaluates configured conversion triggers, records conversions, and sends events to Meta. Users manage accounts, campaigns, triggers, inbox messages, and funnels through the dashboard; the master bot also handles Telegram-based access and reusable invitations. Redis carries click/session payloads and real-time notifications, while PostgreSQL holds product state. The README documents funnel and inbox behavior beyond the sampled source, so those capabilities are represented without asserting unsampled internal call paths.
Main entry points: main.py Web API · database.py Database access · worker.py Telegram worker · index.html Dashboard UI
Components 20
Dashboard and API
- Dashboard UI
dashboard/index.html - Web API
service_a/main.py - WebSocket hub
service_a/websocket_manager.py - Master bot
master_bot/bot.py - Accounts and campaigns
service_a/main.py - Message inbox
service_a/main.py
Telegram tracking
- Click tracking
service_a/main.py - Telegram worker
service_b/worker.py - Meta CAPI
service_b/meta_capi.py - Telegram
- Meta platform
Conversion analytics
- Funnels and steps
service_a/main.py - Inbound webhooks
service_a/main.py - Conversion logs
shared/models.py
Shared platform
- Database access
shared/database.py - PostgreSQL
- Redis
Other components
- Tracker user
- Telegram user
- External system
Connections 26
- Tracker user → Dashboard UI: uses
- Dashboard UI → Web API: requests
- Web API → Accounts and campaigns: manages
- Web API → Message inbox: serves
- Web API → Funnels and steps: manages
- Web API → Inbound webhooks: accepts events
- Web API → Click tracking: handles clicks
- Click tracking → Database access: reads campaign
- Click tracking → Redis: stores click data
- Click tracking → Telegram: redirects visitor
- Telegram user → Telegram: sends activity
- Telegram → Telegram worker: delivers updates
- Telegram worker → Redis: consumes click data
- Telegram worker → Database access: reads and writes
- Telegram worker → Meta CAPI: fires conversions
- Meta CAPI → Meta platform: sends events
- Telegram worker → Redis: publishes alerts
- Web API → Redis: subscribes alerts
- Web API → WebSocket hub: forwards alerts
- WebSocket hub → Dashboard UI: pushes updates
- Web API → Database access: queries and updates
- Master bot → Database access: manages access
- Master bot → Telegram: serves commands
- Database access → PostgreSQL: reads and writes
- Database access → Conversion logs: persists records
- External system → Inbound webhooks: posts conversions