What this category’s data looks like
Marketing content data is sourced from exclusive asset management systems across the group’s financial, insurance, and wealth management subsidiary business lines. Update schedules align with each subsidiary’s marketing campaigns, with no fixed cycle. Batch synchronization frequency is no less than once per day. The data uses structured JSON format, including fields such as unique asset identifier, affiliated business segment, content type, creation time, review status, and associated product code list.
material_unique_id is a string type. business_subject is an enumeration field. content_type falls into three categories: copywriting, visual assets, and scripts. associated_product_codes is an array type. Time fields use ISO 8601 format. Content text fields are counted by character count.
What constraints these characteristics impose on HTTP interfaces and external systems
The multi-business line data characteristics of diversified holdings require external interfaces to support filtering by the business_subject dimension. This allows accurate retrieval of marketing content for target businesses, and prevents assets from unrelated businesses from being included.
The on-demand update rhythm across multiple business lines requires interfaces to support both full pull and incremental pull modes. This adapts to the needs of different synchronization scenarios.
Structured data fields require interface request parameters to strictly validate enumeration values and array formats. This prevents invalid data from entering the knowledge base.
The multi-value attribute of associated product codes requires pagination logic to adapt to dynamic data volumes. This avoids missing some assets due to fixed pagination limit settings.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
external_api_allowed_fields | ["material_unique_id", "business_subject", "content_type", "publish_time", "associated_product_codes"] | Transmit only core necessary fields for marketing content, reducing interface transmission load |
external_api_batch_size | 50–100 items | Balance response speed and data processing efficiency for single requests, adapting to batch asset synchronization needs across multiple business lines |
external_api_timeout | 300 seconds | Full and incremental synchronization requests may include assets from multiple business lines, requiring sufficient response duration to avoid timeout interruptions |
rag_query_filter | {"associated_product_codes": {"$exists": true}} | Only recall valid marketing content associated with products, filtering invalid assets that have not been launched |
external_api_retry_count | 3 times | Address temporary network fluctuations or interface jitter, ensuring stability of synchronization tasks |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require targeted analysis, and it is recommended to test on your own samples before finalizing settings.
Three common errors
- Empty results are returned after calling the external marketing asset interface. Cause: Allowed fields for
external_api_allowed_fieldsare not configured, or filter fields do not match fields returned by the interface. - When viewing knowledge base history records, the
sourcefield only displays a fixed identifier, and specific asset source information cannot be viewed. Cause:material_unique_idorbusiness_subjectare not added as display fields in the knowledge base source configuration, only the default interface identifier is retained. - A
413 Request Entity Too Largeerror is triggered when connecting to an external monitoring system. Cause: A reasonableexternal_api_batch_sizevalue is not configured, and the number of assets pulled in a single request exceeds the load limit of the interface or system.
How to confirm configuration is complete
- Initiate a test pull request, and check whether returned fields match the configuration of
external_api_allowed_fields. - View the
sourcefield in knowledge base history records, and confirm that it includes relevant information about business segments and asset identifiers. - Submit a batch synchronization task, and check whether the interface response status code is within the normal range, with no timeout or error prompts.
- Configure monitoring alert rules, and verify that alert trigger conditions match the interface’s error status codes and response duration.
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.