This document is written for FastGPT v4.17.0.
What this category of data looks like
Data sources for campaign performance optimization scenarios include advertising platform backends, attribution systems, CRM lead databases, and landing page analytics tools. Updates occur daily or in real time. Daily output documents include daily and weekly campaign reports, single adjustment records, material A/B test data tables, and optimization review notes. Most fields are core advertising metrics such as impressions, clicks, conversions, and customer acquisition cost. Units include counts, yuan, cost per thousand impressions, and similar units. Most data structures use structured tables, while some review documents include unstructured text analysis content.
What constraints these characteristics impose on sharing and embedding
The real-time or daily update cadence of campaign data requires embedded Q&A systems to pull or refresh data from external sources on a scheduled or real-time basis. This logic is implemented separately by external systems or calling parties. FastGPT only provides a basic sharing and embedding carrier to avoid viewing outdated report content during on-call operations.
Structured adjustment records, test tables, and similar documents require embedded components to retain the original table row-column format and field mapping via external data source format configuration. FastGPT’s sharing and embedding components only provide basic display capabilities. This adaptation logic is implemented separately by external systems; otherwise, detailed advertising metrics cannot be displayed accurately.
The privacy requirements of internal operations and ticket scenarios require sharing links to have access permission configurations (business editions support identity verification integration with third-party systems) to prevent sensitive campaign budget and conversion data from being accessed by external parties. Holding the shareId alone must not be used as an authorization basis.
The diverse fields of advertising metrics require embedded Q&A systems to accurately connect to the external data sources of corresponding projects. This connection logic is implemented separately by external systems or calling parties. FastGPT only provides a basic sharing and embedding carrier to avoid cross-project data confusion that could affect decision-making.
How to set configurations
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
Sharing entry shareId | Copy the full share link generated by the system; do not manually replace the identifier | Identifies the sharing entry; campaign performance optimization business records and data permissions must still be handled by external systems |
| Share link validity period | Test starting point: 7 days; adjust based on campaign performance optimization collaboration cycles and revocation requirements | Verify that the link works within the valid period and access behavior after expiration; this value is not an official default or industry statistic |
| QPM | Test starting point: 20 requests per user per minute; adjust based on actual load | Limits the access frequency of a single user; must be verified combined with request logs and actual load |
| Identity verification | When identity permission requirements apply, first verify business edition capabilities and the uid returned by the third-party identity service | Holding a share link does not equal having business data permissions; third-party identity and data scope must be verified separately |
| Cited content display | Select display configurations for snippets, full text, or original source based on the sensitivity of campaign performance optimization materials | Check displayed content within authorized data ranges; hidden interfaces cannot replace data permission controls |
| Conversation record verification | Test example: Prepare 10 campaign performance optimization Q&A samples, check them on the same browser and another device respectively | Anonymous records rely on browser local identity; records cannot be guaranteed to persist across devices or after cache clearance |
Three common mistakes
- Campaign performance optimization-related sharing links fail to open. First verify the full system-generated link and its validity period, then check browser request statuses. Do not manually replace
shareId. - The visible scope of campaign performance optimization data does not match expectations. Verify third-party identity verification results, workflow request parameters, and external system data permissions separately. The sharing entry identifier alone does not provide business authorization.
- The same campaign performance optimization Q&A is not visible on another device. For anonymous scenarios, first check device, browser, and local identity status. Records cannot be guaranteed to persist across devices or after cache clearance; do not use this phenomenon alone to judge service anomalies.
How to confirm proper configuration
- Access the embedded link using a mainstream browser that does not use the IE kernel. Confirm that the page loads normally and displays the corresponding campaign optimization Q&A content and data.
- Submit a question related to the current campaign project. Confirm that the Q&A results match the project’s advertising metrics and historical document content.
- Check the
shareIdparameter in the embedded code. Confirm that it is the system-generated value copied from App Details > Release Channels > Guest Access Window, and matches the sharing entry of the current campaign optimization project. - Attempt to access the embedded link using a non-whitelisted account. Confirm that the page fails to load normally or prompts insufficient permissions.
All configuration values provided are common starting points and should be evaluated 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.