What Data for This Category Looks Like
This category's data primarily comes from search ad backends, search term reports, bidding ranking data, and landing page data. Daily produced documents include keyword lists, negative keyword tables, bid records, and search term reports. Data update frequency is usually daily or weekly. Fields for individual documents include keyword text, match type, single bid amount (unit: yuan), average daily search volume, conversion link identifier, negative keyword activation status, and other relevant fields. Some summary reports also include cross-account statistical fields.
What Constraints These Characteristics Impose on Permission and Data Isolation
Data for this category is associated with different ad accounts and business entities. Keyword and bid data from different accounts are sensitive business information and require strict isolation. Frequently updated documents require permission configurations to take effect quickly to prevent data leaks or accidental operations. Operational boundaries differ significantly across roles. SEM optimizers need full read-write permissions. Agency operations personnel can only access specified data for signed clients. Brand marketing personnel can only view keywords and reports related to their own brand. Cross-account summary data requires additional aggregation permission configuration to prevent unauthorized personnel from accessing full industry data.
How to Set Up Configurations
FastGPT v4.17.0 supports the following configuration items:
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
teamId | Bind the unique identifier of the corresponding ad account | Accurately isolate keyword and report data from different ad accounts |
| Member role configuration | Preset three roles: SEM optimizer, agency operations, brand marketing | Match the operational boundaries of business roles |
| Data scope permission | Limit to the keyword scope of signed clients | Prevent cross-client data leaks |
| Sensitive field masking | Hide bid amount (unit: yuan) and conversion data fields | Adapt to the viewing needs of non-core roles |
| Ticket permission | Assign creation permission to on-call operations personnel, approval permission to administrators | Match the internal ticket workflow rules |
| SSO integration configuration | Enable enterprise-level SSO | Unify identity verification, comply with enterprise security requirements |
Three Common Configuration Mistakes
- Phenomenon: After assigning write permissions to other team members, the members still cannot create keyword list documents. Cause: The
teamIdparameter for the corresponding ad account is not bound, and the permission scope does not cover the target account. - Phenomenon: A 403 status code is returned when accessing search term reports. Cause: The data scope permission is not configured to the client scope to which the current member belongs, making cross-client data viewing impossible.
- Phenomenon: After submitting an internal operations ticket, the approval role does not receive a notification. Cause: Ticket creation permission is not configured for the on-call operations role, and permission rules do not cover the ticket workflow link.
How to Verify the Configuration Is Complete
- Switch to a test member account, attempt to access keyword data from a non-affiliated client, and confirm that viewing is not possible.
- Assign the permission for the corresponding
teamIdto the test member, attempt to create a keyword list document, and confirm that the operation can be completed normally. - Submit an internal operations ticket, confirm that the approval role can receive notifications and complete the approval process.
- Log in to the system using an enterprise SSO account, confirm that all resources within the configured scope can be accessed normally.
The values provided here 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.