This document applies to FastGPT v4.17.0.
What this category of data looks like
Data for this category primarily originates from advertising platforms, customer relationship management systems, attribution collection SDKs, and online form systems. Updates follow a daily or weekly batch synchronization schedule. Daily generated documents include attribution rule configuration tables, lead distribution allocation sheets, channel effect reports, and abnormal data reconciliation documents. Fields typically include channel identifiers, lead touch time, attribution subject identifiers, conversion association IDs, and similar items. Units follow the standards of the source system: for example, time uses UTC timestamps, and amounts use the corresponding currency units.
What constraints do these characteristics impose on the database and operations link
Multi-source heterogeneous data formats require the database to support flexible field mapping and cleaning logic to prevent data import failures. Daily or weekly batch synchronization tasks generate high concurrent connection demand, so connection pool parameters must be properly configured to avoid connection exhaustion. As sales attribution and channel ROI calculations are involved, data consistency and integrity requirements are high. Raw data and cleaned data must be retained for abnormal reconciliation. Additionally, data volume grows with campaign scale, so storage capacity and query performance must be monitored to ensure report generation efficiency.
How to configure the settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Database connection pool maximum connections | 20–30 | Adapt to concurrent requests from daily batch synchronization, avoid connection exhaustion |
| MongoDB connection address | mongodb://user:pass@host:port/fastgpt_attribution | Corresponds to the MONGODB_URI parameter, stores attribution data and lead history, supports index optimization |
| PostgreSQL connection address | postgresql://user:pass@host:port/fastgpt_report | Corresponds to the PG_URL parameter, stores structured attribution rules and report metadata |
| Redis connection address | redis://:auth@host:port/0 | Corresponds to the REDIS_URL parameter, caches channel parameter verification results and deduplicated lead IDs |
| Data backup cycle | 2 AM daily | Retains 7 days of raw and cleaned data to meet abnormal reconciliation requirements |
| Synchronization task timeout | 600 seconds | Adapts to the task execution limit associated with DB_MAX_LINK, supports large data volume processing for weekly full synchronization |
Three common configuration errors
- Incorrect database connection configuration: manifests as empty fields in channel reports, or synchronization tasks throwing connection timeout errors. Causes include failure to correctly fill in authentication parameters or host addresses for
MONGODB_URI, or failure to enable remote access permissions for the MongoDB service. - No persistent storage configured: manifests as lead data loss after service restart, or inability to find mounted storage volumes during Sealos deployment. Causes include failure to configure a persistent storage volume for the database container, or a mismatch between the storage volume mount path and configuration.
- Failed lead deduplication logic: manifests as the same lead being assigned to multiple sales representatives, or duplicate data appearing in ROI reports. Causes include failure to enable Redis cache deduplication flags, or incorrect
REDIS_URLconfiguration causing cache malfunction.
How to confirm correct configuration
- Run a database connectivity test script to verify the connection status of
MONGODB_URI,PG_URL, andREDIS_URL, and confirm there are no authentication or network exceptions. - Trigger a manual synchronization task, check that channel data is successfully written to the database, and that core fields are complete and not missing.
- View the abnormal reconciliation sheet generation logs, confirm that the data cleaning and deduplication processes are executed normally with no error messages.
- View the database connection pool monitoring panel, confirm that the current active connection count does not exceed the configured connection pool threshold, and there is no connection exhaustion.
The values provided here are common starting points, and should be evaluated against the reader’s own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.