Mini-program analytics WeChat, Alipay and Douyin mini-programs. One console.
Did users arrive from a QR code, a share, search or an article? Did the share bring new users back? How do pages flow? Each platform keeps its own scene names, compared on one report.
- WeChat · Alipay · Douyin
- Scene-value analysis
- Shares and return traffic
- Same person as web and app
Visitors
48,213
▲ 12.4%
New users
6,120
▲ 9.1%
Shares
9,860
▲ 6.7%
D1 retention
38.4%
▲ 2.1 pts
Avg. stay
2m 48s
▲ 14s
Visitors · daily
This periodPreviousPlatform share
- WeChat58%
- Alipay27%
- Douyin15%
Three platforms in one project; scene values keep their original names.
Six numbers to read first
Visits, new users, active users, retention, stay and shares. Each one splits by platform, scene and page.
Visitors
48,213▲ 12.4%
Unique users who opened the mini-program in 14 days, all three platforms combined.
New users
6,120▲ 9.1%
First-time opens. 38% of them arrived through a share.
Active users
21,480▲ 6.7%
DAU, WAU and MAU, with D1 and D7 active retention.
D1 retention
38.4%▲ 2.1 pts
New users who open again the next day. QR-code arrivals are highest at 41%.
Avg. stay
2m 48s▲ 14s
Median session length. Campaign pages pull the average up.
Shares
9,860▲ 18.2%
Forwarded cards and copied links, with 4,120 return opens.
Which entrance did users come through
WeChat scene values, Alipay sources and Douyin entrances become one table. QR code, share, search, article, chat — every entrance shows visits, share, D1 retention and order rate.
- Retention and order rate per entrance, not just visits
- Switch platform; scene names stay as the platform calls them
- New scenes land in "Other" and raise a notice
Example scenario: Before Singles' Day, ops swapped 20 store posters for parameterised mini-program codes. After the campaign, scene values showed which stores were scanned most and which barely at all — the next print run was allocated accordingly.
Entrance mix
- Share31%
- QR code21%
- Search17%
- Other31%
| Scene | Entrance | Visits | Share | D1 | Order rate |
|---|---|---|---|---|---|
| 1011 | 1-to-1 chat | 14,820 | 31% | 42.6% | 6.8% |
| 1007 | Group chat | 10,106 | 21% | 51.2% | 9.4% |
| 1005 | Top search bar | 8,240 | 17% | 36.0% | 4.1% |
| 1035 | Mini-program QR code | 6,310 | 13% | 44.8% | 5.6% |
| 1001 | Discover tab | 5,418 | 11% | 58.1% | 11.2% |
| 1089 | Official account article | 3,319 | 7% | 33.9% | 3.2% |
- Offline codes tracked separatelyEvery mini-program code carries a parameter: store, poster and parcel card each count on their own.
- Chat shares are the largest entrance1-to-1 plus group chat is 52% of visits, but group-chat arrivals retain 9 points lower.
- Search arrivals convert bestUsers from the search bar order at 9.4%, 1.6× the average.
From the entrance to the order, and where they leave
A mini-program is a set of pages, not one screen. The path chart starts at the entrance scene and shows the next page and the page people leave from. Campaign and product pages are separate, so you can see whether the campaign actually sends people into products.
- Start from a scene or any page
- Leaving is a step, so you see which page loses people
- The same path report exists for web and app
Page paths · from entrance scene
Last 30 daysHighlighted: share → product page → order, 62% of all orders. 42% of campaign-page arrivals leave without seeing a product.
- The campaign page leaks42% of users who land on the campaign page leave without reaching a product.
- The product page converts62% of orders pass through a product page; only 8% order straight from the campaign.
- Share after orderingThe share button on the order-success page brought back 640 opens — a coupon card would help.
Which entrance brings people who stay
The matrix groups users by first-open week; the right side compares D1 retention by entrance. Mini-program retention is naturally lower than an app's — the point is which entrance deserves more spend.
- Weekly cohorts, D1 / D7 / D30 in one row
- Retention by entrance, not just the total
- Low-retention entrances pair with subscription messages for win-back
New-user retention · by first-open week
| First open | New | D0 | D1 | D7 | D14 | D30 |
|---|---|---|---|---|---|---|
| Sep 1 | 1,840 | 100% | 38% | 31% | 27% | 22% |
| Sep 8 | 2,012 | 100% | 41% | 33% | 28% | |
| Sep 15 | 1,966 | 100% | 44% | 35% | ||
| Sep 22 | 2,130 | 100% | 46% |
D1 retention · by entrance
QR-code and search arrivals have clear intent and retain best; campaign-page arrivals retain 24% — most leave after the campaign.
- QR-code users are steadiestD1 retention 46% — worth more offline material.
- Win back with subscription messagesUsers inactive for 7 days become a segment and receive a subscription message.
- Merged into one personWhen a user moves from the mini-program to the app, retention does not restart from zero.
Three platforms, one report, original scene names
Each mini-program is a data source inside the same project. The overview adds them up; split by platform any time.
Scene values, forwarded cards, official-account article jumps and subscription-message sources.
- 60+ scene values named automatically
- Group and 1-to-1 shares separated
- Article-jump attribution
Alipay
Source channels, post-payment return, lifestyle-account and search entrances.
- Post-payment returns counted separately
- Lifestyle account and search entrances
- Same page names as WeChat
Douyin
Video anchors, live-room entrances, search and shares, and what happens afterwards.
- Video and live entrances separated
- Anchored product-page conversion
- Reconcile with store orders
The person in the mini-program is the same person on web and app
One project, several data sources. A user orders in the mini-program, buys again in the app, read an article on the website — identity resolution puts all of it on one profile, so funnels and retention follow the person, not the device.
- Anonymous visits before login merge once the account matches
- Event names and fields are shared across the three platforms
- Every report compares platforms side by side
WeChat mini-program
pages/order/confirm · from share
Website
example.com/blog/linen-care · Google
App
iOS · v4.2.1 · opened from push
Lena M.
One person · 3 platforms · 14 sessions
- Read /blog/linen-care on the websiteSep 3 · Google
- Opened the mini-program from a group share, orderedSep 9 · scene 1044
- Installed the app, repeat purchase from a pushSep 28 · push
- Forwarded a group-buy card in the mini-programSep 30 · brought 3 people
- Merged automaticallyWhen the same user id appears on another platform, profiles merge and history is kept.
- Cross-platform funnelsProduct view on web, order in the mini-program, repeat in the app — one funnel.
- Privacy under your controlIdentification must be enabled per site; contact details are stored encrypted. See privacy and security.
From "how many came" to "what they did"
Scenes and shares explain where traffic comes from. For funnels, paths and individual people, switch to Insights — same data.
Initialise once, three platforms share one event set
With uni-app, one integration covers WeChat, Alipay and Douyin; native mini-programs have their own SDKs. Page views, scene values and shares are collected automatically; orders and other business events go through track.
import TapCub from '@tapcub/uni-app'
// Initialise once in app.js
TapCub.init({ siteKey: 'SITE_KEY', autoTrack: true })
// Business event: order
TapCub.track('order_paid', { amount: 74 })const TapCub = require('./libs/tapcub-weapp')
// Initialise once in app.js
TapCub.init({ siteKey: 'SITE_KEY', autoTrack: true })
// Business event: order
TapCub.track('order_paid', { amount: 74 })import TapCub from './libs/tapcub-alipay'
// Initialise once in app.js
TapCub.init({ siteKey: 'SITE_KEY', autoTrack: true })
// Business event: order
TapCub.track('order_paid', { amount: 74 })const TapCub = require('./libs/tapcub-tt')
// Initialise once in app.js
TapCub.init({ siteKey: 'SITE_KEY', autoTrack: true })
// Business event: order
TapCub.track('order_paid', { amount: 74 })Questions about mini-program analytics
Still have a question?
Chat with the team behind TapCub — we usually reply within a few hours on business days.
Which mini-programs are supported?
WeChat, Alipay and Douyin, plus multi-platform mini-programs built with uni-app. Each is a data source in the same project; scene values and page names are kept as they are.
Do I have to maintain a scene-value mapping?
No. WeChat's 60-plus scene values, Alipay source channels and Douyin entrances are named out of the box; new scenes land in "Other" with a notice in the console.
What is share return traffic?
Shares sent from the mini-program, the opens they bring back, and the new users and orders that follow. Viral depth shows how many levels a share travels. A share nobody opens still counts as a share.
Are page paths limited to the entrance scene?
No. Paths start from an entrance scene or any page and continue through product, campaign and order pages, marking where people leave.
Will one person be counted twice across web and mini-program?
When identity can be resolved they merge into one person, and earlier anonymous visits stay on that profile. See user profiles.
Is it a separate subscription?
No. Mini-program and app reports start on Pro ($9/month); web analytics is on every plan. See pricing.
Will reporting be blocked by platform review?
Add the reporting domain to each platform's request whitelist. The SDK does not collect phone numbers, openid or other sensitive fields unless you pass them explicitly; identification must be enabled per site.
Four steps to connect a mini-program
Same account and project as your website and app.
-
1
Create a project
Free account, no credit card. Add to an existing project if you have one.
-
2
Add the mini-program
Pick the platform, get the site key and whitelist the reporting domain.
-
3
Add the SDK
Initialise in app.js as shown above; add business events as needed.
-
4
Publish a version
Once approved, scene opens appear in reports within minutes.
Read the install guide, or explore the console with demo data first. Install guide