What the Data for This Category Looks Like
The revenue rate and market data for e-commerce services is sourced from open transaction reconciliation interfaces provided by e-commerce platforms and third-party e-commerce market data aggregation services. Updates run at fixed daily times to sync full reconciliation data from the previous calendar day. Data documents use structured formats, including core items such as merchant unique identifiers, transaction time dimensions, revenue reconciliation fields, and benchmark reference fields. Field units follow general e-commerce industry transaction and reconciliation standards, with no custom special units. Data only includes reconciliation records for completed transactions, excludes unsettled estimated revenue, and only permits query access to historical data from the past 90 days.
What Constraints These Characteristics Impose on Sharing and Embedding
The fixed daily update schedule for data requires shared content to be configured with a timed refresh mechanism, to avoid displaying expired historical data that could impact merchant decision-making. The structured field format requires embedded components to support formatted display of key-value pair data, and cannot directly use plain text rendering logic. Components must adapt to e-commerce merchants’ requirements for data readability. The restriction that only the past 90 days of historical data is accessible requires shared links or embedded components to verify request time ranges, block query requests that exceed permitted scope, and prevent data leaks. The rule that only completed transaction reconciliation data is included requires embedded logic to automatically filter unsettled estimated revenue fields, to avoid displaying inaccurate revenue information that could mislead merchant judgments. The merchant unique identifier field requires sharing configurations to be bound to the corresponding merchant’s permission identifier, to prevent cross-merchant data leaks and ensure data security.
How to Configure Settings
| Configuration Item | Recommended Value | Rationale for This Value |
|---|---|---|
share_expire_days | 90 days | Matches the platform’s permission restriction of only allowing access to the past 90 days of historical data, to avoid requests outside the legal scope |
refresh_interval | 86400 seconds | Adapts to the fixed daily data update sync schedule, to ensure the latest reconciliation results are displayed |
tenant_permission | Bind to current merchant tenant | Filters transaction data from non-current merchants, to prevent cross-merchant data leaks |
mobile_adapt | Enable full-screen adaptive display | Adapts to e-commerce merchants’ scenario of viewing daily market reports on mobile devices, to improve mobile access experience |
iframe_same_origin | Enabled | Resolves cross-site login status exception issues during iframe embedding, to ensure normal session state synchronization |
custom_avatar | Upload merchant’s own brand avatar | Replaces the default avatar with the merchant’s own brand avatar, to align with the merchant’s brand display requirements |
The parameter values provided on this page are all common recommended starting points for configuration setup. Actual values are affected by material form, data volume, and business rules. Specific issues require case-by-case analysis. It is recommended to conduct testing with relevant samples before finalizing settings.
Three Common Configuration Mistakes
- Symptom: No relevant identity authentication options appear in the sharing configuration interface. Cause: The tenant-specific background configuration page for the corresponding merchant was not accessed, and authentication options for versions v4.9.11 and above are only visible on the tenant-specific configuration page.
- Symptom: After embedding a page via iframe, login status is immediately lost after logging in, with a 403 status code returned. Cause: The
iframe_same_originconfiguration was not enabled, cross-site requests are blocked by the browser’s same-origin policy, and session state cannot be synchronized. - Symptom: The avatar in the sharing window is not updated to the custom avatar. Cause: A custom avatar file meeting format requirements was not uploaded, or changes to the
custom_avatarconfiguration were not saved.
How to Confirm Configurations Are Set Correctly
- Access the sharing link, check if the displayed data time range meets the preset permission requirements, to confirm that the configured time restriction takes effect.
- Use a mobile device to access the embedded page, check if the component layout adapts to the screen size, with no content overflow or misalignment.
- Use an unauthorized account or tenant identity to access the sharing link, confirm that corresponding data cannot be obtained, to verify that the identity authentication configuration takes effect.
- Wait for the preset refresh cycle, then refresh the page, check if the displayed data is updated to the latest reconciliation results, to confirm that the timed refresh configuration takes effect.
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.