What the data for this category looks like
Thermal data related to thermal marketing comes from three sources: utility-side thermal supply terminal operation logs, passenger flow thermal collection devices at offline service outlets, and click heat mapping tools for online marketing pages.
Data update cadence has two categories: Real-time terminal and touchpoint data updates every 5 minutes. Offline regional thermal distribution data is generated in daily batches.
Data documents use structured JSON format with the following fields:
- Thermal Area Code: string, 6-digit administrative division code
- Statistical Period: ISO 8601 format timestamp
- Thermal Value: integer, unit: visits per square meter
- Associated Marketing Touchpoint ID: string, unique identifier for marketing reach nodes
What constraints these characteristics impose on deployment and upgrade
Real-time 5-minute updated thermal data requires a low-latency streaming data access channel during deployment. Otherwise, marketing content updates will lag and fail to match real-time thermal changes.
Daily offline batch-imported thermal data has a large volume. Configure scheduled tasks to run during off-peak business hours to avoid occupying core business resources.
The integer unit of the Thermal Value field requires strict numerical range verification during data parsing. This prevents abnormal collected data from flowing into the knowledge base.
The cross-system binding requirement for associated marketing touchpoint IDs requires a dedicated ID mapping interface during deployment. This ensures precise matching between thermal data and marketing content.
Configuration Settings
| Config Item | Recommended Value | Rationale |
|---|---|---|
HEAT_DATA_SYNC_INTERVAL | 300 seconds | Matches the 5-minute update frequency of thermal data to ensure real-time updates of marketing content |
PARSE_HEAT_DATA_TIMEOUT | 60 seconds | Adapts to the parsing duration of a single thermal data entry to avoid timeout for single synchronization tasks |
BATCH_IMPORT_MAX_SIZE | 1000 MB | Limits the volume of daily batch-imported offline thermal data to prevent excessive server load |
HEAT_DATA_VALID_RANGE | 0–10000 | Verifies the reasonable range of thermal values to filter invalid data from abnormal collections |
CONTACT_ID_ASSOCIATION_ENABLE | Enabled | Enables association mapping rules to ensure precise binding between thermal areas and marketing touchpoints |
UPLOAD_HEAT_DATA_STRICT_MODE | Enabled | Enables strict verification mode to ensure field integrity and format compliance for imported data |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by data format, volume and business rules. Specific issues require individual analysis. It is recommended to test against your own samples before finalizing settings.
Three common mistakes
- Symptom: A
400 Bad Requesterror occurs during thermal data synchronization, with a prompt about field format mismatch. Cause:UPLOAD_HEAT_DATA_STRICT_MODEis not enabled, leading to unstructured redundant fields being imported. - Symptom: Batch import tasks for offline thermal data continue to time out. Cause: The
BATCH_IMPORT_MAX_SIZEconfiguration is not adjusted, and the imported volume exceeds the load limit of the deployment node. - Symptom: A
403 Forbiddenerror occurs during multi-model combined calls, and APIKEY cannot be allocated by group. Cause: Association mapping rules for multiple APIKEYs are not properly configured, and environment variables for KEY groups are not added to the deployment configuration.
How to confirm configuration is complete
- Upload a test thermal data entry that complies with field specifications, view the parsed preview interface, and confirm that all fields are displayed normally with no format abnormalities or missing content.
- Manually trigger a scheduled synchronization task, view the synchronization duration in the system logs, and confirm that it matches the preset synchronization interval configuration.
- Call the association mapping interface, enter a test thermal area code, and verify that the preset marketing touchpoint ID is returned.
- Restart the deployment node, check the running status of the data synchronization task, and confirm that there are no startup failure log errors.
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.