What the data for this category looks like
Ad creative audit data sources include ad platform delivery creatives, landing page screenshots, product qualification documents, and the advertising law compliance clause library. Data update rhythms are split into real-time and daily batch modes. Real-time updates correspond to immediate audits after a single creative is submitted. Daily updates correspond to centralized verification of batch agency creatives. Daily processed documents include copy content for single creatives, landing page URLs and screenshots, violation records marked by auditors, and version logs of modifications and iterations. Data fields include creative unique identifiers, violation type codes, audit status, landing page verification results, and more. There are no unified fixed units. Some fields use character count or entry count as statistical dimensions.
What constraints do these characteristics impose on workflow orchestration?
Multi-source data sources require workflows to configure independent nodes to connect to ad platforms, landing page services, and compliance clause libraries. This avoids data pulling conflicts. The mixed update rhythm of real-time and daily updates requires workflows to support both event-triggered and scheduled pulling startup modes. This adapts to different audit scenarios. Diverse document types and field structures require variables in workflows to define categorized variables for different documents. Examples include creative copy length and landing page compliance status. A single creative audit error can lead to ad rejection or account restriction. Workflows must include verification nodes and failure fallback branches. This ensures abnormal links can be quickly located.
How to configure the settings
These configurations apply to the workflow orchestration feature of FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Trigger Timing | Trigger on creative update events, or perform batch pulling at 2 AM daily | Adapt to the needs of single creative immediate audit and centralized verification of batch agency creatives |
variables | Define three types of variables: violation count statistics, creative type, landing page verification result | Adapt to the needs of categorized statistics and cross-node status synchronization for ad creative audits |
nodeId | Assign unique identifiers to copy checking nodes and landing page verification nodes | Facilitate data flow between workflow nodes and failure fallback positioning |
| Failure Retry Count | 3 times, 60-second interval | Address scenarios of temporary network fluctuations or ad platform API call failures |
| Long Text Processing Threshold | 800–1200 characters | Adapt to the typical length range of ad creative copy, to avoid node timeouts |
| Variable Scope | Global | Adapt to the needs of cross-node audit status synchronization, ensuring variable values can be read across the entire workflow |
Three common configuration errors
- Variable updates do not display changes in the interface: the statistical values defined by
variablesdo not update alongside audit progress. The cause is that the variable scope is not set to global, and only takes effect within a single node. - Long copy generation results are truncated: the returned audit opinion only contains part of the copy content. The cause is that no processing threshold adapted to ad creative length is set, exceeding the node's default processing limit.
- Workflow nodes have no trigger records: the copy checking node corresponding to
nodeIdremains in a pending state. The cause is that the binding relationship between creative update events and the trigger node is not correctly associated.
How to confirm the configuration is correct
- Upload an ad creative containing violating copy, check if the workflow automatically triggers the copy checking node, to confirm the trigger timing configuration is effective.
- Manually trigger the violation count update operation for
variables, check the variable panel to confirm the value accumulates correctly, to verify the variable configuration and scope settings are correct. - Simulate an ad platform API return error, check if the workflow triggers the failure retry mechanism, to verify the retry count and interval configuration are effective.
- View the node log corresponding to
nodeId, confirm that data flow is normal, with no missing fields or format errors.
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.