What this category of data looks like
This document is written based on FastGPT v4.17.0. Data for this category typically comes from search ad backends, search term reports, bidding ranking data, and landing page data. Daily generated documents include keyword lists, negative keyword tables, bid records, and search term reports. Core fields include keyword text, match mode, bid amount, monthly search volume, conversion attribution identifier, and others. Data update frequency is primarily daily or weekly. The number of entries per document varies with the scale of the ad account, with no fixed unified value.
What constraints these characteristics impose on the permissions and data isolation link
Data for this category includes sensitive business information such as bidding strategies and conversion attribution, and involves permission division for multiple user roles (such as SEM optimizers, agency operations staff, brand marketing teams). In scenarios with parallel management of multiple accounts, strict isolation of keyword data from different customers or sub-accounts is required to prevent cross-account data leaks. At the same time, keyword report shared links that do not require login must be bound to permission scopes to prevent unauthorized access to sensitive ad data. Additionally, team members’ operations must match the management permissions of the corresponding account to avoid unauthorized modification of negative keywords or bid records.
How to set the configurations
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
| Team data binding | Associate corresponding ad accounts by teamId | Achieve physical isolation of ad data across different teams |
| No-login share link limit | 10–100 per application | Adapt sharing needs from small and medium-sized teams to large agencies |
| Member operation verification | Verify permission scopes by tmbId | Prevent unauthorized modification of keywords or bid records |
| Data access granularity | Split data sets by ad sub-account | Match business scenarios of parallel multi-account management |
| Operation log retention | 30–90 days | Meet operational traceability requirements for compliance reviews |
Three common mistakes
- Phenomenon: A prompt reading "No permission to operate this conversation record" appears on the interface. Cause: The current operating account is not bound to the
teamIdscope of the corresponding ad account, resulting in permission verification failure. - Phenomenon: The no-login window fails to create share links exceeding 10 in quantity. Cause: The no-login share link limit configuration in the application is not adjusted, and the default limit is 10 per application.
- Phenomenon: Cross-team members can view keyword data or bid records of other customers. Cause: The data isolation granularity is not configured by ad sub-account, resulting in data not being split by
teamId.
How to confirm the configuration is complete
- Attempt to access the shared keyword report link using an unauthorized account, confirm that sensitive data content cannot be viewed.
- Enter the application configuration page, check the no-login share link limit parameter, confirm that the value meets the current business sharing needs.
- Switch to different team accounts, verify that only ad account data bound to the corresponding
teamIdcan be operated. - View the operation log module, confirm that members’ keyword modification, bid adjustment and other operations are fully recorded.
The values provided here 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.