Channel Publisher Integration
This document is for channel publishers, apps, websites, WebViews, mini programs, and content distribution channels. It helps channels choose the appropriate MiniGame content integration method.
1. Integration Goals
MiniGame provides channel publishers with high-quality HTML5 game content, game slot recommendation capabilities, game center setup support, and monetization options. Channels can introduce game content into their own traffic scenarios to improve user dwell time, activity, reactivation, and monetization efficiency.
Typical benefits include:
Expand entertainment consumption scenarios with curated game content.
Improve user retention through game recommendations, tasks, campaigns, and content operations.
Quickly host game content through game slots, game centers, or channel entry points.
Support advertising, hybrid monetization, in-app purchases, and other business models.
2. Documentation
| Category | Document | Use Case |
|---|---|---|
| Game Slot API | Game Slot OpenAPI-V4 Integration Guide | Retrieve game slot content through OpenAPI from the server or client side and render it independently |
| Android SDK | Game Slot Android SDK Guide | Android apps that want to quickly integrate game slot components through the SDK |
| FAQ | Channel Publisher FAQ | Common questions about integration, debugging, data, settlement, and launch |
3. Choosing an Integration Method
3.1 OpenAPI-V4 Game Slot API
This option is suitable for channels that need custom UI, content orchestration, server-side aggregation, or consistent rendering across platforms. The channel requests one or more game slots through the API, receives game lists, jump links, and tracking information, and then handles rendering, click processing, and exposure triggering independently.
This method is suitable for:
Apps, Web, WebView, mini programs, or unified cross-platform content services.
Scenarios that need to combine MiniGame recommendations with the channel's own recommendation, campaign, or content systems.
Scenarios that require precise control over page layout, ranking strategy, caching strategy, and tracking logic.
3.2 Android SDK Game Slot Components
This option is suitable for Android apps that want to launch game slots quickly with lower engineering cost.
The SDK encapsulates initialization, game slot loading, component rendering, click jump, and exposure tracking, making it appropriate for standardized entry points and fast validation.
4. Recommended Integration Flow
Define the integration scenario: in-app entry, web page, game center, channel page, campaign page, or bot entry.
Choose the integration method: prioritize OpenAPI-V4 or the Android SDK.
Obtain integration credentials: MiniGame assigns the channel identifier, secret, game slot, or SDK initialization parameters.
Complete technical debugging: verify content requests, display, jumps, exposures, clicks, closing, and error fallbacks.
Configure operation strategy: MiniGame AI confirms the game slot style, count, ranking strategy, target country or region, language, and monetization method, then continuously optimizes based on post-launch user data feedback.
5. Launch Checklist
Production environment credentials have been obtained and isolated from test environment parameters.
Game display, click-to-open behavior, exposure reporting, and error fallback behavior have been verified.
The content caching strategy has been confirmed not to break tracking, ranking, or real-time operation requirements.
Dashboards or log diagnosis paths have been established for key metrics.
