What data for this category looks like
Sources of data for advertising and marketing intelligent due diligence reports include advertising platform APIs, media monitoring tool interfaces, third-party public opinion systems, and compliance filing databases. Data update frequencies vary widely. Real-time exposure and conversion data for advertising campaigns updates hourly. Public opinion data updates every minute. Compliance filing data updates quarterly.
A single report follows a standard document structure. It includes fields such as media resource identifier, delivery period, impression count, conversion count, budget amount, and compliance keyword hit status. Common units are counts, units, and yuan. Some data sources present data using thousand impressions or ten thousand yuan as units.
Constraints on HTTP interfaces and external systems
Multiple data source access requirements demand configuration of multiple independent external API endpoints. Each endpoint uses unique authentication methods and request formats, requiring separate adaptation. Different update frequencies require distinct polling intervals. This avoids triggering rate limits via high-frequency calls. Inconsistent fields and units require dedicated mapping and conversion rules. Without these rules, due diligence report data becomes disorganized.
Compliance data sources have stricter access frequency limits. Additional rate limiting configurations are needed to prevent temporary interface bans.
How to configure settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
external_api_auth_type | Selected based on the connected platform, such as api_key or oauth2_client_credentials | Authentication standards vary across advertising and marketing data sources. Advertising platforms mostly use API Key, while compliance filing interfaces mostly use OAuth2 |
external_api_poll_interval | 1–5 minutes | Advertising campaign data updates hourly, public opinion data updates every minute. This middle range balances real-time performance and call quotas |
field_mapping_rule | Map data source fields to standard fields such as media_id, put_time, impression_count | Field naming differs widely across advertising and marketing data sources. Unified mapping supports subsequent processing logic |
request_rate_limit | 100 requests/minute | Most advertising platform API rate limits fall between 100-200 requests per minute. Using the lower end of the range avoids triggering rate limits |
response_parse_timeout | 30 seconds | Advertising data interfaces return large datasets. 30 seconds covers most normal response durations |
unit_conversion_config | Enable thousand impressions to single impressions and ten thousand yuan to yuan | Inconsistent unit formats across data sources. Unifying units ensures consistency in due diligence report data |
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 individual analysis. It is recommended to test on your own samples before finalizing settings.
Three common configuration mistakes
- Receiving 404 errors when calling third-party advertising platform APIs. The cause is incorrect configuration of the interface endpoint path. Some platforms have different API version paths; for example, the v2 version interface of some media platforms uses a different path than the v1 version.
- Empty data fields returned by interfaces. The cause is incorrect configuration of field mapping rules. Nested fields from advertising and marketing data sources, such as
data.report.impression, are not extracted correctly, preventing subsequent processing from obtaining valid data. - Triggering rate limit errors from interface calls. The cause is setting an unreasonable request rate limit threshold. High-frequency calls to advertising platform APIs result in temporary access bans from the platform.
How to confirm successful configuration
- Initiate a single test call, check if the raw data returned by the interface matches the data shown in the third-party platform's console.
- Verify that the standard fields after field mapping are complete, with no missing values or format errors.
- Review call logs to confirm that request frequency does not exceed the configured rate limit threshold, and that there are no 404 or rate limit errors.
- Trigger the due diligence report generation process, confirm that the generated report includes correct advertising campaign data and unified unit formats.
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.