What the data for this category looks like
Core data for campaign setup comes from advertising platforms, user profiling tools, budget scheduling sheets, and attribution analysis tools. It is delivered via campaign setup documents, targeting setting lists, budget allocation tables, and conversion tracking configuration items. Update frequency is mostly daily or when a single campaign launches. Fields include targeted audience package ID, budget amount, conversion event code, and others. Units include yuan, visits, days, and more. Data structure adjusts based on campaign scenarios. Targeting configuration fields vary across industries. The system must adapt to storage and query needs for multi-source heterogeneous data overall.
What constraints these characteristics impose on deployment and upgrade
Campaign setup data comes from scattered sources and has high update frequency. This requires configuring a high-concurrency database connection pool during deployment. This prevents connection resources from being exhausted by concurrent access. Multi-source data storage needs require compatible database and cache configurations. This ensures fast read and write access for targeting configurations and budget data. Internal ticket and operations on-call scenarios require stable domain names and authentication configurations. This ensures the legality and security of ticket notifications and document sharing. During upgrades, data migration consistency must be maintained. This prevents loss of campaign setup configurations. The content on this page is written based on the official environment variable specifications for FastGPT v4.17.0.
How to set the configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://username:password@mongodb:27017/fastgpt?authSource=admin | Adapts to the multi-document storage needs of campaign setup data. Must specify the authentication source and database name |
REDIS_URL | redis://:redis_password@redis:6379/0 | Used to cache frequently accessed targeting configurations and budget data, reducing database load |
DB_MAX_LINK | 200–300 | Matches the concurrent access peak for daily updated campaign setup data, avoiding connection exhaustion |
FE_DOMAIN | https://your-deploy-domain.com | Used to generate valid jump addresses for ticket notifications and document sharing |
ROOT_KEY | Randomly generated string of 32 or more characters | Serves as the system's highest-privilege authentication credential, ensuring the security of internal ticket management |
FILE_TOKEN_KEY | Random string independent of other keys | Used to encrypt temporarily exported files related to campaign setup, preventing data leaks |
Three common mistakes
- Symptom: MongoDB connection timeout occurs when running
pnpm devin a local development environment. Cause: TheMONGODB_URIparameter is not configured correctly, or the associated MongoDB instance is not started normally. - Symptom: The frontend cannot switch to HTTPS protocol when accessing the page. Cause:
FE_DOMAINis not set to an HTTPS-formatted domain name, and no SSL certificate is configured on the reverse proxy layer. - Symptom: Server startup verification fails, or internal ticket functions are abnormal. Troubleshooting items: The server environment variables
AIPROXY_API_ENDPOINT(AI Proxy service root address, format such as http://aiproxy:3000, no path suffix allowed) orAIPROXY_API_TOKEN(AI Proxy admin Token, must match the AI Proxy server configuration and not be empty) are not configured correctly. Or the AI Proxy admin Token is mistakenly used as an application API authentication key, confusing server environment variables and application authentication keys.
How to confirm configurations are correct
- Start the FastGPT server. Check that the startup logs have no verification errors indicating missing
AIPROXY_API_ENDPOINTorAIPROXY_API_TOKEN. - Access the configured
FE_DOMAINaddress. Confirm that the frontend page loads normally, and internal tickets associated with campaign setup documents can be created normally. - Run a MongoDB connection test. Confirm that collection data related to campaign setup can be read and written normally.
- Check the Redis monitoring panel. Confirm that the connection count is within a normal range, with no frequent connection disconnections or timeouts.
The values provided are common starting points and should be measured 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.