Data Characteristics for This Category
This category’s data primarily originates from landing page access logs, heatmaps, form submission data, and ad source parameters. Daily associated documents include landing page plans, tracking requirement documents, AB test reports, and form field lists. Data is split by ad campaign, landing page version, and activity cycle. Updates occur weekly or after a single campaign ends. Data fields include page dwell time, form submission link nodes, ad utm parameter values, and landing page version identifiers. No fixed statistical percentage metrics are included. Only raw behavior and configuration information are recorded.
Constraints on Permissions and Data Isolation
Landing page conversion optimization data is associated with multi-dimensional business identifiers, and involves ad delivery cost and lead data. Permission isolation must match the hierarchy of ad campaigns and landing page versions. Data updated per activity cycle must strictly limit access scope to avoid cross-team data confusion. Form data is directly bound to user leads. Only authorized growth product and front-end operations personnel can access the corresponding team’s dataset. Ad source parameters are linked to delivery costs. Permission configuration must align with the team’s ad delivery permissions to prevent unauthorized access leading to cost information leakage. Historical version AB test reports must be stored separately by tmbId and teamId to avoid cross-team data overlap.
Configuration Settings
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
teamId binding rule | Bind to ad delivery account ownership, match team permission hierarchy | Align with ad delivery business permissions to ensure only authorized teams can access corresponding data |
tmbId storage rule | Assign a unique tmbId to each landing page version, based on actual measurement | Distinguish landing page data for different activities to prevent cross-version data confusion |
| Data access time range | Only allow viewing activity data from the past 7 days under the corresponding teamId | Limit access to historical data to reduce data leakage risks |
| Historical version isolation rule | Filter data by both tmbId and teamId dimensions | Avoid cross-activity and cross-team overlap of AB test reports and log data |
| Form data permission | Only accounts bound with ad delivery permissions can view | Protect form submission lead data and delivery-related information |
Three Common Misconfigurations
- Phenomenon: After adding a custom plugin to a workflow, no input or output parameters are displayed, and no error logs are generated. Cause: The plugin’s access permissions are not bound via
teamId, causing the plugin configuration to not sync to the corresponding team’s workflow environment. - Phenomenon: A team cannot create multi-account shared login, and added table data does not take effect. Cause: The team association rule for
teamIdis not configured correctly, causing the account-team binding relationship to not take effect. - Phenomenon: When exporting application historical versions, the
tmbIdfield is missing in earlier versions. Cause: The automatic fill configuration for historical versiontmbIdis not enabled, causing old version data to lack isolation identifiers.
How to Confirm Correct Configuration
In FastGPT v4.17.0:
- Access via accounts from different teams, and confirm only landing page data and activity logs under the corresponding
teamIdare accessible. - When a new landing page version is uploaded, confirm the system automatically generates a unique
tmbIdand associates it with the corresponding activity data. - When cross-team account access is tested, confirm other teams’ form submission data and ad source parameters are not visible.
- When historical version data is viewed, confirm each record carries the
tmbIdandteamIdfields.
The values provided are common starting points and should be evaluated against the relevant deployment’s own sample data.
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.