Code and Change Review Assistance for Information Flow Ad Creative Testing: Citation Sources and Traceability

Data for this category primarily comes from advertising placement platforms, creative asset libraries, user interaction data, and backend conversion

What the data for this category looks like

Data for this category primarily comes from advertising placement platforms, creative asset libraries, user interaction data, and backend conversion data. Updates occur on a daily or weekly basis. Commonly associated documents include creative scripts, asset test sheets, placement data reports, and iteration checklists. Core fields include asset unique identifiers, graphic-video combined copy, click-through rate, conversion cost, placement time slots, and more. There are no unified fixed statistical units; fields and units are flexibly adjusted based on specific placement goals.

Data from multiple sources must be clearly traced to the corresponding advertising platform or asset library to avoid confusion between creative assets from different channels. Dynamic data updated daily or weekly requires the traceability link to support near-real-time pulling of the latest versions, ensuring that the referenced creative combination is currently active. In scenarios with multiple associated documents, traceability must be bound to specific iteration checklist items and test sheet rows to prevent cross-version reference errors. The non-standardized nature of core fields requires traceability configuration to adapt to flexible field mapping rules, accommodating field differences across different placement targets.

How to configure the settings

This configuration applies to FastGPT v4.17.0.

Configuration ItemRecommended SettingRationale
quoteMaxToken1000–1400 tokenAdapts to the typical content length of information flow creative test documents, retains complete traceability information
responseDataEnable traceability associationBinds placement data and asset sources for creative testing, meets attribution requirements for growth teams
detailFull displayShows core traceability fields such as asset ID and placement time slots, adapts to verification needs for test reports
Traceability channel grouping rulesClassify by advertising platformDistinguishes creative assets from different channels, avoids cross-platform data confusion
Traceability update cycleSync daily at midnightMatches the daily update data rhythm of this category, ensures reference to currently active creative combinations

Three common configuration mistakes

  • Symptom: An error appears when viewing knowledge base citations, with the interface prompting "Missing traceability data". Cause: The responseData association switch is not configured, preventing binding of creative test placement data and asset sources.
  • Symptom: Knowledge base search input and response citations are forcibly displayed in responses, with no way to hide them. Cause: Custom display configuration for traceability details is not enabled, and all traceability fields are displayed by default.
  • Symptom: The referenced creative asset version does not match the current iteration checklist. Cause: The traceability update cycle is set too long, failing to sync the latest creative iteration data.

How to confirm the configuration is applied correctly

  • Upload an information flow creative test script and asset test sheet, trigger the code change review process, and check if the citation traceability module displays the associated information of the corresponding documents.
  • Adjust the quoteMaxToken parameter value, verify that the truncation logic of referenced content conforms to the configured token range.
  • Disable the responseData switch, confirm that the traceability module no longer displays placement data association information, and verify that the configuration takes effect.
  • View the traceability details module, confirm that when detail is set to full display, core fields such as asset ID and placement time slots are shown.

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.