What the data for this category looks like
Profitability data for brand agency services comes primarily from partner brands’ e-commerce store backends, advertising platform backends, and internal ledgers for agency services. Data is updated daily, corresponding to the previous day’s operational metrics. Each daily profitability report includes fields such as service brand identifier, total daily revenue, channel advertising costs, service revenue share, conversion volume, reach volume, and revenue per customer. Units are mostly Chinese yuan (CNY) and counts. Some fields require dimension splitting based on the agency’s subdivided service categories.
What constraints do these characteristics impose on forms and interactions
The daily updated data requirement means the form must include a scheduled trigger to pull the previous day’s data, to avoid using expired data for reports. The multi-field and dimension-splitting structure requires the form to preset filter dimensions such as brand and channel, to reduce manual input steps, and support aggregated data display by dimension. Multiple data sources require the form to connect to multiple interfaces including e-commerce backends and ad platforms. The interaction flow must include data consistency checks, such as verifying that total revenue matches the sum of revenue from all channels, and trigger alerts for discrepancies. For dialogue scenarios, the interaction must support automatically matching corresponding report data when a user enters a brand keyword, without requiring manual upload or full field entry.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
formFieldPreset | brand logo, daily total revenue, channel placement cost, service share ratio, conversion visits, reach visits | Matches the standard field structure of brand agency profitability daily reports, covers core business data |
dataSyncInterval | 86400 seconds | Adapts to the daily data update rhythm, scheduled to pull the previous day’s operational data |
multiSourceDataCheck | Enabled | Validates consistency across multiple data sources, prevents discrepancies between total revenue and the sum of channel revenues |
dialogueFormTrigger | trigger by brand keyword | Adapts to interaction habits in dialogue scenarios, users enter a brand name to summon the corresponding form |
formFieldFilter | filter by service category | Adapts to data splitting requirements for subdivided agency service categories, supports filtering fields by category |
workflowFormTimeout | 300 seconds | Covers average response times across multi-platform interfaces, prevents data pull timeouts and interruptions |
The parameter values provided on this page are all common recommended starting points for defining configurations. Actual values are affected by material form, data volume, and business rules. Specific issues require specific analysis. It is recommended to test on your own samples before finalizing settings.
Three common configuration errors
- Phenomenon: Form fields configured in the workflow do not display in the dialogue interface, and interaction buttons are unresponsive. Cause: The dialogue trigger configuration for
dialogueFormTriggeris not enabled, or preset fields are not bound to workflow nodes. - Phenomenon: No subsequent connection action occurs after form submission, and no contact request is received on the WeChat Work channel. Cause: The message push parameter for
formSubmitCallbackis not configured, or the WeChat Work receiving account is not bound. - Phenomenon: Multi-source data pull times out, returning empty fields or status code
504. Cause: The value set forworkflowFormTimeoutis too short, failing to cover response times across multi-platform interfaces.
How to confirm configurations are correctly set
- A preset brand keyword entered in the FastGPT test dialogue interface triggers automatic display of the form with corresponding fields.
- Manual data synchronization triggers pulls of fields that match the field list configured in
formFieldPreset. - Submitting a test form triggers the preset callback action, such as pushing a message to a specified channel.
- Workflow run logs show no abnormal prompts for multi-source data check results.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.