A WeChat Mini Program Livestream Launch Checklist: Shares, Product Routes, Analytics and Return Paths
Before launch, test the production Mini Program journey from a shared card through viewing, product detail, order attribution and return to the room.
A successful proof of concept is not the final launch check. Before publishing a Mini Program livestream event, run the journey from the real entry point through viewing, sharing, product detail, a test order and return. Use the production AppID, final domains, channel settings and experience build. A room can play correctly while member identity, product routes or attribution still break the event.
Use production configuration to test sharing, products, orders, analytics and return to the room before launch.
01 / Entry and sharing
Enter from each intended home, member, store or course page and verify channel and campaign parameters. Share a real Mini Program card to another account and verify its landing page, login, channel and source. Provide meaningful states before a stream starts and after it ends. A WebView route should check its H5 and Mini Program share paths; a native host should manage share parameters consistently.
02 / Products and orders
Click a room product and inspect product ID, campaign ID, member price, stock, coupon rules and destination. Place a test order and return to the room. Include removed products, unavailable stores, logged-out members and canceled payment. A WebView route also needs business-domain, WeChat JS-SDK and H5-to-Mini-Program checks; native and uni-app routes need component callback and host navigation checks.
03 / Analytics and attribution
Define events for room entry, playback, viewing, interaction, product click, order and return. Use one test member and campaign ID to connect front-end events, server orders and reports. Record only the necessary business data; manage sensitive identifiers on the server. If a product opens but its order has no campaign source, the launch journey is incomplete.
04 / Playback and return
Test live, replay, network interruption, payment-page return and repeated room entry on target iOS and Android devices. If small-window playback is enabled, check the transition to product detail, closing the window and avoiding duplicate playback on return. POLYV’s documented WebView intermediary covers live viewing; replay needs its own validation.
05 / Release and rollback
Recheck the production AppID’s categories, plugin and player permissions, business domains, privacy notice, channel configuration and component version. Close launch blockers before submitting for WeChat review, and retain the previous package and configuration record. Assign operations, engineering and QA owners for event-day checks of public share cards and real order paths.
06 / End-to-end checks before review submission
Run these cases in the production AppID experience build with final channel settings. Record account, device, evidence and owner for each row.
| Step | Action | Launch blocker |
|---|---|---|
| Shared card | Open a card from a real chat | Wrong channel, lost source or failed login |
| Viewing and replay | Watch live, then open replay after processing | Blank page, wrong channel or bypassed access |
| Product detail | Click available, removed and out-of-stock items | Wrong item, broken route or invalid stock rule |
| Order attribution | Place a test order and inspect server data | Missing member, product or campaign source |
| Analytics | Reconcile entry, play, product, order and return events | Missing core event or duplicate event |
| Return and small window | Return after canceled/completed payment | Double audio, black screen, wrong back stack or lost identity |
After changing the build or production domains, rerun the affected entry-to-order journey. Keep the previous package, channel settings and event-day owners available.
Frequently Asked Questions
Why retest after a successful POC? POCs often use test channels and domains; launch regression verifies production configuration and the complete customer journey.
Can testing stop in developer tools? No. Sharing, playback, small windows and return navigation need target iOS and Android devices.
What should be sampled after launch? Check a public share card, production product page, order attribution and return to the room.
Further Reading
Continue with What Should a WeChat Mini Program Livestream POC Test? A Script for Live, Replay, Chat, Products and Login and Livestream Plays but the Product Will Not Open: Troubleshooting WebView Domains and Mini Program Navigation. For the overall integration choice, see the WeChat Mini Program SDK guide. The Chinese edition covers the same task for local teams.
About POLYV
A POLYV viewing page can enter an existing Mini Program, while the company’s host and business systems still own launch checks for sharing, products, orders and analytics. See the developer center for route-specific scope.