Umeng Mini Program Promotion Channel Query

Problem

Mini program, H5, and mini game teams often need to answer questions such as which promotion channels brought new users yesterday, how a campaign trended over the past seven days, or whether a scene value such as QR-code scan is behaving as expected. The data comes from multiple read-only OpenAPI endpoints, and channel names, campaign names, internal IDs, and promotion-list code values are easy to mix up. This skill narrows the query path to five read-only interfaces.

How it works

The core workflow is to confirm that the application is a mini program, H5, or mini game and to obtain dataSourceId (AppKey). From there:
- Use umeng.umini.getCustomerSourceOverview to rank acquisition sources by channel, campaign, H5 scene, or other scene.
- Use getChannelOverview, getCampaignOverview, or getSceneOverview to inspect detailed metrics and time trends for a selected channel, campaign, or scene value.
- Use getSceneInfoList to list campaigns or channels, especially when the full promotion url is needed.
When the user supplies a Chinese channel or campaign name, first call the overview endpoint and take data[].id; pass that 26-character ID to the detail endpoint. Trend responses are ordered by dateTime in descending order, so data[0] is the latest point and data[-1] is the earliest point when calculating change.

Boundaries

The skill is read-only and does not create promotion links. It does not cover Android or iOS app channel analytics, which should use the App channel skill. H5 applications do not support getSceneOverview or the launch / onceDuration indicators; use sourceType=platform to compare H5 scene sources instead. The code returned by getSceneInfoList is a 25-character code and should not be used directly as channel or campaign.