What this category of data looks like
Data for this category mainly comes from advertising platforms, CRM systems, attribution SDKs, and form systems. The update frequency is typically daily or weekly. Regularly produced documents include attribution rule configuration tables, lead distribution tables, channel effect reports, and exception checklists. Core fields include channel identifier, lead unique ID, assigned sales account, conversion timestamp, and consumption amount. Data is stored in structured table format, with no semi-structured unstandardized content.
What constraints do these characteristics impose on the "sharing and embedding" workflow
Scattered data sources and differing update frequencies (daily and weekly) require the original business system to support pulling data within a specified time range, to avoid cross-cycle data confusion. Core fields contain structured content such as channel identifiers and lead IDs, so field mapping relationships must be retained to ensure that embedded attribution rules and lead distribution information match the original business system. Exception checklists involve sensitive information such as sales assignments, so permission checks must be configured to allow only authorized users to access via embedded links. The workflow must also support viewing needs for different roles, adapt display logic for scenarios such as growth operations and sales operations, which is defined by the original business system.
How to set configurations
Configurations in this chapter are formulated combining FastGPT non-login sharing channels and original business system rules.
| Configuration Item | Recommended Setting Method | Basis for This Setting |
|---|---|---|
Sharing entry shareId | Copy the full sharing link generated by the system, do not replace the identifier on your own | Identify the sharing entry; channel attribution and lead distribution business records and data permissions still need to be handled by external systems |
| Sharing link validity period | Test starting point: 7 days; adjust based on actual testing of channel attribution and lead distribution collaboration cycles and revocation requirements | Verify availability within the validity 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 | Limit the access frequency of a single user, which needs to be verified combined with request logs and actual load |
| Identity verification | When identity permission requirements exist, first verify business edition capabilities and the uid returned by the third-party identity service | Holding a sharing link does not equate to having business data permissions; third-party identity and data scope must be verified separately |
| Referenced content display | Select display configurations for referenced fragments, full text, and original text based on the sensitivity of channel attribution and lead distribution materials | Check displayed content within authorized data ranges; do not use hidden interfaces as a substitute for data permission control |
| Conversation record verification | Test example: Prepare 10 channel attribution and lead distribution Q&A samples, check on the same browser and another device respectively | Anonymous records rely on browser local identity, and retention cannot be guaranteed across devices or after cache clearing |
Three common errors
- Sharing entries related to channel attribution and lead distribution fail to open. First verify the full system-generated link and its validity period, then check browser request status; do not replace
shareIdon your own. - Visibility of channel attribution and lead distribution data does not match expectations. Verify third-party identity verification results, workflow request parameters, and external system data permissions separately; the sharing entry identifier itself does not provide business authorization.
- The same channel attribution and lead distribution Q&A is not visible on another device. For anonymous scenarios, first check device, browser, and local identity status; records cannot be guaranteed to be retained across devices or after cache clearing, do not judge service anomalies solely based on this phenomenon.
How to confirm configurations are complete
- Copy the full sharing link generated from Application Details - Publish Channels - Non-login window, open it in an incognito browser, and verify that the corresponding content loads normally.
- Add test URL parameters (such as
channel=test&leadId=123) to the end of the sharing link, open the embedded page, and check if the original business system can correctly obtain and display the corresponding parameter content. - Switch to an unauthorized account to access the embedded page, and verify that the original business system or third-party verification will intercept access or prompt no access permission.
- Wait for the original business system to complete data update, reopen the embedded page, and check that the displayed content matches the original business system.
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.