What data for this category looks like
Core advertising and marketing data comes from landing page form submissions, interaction logs from ad campaign backends, and user behavior data linked to creative materials. Data sources include tracking pixels from delivery channels, form control interaction records on landing pages, and budget and conversion linked data for ad campaigns. Form submission events are synced in real time. Cumulative data from channel campaigns is aggregated daily. Individual data entries follow this structure: ad creative ID, delivery channel code, form fields (such as contact information, demand descriptions), interaction dwell time, number of submit button clicks, and linked ad campaign ID. Unit specifications: dwell time is measured in seconds, click counts use positive integers, creative ID and channel code use string format, and the demand description field has a large allowable length range.
Constraints imposed by these characteristics on forms and interactions
Advertising and marketing data is linked to ad campaigns and delivery channels. Form interaction processes must carry linked parameters to ensure submitted data can be traced back to specific ad campaigns. Real-time sync requirements mandate that form submission data be synced to the campaign backend immediately. This avoids delayed campaign adjustments caused by data latency. Form fields have custom requirements, such as budget range and delivery region exclusive fields. These require configuration for non-standard controls. Long-text demand description fields require forms to support validation and storage for long-text input, to prevent submitted content from being truncated. Interaction data must be linked to specific user behaviors. Form interaction logs must record complete data for user dwell time, button clicks, and other steps.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
formCustomFields | Include ad campaign ID, delivery region, budget range | Match the exclusive data field requirements of advertising and marketing scenarios, ensure submitted data can be linked to specific ad campaigns |
formMaxLength | 800–1200 characters | Adapt to long-text input for demand descriptions in advertising and marketing scenarios, prevent content truncation |
formSubmitSyncEndpoint | Bind to the callback interface of the ad delivery backend | Ensure data submitted via forms is synced to the delivery system in real time, meet data traceability and campaign adjustment requirements |
formCustomControlEnabled | Enabled | Support exclusive controls such as delivery region selectors and budget sliders, replace the 3 built-in basic controls |
formSubmitSyncTimeout | 600 seconds | Avoid submission failure caused by network latency during synchronization, adapt to the interface response rhythm of the ad delivery backend |
formFieldRequired | Configure ad campaign ID and contact information as required fields | Ensure core data fields are not omitted, guarantee the integrity of subsequent campaign analysis |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require targeted analysis. It is recommended to test on your own samples before finalizing settings.
Three common configuration errors
- Symptom: The linked ad campaign ID field is empty after form submission. Cause: The field was not added to the
formCustomFieldsconfiguration, so no linked parameters are included in submitted data. - Symptom: Only 3 built-in form controls appear in the interface, and custom field controls cannot be added. Cause: The
formCustomControlEnabledconfiguration item was not enabled. The platform loads only built-in basic controls by default. - Symptom: Long-text form submission data cannot be effectively retrieved during knowledge base search. Cause:
formMaxLengthwas not set to a reasonable range, causing excessively long input content to be truncated or not properly tokenized.
How to verify correct configuration
- Access the application's form configuration interface, review the
formCustomFieldslist, and confirm that exclusive fields such as ad campaign ID and delivery region have been added. - Submit a test form, log in to the callback interface of the ad delivery backend, and confirm that all configured fields are present in the submitted data.
- After enabling the
formCustomControlEnabledconfiguration, refresh the form preview page, and confirm that custom controls display normally. - Submit long-text content, run a knowledge base search, and confirm that long-text fragments can be retrieved normally.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.