What the data for this use case looks like
The data for this use case comes primarily from advertising placement platforms, internal material libraries, user interaction data, and conversion data. Daily produced documents include creative scripts, material test sheets, placement data reports, and iteration checklists. Most updates occur on a daily or weekly basis. Data fields include material type, creative variable combinations, placement time periods, conversion metrics, and others. Units include material duration, click volume, conversion cost, and others. Core processing steps focus on creative variable design, material fatigue assessment, and test conclusion summarization. Abnormalities directly impact placement performance.
Constraints on deployment and upgrade workflows
This page’s configuration guidance is based on FastGPT v4.17.0. Data sources for this use case are scattered and update frequencies are inconsistent. Deployment must support access formats for multiple data sources. Upgrades must maintain stability for data synchronization. Daily documents include multiple types of structured and unstructured content. Deployment must configure parsing rules adapted to different document types. Test conclusion summarization relies on complete historical data storage. Sufficient storage space must be reserved. Material compliance risks require adding a pre-deployment compliance check step. Upgrades must synchronously update the compliance rule library. The diversity of creative variable combinations requires the system to support flexible context loading configurations to avoid processing timeouts.
How to set configuration values
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://username:password@host:27017/fastgpt_creative_test | Adapts to the storage needs of this use case’s multi-source data, supports reading and writing of massive material and placement data |
REDIS_URL | redis://:password@host:6379/0 | Used to cache frequently accessed material test results and user interaction data, reduces database load |
DB_MAX_LINK | 200 | Matches the massive data connection volume requirements of daily updates for this use case, prevents connection exhaustion |
STORAGE_S3_ENDPOINT | https://s3-cn-beijing.aliyuncs.com | Adapts to the cloud storage needs of the material library, supports upload and download of large-volume video materials |
FE_DOMAIN | https://creative-test.ad-platform.com | Configures the frontend access domain name, ensures normal pushing of internal work orders and test results |
Three common configuration mistakes
- Persistently jumping download addresses before results appear after custom plugin runs: The frontend interface repeatedly refreshes the download link before returning a stable result. The cause is incorrect configuration of
REDIS_URLleading to cache failure. Plugin execution status cannot be persisted, and repeated pulling of execution logs causes delays. - Startup error during offline deployment: The terminal returns error messages indicating database connection failure or missing dependencies. The cause is failure to pre-configure dependency packages and local database connection parameters required for the offline environment, and failure to complete preparatory steps for offline image pulling.
- Response timeout when connecting multiple models: A 504 timeout status code is returned when calling advertising platform data interfaces. The cause is failure to set reasonable connection timeout parameters, which cannot adapt to the concurrent request requirements of multiple data sources for this use case.
How to verify successful configuration
- Run a database connection test command, verify that the
MONGODB_URIandREDIS_URLconfigurations can establish a normal connection. Confirm basic storage configuration is correct after a successful connection. - Upload a creative script and material test sheet, verify that the document parsing function works normally. Confirm document adaptation configuration is correct if parsing results include correct fields and data.
- Trigger an internal work order flow, confirm that work order messages can be pushed to the specified channel. Confirm that
FE_DOMAINand message push configuration is correct. - Run a custom plugin test task, observe whether the download link outputs stably without repeated jumping. Confirm cache configuration is correct.
The values provided here are common starting points and should be evaluated against the user’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.