管理后台 - WeChat Viral 活动裂变系统

加载中...

📊 进行中活动

👥 参与人数

🤝 助力人数

- 有效

🎁 已领取奖励

📈 人均助力

📋 进行中的活动

活动名称	参与人数	助力人数	已领奖励	状态
加载中...

🕐 最近动态 (最近24小时)

加载中...

加载活动列表...

🏆 影响力排行榜

哪些用户带来最多粉丝，拥有最高的裂变潜力？

👥

- 活跃用户数

🌟

- 平均影响力

🔄

- 平均裂变系数

🏅

- 最佳表现者

排名	用户	得分	助力数	二代数	裂变K值	留存率	奖励数	趋势
加载中...

📈 活动对比分析

对比不同活动的效果表现

活动 A:

活动 B:

选择两个活动进行对比

全部活动概览

活动	状态	健康	参与	助力	转化	留存	奖品
加载中...

📚 Analytics Reference Guide

Documentation for all reports and metrics

🏆 Top Influencers Report ▼

Identifies users who bring the most followers and have the highest viral potential.

Metrics Explained:

Influence Score	Weighted score: `(helpers × 2) + (retention% × 1.5) + (secondary referrals × 3)`
Helpers	Number of users who followed via this user's referral
2nd Gen	Secondary referrals - helpers who also became participants and brought their own helpers
Viral K	Viral coefficient: `New users brought / Original users`. K > 1 means exponential growth
Retention	Percentage of helpers still following the OA
Trend	📈 Growing, ➡️ Stable, 📉 Declining (based on last 7 days)

Use Cases:

Identify power users for special rewards or partnerships
Understand what makes successful referrers
Target high-potential users for VIP campaigns

📈 Campaign Comparison Report ▼

Compare performance metrics across different campaigns to identify winning strategies.

Metrics Explained:

Health Score	0-100 score based on: activity level, retention, conversion rate, reward claims
Conversion Rate	`Participants / Total Helpers × 100` - How many helpers become participants
Funnel	Visual: Scans → Follows → Participants → Rewards Claimed

Use Cases:

A/B test different campaign designs
Identify best-performing reward structures
Optimize campaign timing and messaging

🎯 Traffic Sources Report ▼

Understand where your users come from and which channels perform best.

Source Types:

📷 QR Scan	Users who scanned a QR code from a poster or shared image
📝 Article Link	Users who clicked a link embedded in a WeChat article
📱 OA Menu	Users who clicked from the Official Account menu
🔗 Direct Link	Users who accessed via direct Mini Program link

Quality Metrics:

Conversion Rate by Source - Which sources bring users who participate
Retention by Source - Which sources bring loyal followers
Avg Helpers by Source - Which sources bring viral users

📅 Trends Report ▼

Track growth patterns and identify optimal times for engagement.

Charts & Visualizations:

Growth Chart	Daily helpers, participants, and unfollows over time
Activity Heatmap	Shows peak activity by day of week and hour
Growth Rate	Day-over-day and week-over-week percentage changes

Use Cases:

Identify best times to post content
Spot anomalies (sudden drops or spikes)
Plan campaign launches based on activity patterns

🔍 Campaign Debug Report ▼

Detailed debugging information for individual campaigns.

Sections:

Campaign Health	Overall status: Active, Recent Activity, Retention Health
Stats Grid	Participants, Valid Helpers, Unfollowed, Retention %, Rewards Claimed, Today's Activity
Debug Tools	复制场景值、下载二维码、查看原始数据
Leaderboard	Top 5 performers with medals, avatar, helper count, claimed tiers
Participants Table	User info, referral code, progress bar, reward status, join time
Helpers Table	Helper OpenID, who they helped, source channel, valid/invalid status
Events Log	Recent campaign events with type icons and descriptions

Scene String Format:

camp_{campaignId}_ref_{referralCode}

Used in QR codes to track which campaign and who referred the user.

🔄 数据流与架构 ▼

How data flows through the system when a user participates in a campaign.

┌─────────────────────────────────────────────────────────────────────┐
│                        VIRAL CAMPAIGN DATA FLOW                      │
├─────────────────────────────────────────────────────────────────────┤
│                                                                      │
│  1. USER SCANS QR CODE                                               │
│     └─→ Scene: camp_abc123_ref_XYZ789                                │
│                                                                      │
│  2. WECHAT OA WEBHOOK                                                │
│     ├─→ Event: subscribe/SCAN                                        │
│     ├─→ Parse scene → campaign_id + referral_code                    │
│     └─→ Log event to event_logs                                      │
│                                                                      │
│  3. BACKEND PROCESSING                                               │
│     ├─→ Find participant by referral_code                            │
│     ├─→ Create helper record in campaign_helpers                     │
│     ├─→ Update participant's helper_count                            │
│     └─→ Send auto-reply with Mini Program link                       │
│                                                                      │
│  4. USER OPENS MINI PROGRAM                                          │
│     ├─→ Landing page with campaign info                              │
│     ├─→ Registration if new user                                     │
│     └─→ Become participant → generate own referral_code              │
│                                                                      │
│  5. REWARD CLAIMING                                                  │
│     ├─→ Check valid helper_count vs reward threshold                 │
│     ├─→ Re-validate helpers (check unfollows)                        │
│     └─→ Create claim record in campaign_reward_claims                │
│                                                                      │
│  6. UNFOLLOW HANDLING                                                │
│     ├─→ Webhook: unsubscribe event                                   │
│     ├─→ Mark helper as is_valid = false                              │
│     └─→ Recalculate on next reward claim attempt                     │
│                                                                      │
└─────────────────────────────────────────────────────────────────────┘

Key Database Tables:

campaigns	Campaign configuration (name, dates, rules, status)
campaign_rewards	Reward tiers (helpers_required, name, content)
campaign_participants	Users participating (referral_code, helper_count)
campaign_helpers	Helper records (helper_openid, is_valid, source)
campaign_reward_claims	Claimed rewards (participant, reward, timestamp)
event_logs	All system events for debugging

快速选择:

请选择一个活动查看调试数据

🔄 How Campaign Fission Works (Step-by-Step) ▼

User A Joins Campaign

User registers and becomes a participant. System generates a unique referral_code (e.g., CMSFJE).

Database: campaign_participants → new row with user_id, campaign_id, referral_code

Generate QR Code with Scene

User generates a poster with QR code. The QR embeds a scene string:

Format: camp_{campaignId}_ref_{referralCode}
Example: camp_a570fa29_ref_CMSFJE

User B Scans QR Code

User B scans the QR code with WeChat. WeChat sends a webhook to your server:

Event: subscribe (new follower) or SCAN (existing follower)
Contains: EventKey with scene string

Backend Processes Webhook

Server parses scene string, finds User A by referral_code, records helper:

Actions:
• campaign_helpers → new row linking User B to User A
• campaign_participants → increment User A's helper_count

Auto-Reply Sent

Server sends auto-reply message to User B with Mini Program link.

Link: pages/campaign/index?id={campaignId}&ref={referralCode}

User A Claims Reward

When User A reaches required helpers, they can claim rewards:

Validation: System re-validates is_valid helpers before allowing claim
Database: campaign_reward_claims → new row

📊 Visual Flow

┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐
│  User A  │───▶│ Generate │───▶│  User B  │───▶│ Webhook  │───▶│  Helper  │
│  Joins   │    │    QR    │    │  Scans   │    │ Received │    │ Recorded │
└──────────┘    └──────────┘    └──────────┘    └──────────┘    └──────────┘
                                                                      │
                                                                      ▼
┌──────────┐    ┌──────────┐    ┌──────────┐                   ┌──────────┐
│  Reward  │◀───│  Claim   │◀───│ Threshold│◀──────────────────│  Count   │
│ Delivered│    │  Reward  │    │   Met    │                   │ Updated  │
└──────────┘    └──────────┘    └──────────┘                   └──────────┘

📊 Key Metrics Explained ▼

Metric	Description	Calculation
Participants	Users who joined this campaign and have a referral code	`COUNT(*) FROM campaign_participants WHERE campaign_id = ?`
Valid Helpers	Users who scanned QR and are still following OA	`COUNT(*) WHERE is_valid = true`
Unfollowed	Helpers who unfollowed OA after scanning	`COUNT(*) WHERE is_valid = false`
Retention	Percentage of helpers still following	`Valid Helpers / Total Helpers × 100%`
Rewards Claimed	Total reward tiers claimed by all participants	`COUNT(*) FROM campaign_reward_claims`
Today	New helpers recorded in the last 24 hours	`COUNT(*) WHERE created_at > NOW() - 24h`
Progress	Current helpers vs. next reward tier	`helper_count / next_tier_threshold × 100%`

📡 Webhook Event Types ▼

Event Type	Trigger	Action Taken
`oa_subscribe`	User followed OA for the first time	Record helper if scene contains campaign info
`oa_scan`	Existing follower scanned QR	Record helper if not already recorded
`oa_unsubscribe`	User unfollowed OA	Mark helper as `is_valid = false`
`campaign_helper_recorded`	New helper successfully recorded	Increment participant's helper_count
`campaign_qr_created`	QR code generated for participant	Log for debugging
`campaign_reward_claimed`	Participant claimed a reward tier	Create claim record, update inventory

🗄️ Database Schema Reference ▼

campaigns

Campaign configuration

id, name, description, status, start_time, end_time, rules

campaign_rewards

Reward tiers for each campaign

id, campaign_id, tier_level, helpers_required, reward_name, reward_content

campaign_participants

Users participating in campaigns

id, campaign_id, user_id, referral_code, helper_count, joined_at

campaign_helpers

Who helped whom

id, campaign_id, participant_id, helper_openid, is_valid, source_channel

campaign_reward_claims

Claimed rewards

id, campaign_id, participant_id, reward_id, claimed_at

event_logs

All system events for debugging

id, event_type, user_id, event_data, ip_address, created_at

🔌 API Endpoints Reference ▼

Endpoint	Method	Description
`/api/campaigns/:id`	GET	Get campaign details and rewards
`/api/campaigns/:id/join`	POST	Join campaign, get referral code
`/api/campaigns/:id/qrcode`	GET	Generate QR code for participant
`/api/campaigns/:id/poster`	GET	Generate poster with QR code
`/api/campaigns/:id/claim/:rewardId`	POST	Claim a reward tier
`/api/campaigns/:id/debug`	GET	Get debug data (admin only)
`/api/oa/webhook`	POST	WeChat OA event webhook

⚡ Quick Debug Actions ▼

选择活动:

📑

请选择活动

从上方下拉菜单选择活动，生成完整的运营报表。

连接中...

0 事件总数

0 本次会话

- 最后事件

0 事件/分钟

显示测试事件

正在连接事件流...

🔄 实时日志工作原理 ▼

Technology: Server-Sent Events (SSE)

Live Logs uses Server-Sent Events (SSE) to push real-time events from the backend to your browser. Unlike polling (which repeatedly asks "any new events?"), SSE maintains a persistent connection and the server pushes events as they happen.

┌─────────────────┐     SSE Connection      ┌─────────────────┐
│  Admin Browser  │ ◄────────────────────── │  Backend Server │
│  (EventSource)  │     Real-time events    │  (SSE Manager)  │
└─────────────────┘                         └─────────────────┘
                                                    ▲
                                                    │
                                            broadcastEvent()
                                                    │
                            ┌───────────────────────┼───────────────────────┐
                            │                       │                       │
                     WeChat Webhook          User Actions           Campaign Events
                     (subscribe/scan)        (login/register)       (helper recorded)

Key Features:

Instant delivery - Events appear within milliseconds of occurring
No refresh needed - The page updates automatically
Buffer system - Last 100 events are kept in memory
Auto-reconnect - If connection drops, it reconnects automatically

📋 When to Use Live Logs ▼

✅ Good Use Cases

Testing webhooks - Watch events arrive as you scan QR codes
Debugging in real-time - See exactly what's happening right now
Demos - Show stakeholders the system working live
Monitoring launches - Watch a new campaign's first interactions
Verifying setup - Confirm webhook is receiving events

❌ Use Event History Instead

Searching past events - Live Logs has no search
Investigating issues - Event History has filters and details
Generating reports - Use Analytics or Event History
Reviewing specific users - Event History can filter by user

📡 Event Types You'll See ▼

Event	Icon	Trigger	Data Included
`oa_subscribe`	🔔	User follows Official Account	OpenID, scene string, timestamp
`oa_scan`	📷	Existing follower scans QR	OpenID, scene string, event key
`oa_unsubscribe`	🔕	User unfollows Official Account	OpenID, timestamp
`campaign_helper_recorded`	👥	New helper recorded for campaign	Helper ID, participant ID, campaign ID
`campaign_qr_created`	🎫	QR code generated	Campaign ID, user ID, scene string
`login`	🔑	User logs in	User ID, method, IP address
`register`	📋	New user registers	User ID, referral code, source

🎮 Controls Guide ▼

⏸️

Pause/Resume

Temporarily stop updating the display. Events are still received but not shown until you resume. Useful when you want to examine a specific event.

🗑️

Clear

Remove all events from the display. The connection stays active and new events will appear. Useful to start fresh when testing.

🔄

Reconnect

Close and re-establish the SSE connection. Use this if you see "Disconnected" status or events stop appearing.

🔴

Connection Status

Shows whether you're connected to the event stream. Green = connected, Red = disconnected, Yellow = connecting.

🔧 Troubleshooting ▼

❌ "Connecting..." never changes

Check if backend server is running
Check browser console for errors
Try clicking "Reconnect"
Refresh the page

❌ Events not appearing

Check connection status is "Connected"
Make sure "Pause" is not active
Check filter settings
Verify webhook is configured correctly

❌ Connection keeps dropping

Check network stability
Backend server may be restarting
Cloudflare Tunnel may be unstable
Browser may be throttling background tabs

❌ Missing some events

Events only show while connected
Check Event History for complete record
Buffer only keeps last 100 events

⚡ Quick Actions ▼

加载事件中...

🌐 Cloudflare 隧道 ⏳ 检测中...

隧道地址:

Webhook 地址: -

状态: -

📱 WeChat Official Account ⏳ Checking...

OA AppID: -

Access Token: -

Last Webhook: -

🗄️ Database (Supabase) ⏳ Checking...

Connection: -

Tables: -

⚙️ Backend Server ⏳ Checking...

Local URL: http://localhost:3000

API Status: -

系统总体状态

点击刷新检测

📋 系统检查清单

所有组件都必须正确配置才能使系统正常工作。

🗄️ 数据库 (Supabase)

⏳ SUPABASE_URL 已配置

⏳ SUPABASE_SERVICE_KEY 已配置

⏳ 数据库表已创建

⏳ 数据库连接成功

📱 微信小程序

⏳ WECHAT_APPID 已配置

⏳ WECHAT_SECRET 已配置

⏳ 服务器域名已添加（仅生产环境）

🖥️ 本地开发: 在微信开发者工具 → 详情 → 本地设置中勾选"不校验合法域名"

🌐 生产环境: 在微信公众平台 → 开发 → 开发设置中添加服务器域名

📡 微信公众号

⏳ OA_APPID 已配置

⏳ OA_SECRET 已配置

⏳ OA_TOKEN 已配置

⏳ OA_ENCODING_AES_KEY 已配置

⏳ Webhook URL configured and verified

🚇 Cloudflare Tunnel (Development Only)

⏳ Tunnel URL configured Only needed for local development. Production uses direct domain.

⏳ Tunnel is active

⏳ Tunnel accessible from internet

💻 Backend Server

⏳ Server running on port 3000

⏳ All environment variables loaded

⏳ API routes accessible

📲 小程序开发配置指南

本指南解释了小程序开发中 localhost 与真机测试的核心问题，以及我们的解决方案。

🔴 核心问题

为什么小程序真机无法直接访问 localhost？

localhost 是本地回环地址 — 指向设备自身，不是你的电脑
手机和电脑是不同设备 — 手机的 localhost 是手机本身，无法到达你电脑的服务
微信小程序限制 — 正式环境必须使用 HTTPS 且域名需备案

✅ 我们的解决方案

🌐

Cloudflare Tunnel + Supabase 自动同步

我们使用 Cloudflare Tunnel 将本地服务暴露到公网，并将 Tunnel URL 存储在 Supabase。小程序启动时自动从 Supabase 获取最新 URL，无需每次手动修改代码。

工作流程：

┌──────────────┐    ┌─────────────────┐    ┌──────────────┐
│   你的电脑    │───▶│ Cloudflare Tunnel│───▶│   公网 URL   │
│ localhost:3000│    │                 │    │ xxx.trycloudflare.com │
└──────────────┘    └─────────────────┘    └──────────────┘
                                                   │
                           ┌───────────────────────┘
                           ▼
            ┌──────────────────────────┐
            │       Supabase          │◀─── Admin 后台保存 URL
            │   tunnel_config 表      │
            └──────────────────────────┘
                           │
                           ▼
            ┌──────────────────────────┐
            │      小程序 (真机)        │◀─── 启动时自动获取 URL
            │  自动使用最新 Tunnel URL  │
            └──────────────────────────┘

🔄 自动环境检测

小程序会自动检测运行环境，选择正确的 API 地址。

🖥️ 模拟器环境

platform = devtools
使用 http://localhost:3000/api
无需额外配置

📱 真机环境

platform = ios 或 android
从 Supabase 获取 Tunnel URL
URL 缓存 5 分钟

⚙️ 必要配置

以下配置只需完成一次。

微信公众平台 - 添加 Supabase 域名

进入「开发 → 开发管理 → 开发设置 → 服务器域名」
在 request合法域名 添加：https://fseyfnuqxvrcwrpshxyv.supabase.co

开发者工具 - 开启不校验合法域名（开发时）

在微信开发者工具右上角「详情 → 本地设置」
勾选 ☑️ 不校验合法域名、web-view（业务域名）、TLS 版本以及 HTTPS 证书

真机调试 - 开启调试模式

扫码预览时，点击右上角「...」→「开启调试」
这样真机也可以访问非 HTTPS 域名（开发阶段）

📋 日常开发流程

启动后端服务 — cd backend && npm run dev
启动 Cloudflare Tunnel — cloudflared tunnel --url http://localhost:3000
复制 Tunnel URL — 从终端输出中复制 https://xxx.trycloudflare.com
在 Admin 后台保存 URL — 「基础设施 → 隧道配置」粘贴并保存
真机预览 — 小程序会自动获取最新 URL，无需改代码

🔧 常见问题排查

真机提示「request:fail url not in domain list」

原因：Supabase 域名未添加到合法域名列表

解决：在微信公众平台添加 https://fseyfnuqxvrcwrpshxyv.supabase.co 到 request 合法域名

真机请求超时或无响应

可能原因：

Cloudflare Tunnel 已断开（每次重启电脑后需要重新启动）
Admin 后台的 Tunnel URL 未更新
后端服务未启动

解决：重新启动 tunnel 并更新 URL

模拟器正常但真机报错

原因：模拟器使用 localhost，真机需要公网 URL

解决：确保 Tunnel 正在运行且 URL 已保存到 Admin 后台

小程序无法获取 Tunnel URL

检查步骤：

确认 Supabase 域名已添加到 request 合法域名
检查 tunnel_config 表中是否有记录
清除小程序本地存储后重试

🚀 生产环境注意事项

上线生产环境前，需要完成以下配置：

域名备案 — 国内服务器需要 ICP 备案
HTTPS 证书 — 所有 API 必须使用 HTTPS
正式域名 — 替换 Cloudflare Tunnel 为正式域名
添加合法域名 — 在微信公众平台添加正式 API 域名
关闭调试开关 — 小程序代码中移除开发时的调试代码

Connection Status

Checking...

📦

LOCAL SERVER

Checking...

⚡

PROCESS PID

Checking...

🌐

LATENCY

Checking...

🔗 Current Tunnel URL

Not configured

📡 WeChat Webhook URL

Not configured

更新 Tunnel URL

从 cloudflared 命令输出中复制 URL，粘贴到下方保存。

🌐

📱

小程序自动同步

保存后，小程序真机调试会自动获取最新的 Tunnel URL，无需手动修改代码。
首次使用需在小程序「request合法域名」添加：fseyfnuqxvrcwrpshxyv.supabase.co

Quick Reference Commands

▼

🔗 Why Do You Need a Tunnel?

▼

Connection Status

Checking...

📱

OA APPID

Checking...

🔑

ACCESS TOKEN

Checking...

📡

LAST WEBHOOK

Checking...

🆔 OA AppID

Not configured

🔐 OA Secret

Not configured

📡 Webhook URL

Not configured

🔗 Update Webhook URL in WeChat Console

Go to WeChat MP Admin to configure the webhook URL and message settings

Open WeChat Console ↗

📱 Why Do You Need WeChat Official Account?

▼

Quick Reference

▼

Connection Status

Checking...

🗄️

CONNECTION

Checking...

📊

TABLES

Checking...

⚡

LATENCY

Checking...

🔗 Supabase URL

Not configured

🔑 Supabase Key

Not configured

🗄️ Why Do You Need Database?

▼

Quick Reference

▼

Connection Status

Checking...

💻

LOCAL SERVER

Checking...

❤️

API HEALTH

Checking...

⏱️

RESPONSE TIME

Checking...

🔗 Local URL

http://localhost:3000

🌍 Environment

development

🔧 Node Version

-

💻 Why Do You Need Backend Server?

▼

Quick Reference

▼

🔄 完整数据流

了解数据如何在裂变营销系统中流转

1 扫码关注流程

👤

用户B扫描二维码

二维码包含: camp_{campaignId}_ref_{userA_code}

↓

➕

用户B关注公众号

微信触发 "subscribe" 事件

↓

📡

Webhook 事件

微信 → Cloudflare 隧道 → 后端

POST /api/oa/webhook

↓

💾

记录助力

保存到 campaign_helpers 表:

helper_openid (用户B)
participant_id (用户A)
campaign_id
is_valid = true
source_channel = 'wechat_scan'

↓

📊

更新进度

用户A的 helper_count++

检查是否解锁奖励

↓

💬

自动回复用户B

发送小程序链接:

pages/landing/index?ref={code}&from=oa

2 新用户注册

📱

用户B打开小程序

带邀请码的落地页

↓

🔐

wx.login()

获取微信code → 换取session

POST /api/auth/login

↓

✍️

填写注册表单

姓名、电话、公司等

↓

💾

创建用户记录

保存到 users 表

关联邀请码到用户A

↓

📝

记录事件

保存到 event_logs:

event_type: 'register'
user_id: 用户B
referrer_id: 用户A
source: 'oa_scan'

3 用户B成为分享者

🎯

用户B参与活动

成为参与者

↓

🎫

生成用户B的二维码 POST /api/oa/scene

scene: camp_{id}_ref_{userB_code}

↓

🖼️

生成海报

用户B的头像 + 昵称 + 二维码

POST /api/campaigns/{id}/poster

↓

📤

用户B分享海报

朋友圈、群聊、好友

↓

🔁

循环继续

用户C扫码 → 助力用户B → 成为分享者

裂变增长！🚀

4 进度追踪与奖励

📊

实时进度更新

小程序显示助力人数

查询 campaign_participants

↓

🎁

解锁奖励

helper_count ≥ required_helpers

按钮："领取奖励"

↓

✅

领取奖励 POST /api/campaigns/{id}/claim/{rewardId}

验证助力数（重新计算有效助力）

↓

📝

数据库记录

保存到 campaign_reward_claims

记录事件: 'campaign_reward_claimed'

5 数据分析与追踪

📈

持续追踪

所有事件保存到 event_logs

用户行为（登录、注册、扫码）
公众号事件（关注、取关）
活动事件（助力、领奖）

↓

🎯

来源追踪

source_channel: wechat_scan, h5_share 等

referrer_id: 谁邀请的用户

campaign_id: 哪个活动

↓

👑

影响力排行榜

计算 influence_score

直接邀请 + 二级邀请

↓

📊

管理后台

实时指标、图表、调试日志

监控活动表现

🛡️ 防作弊与边界情况

🔄

Unfollow Handling (Balanced Approach):

When user unfollows: Set is_valid = false in campaign_helpers
Don't immediately update participant's helper_count
On reward claim: Re-calculate valid helpers only
If insufficient: Show "Some helpers unfollowed, need X more"
If re-follows: Restore is_valid = true

🚫

Duplicate Prevention:

Same user (by openid) can only help once per participant per campaign

Database unique constraint: (helper_openid, participant_id, campaign_id)

⏰

Time Limits:

Campaign has start_date and end_date

Helpers only count if within campaign period

🔍

Admin Monitoring:

Real-time event stream shows suspicious patterns

Filter by: rapid helps from same IP, bot-like behavior

加载设置中...

🛠️ 开发测试工具

快速重置数据，高效测试活动流程

小程序注册加载中...

🧪 测试账号

核心功能

保存测试微信账号，快速重置助力记录进行重复测试。

加载中...

💡 如何使用？

重置 - 清除助力记录，可重新扫码助力

完全重置 - 清除所有数据+公众号关联，测试完整新用户流程

🔄 活动数据重置

重置指定活动

仅清除选定活动的助力、参与、领奖记录

清除测试用户

删除所有非管理员用户，保留活动配置

-- 用户

⚙️ 高级选项 ▼

🗑️

重置所有活动数据

清除所有活动的助力、参与、领奖记录

🔧

手动重置 OpenID

☢️ 危险操作区谨慎使用

删除全部用户

删除所有用户，保留活动配置

☢️ 删除全部数据

删除所有数据：用户、活动、记录等

📊 操作结果

- 总用户数

- 📱 小程序用户

- 📢 公众号粉丝

- ✅ 已注册

- 👑 管理员

📱 有小程序 📢 有公众号 ✉️ 有邮箱 📞 有手机 👑 管理员

	用户	联系方式	微信标识	互动数据	来源	操作
加载中...

第 1 / 1 页显示 0 / 0 条

🤖 AI 客服配置

检查中...

配置 AI 客服与 n8n 的集成，自动回复公众号用户消息。

启用 AI 客服

启用后，用户发送消息会转发到 n8n 处理，AI 生成回复后自动发送给用户。

n8n Webhook URL

配置 n8n 工作流的 Webhook 接收地址。

超时设置

n8n 响应超时时间（毫秒）。微信要求 5 秒内响应，建议设置 4500ms。

毫秒 (推荐: 4500)

兜底消息

当 AI 无法回复或超时时，发送给用户的消息。

转人工提示

转接人工客服前发送给用户的消息。

转人工关键词（备用）

用户消息包含这些关键词时，直接转人工（作为 AI 判断的补充）。

多个关键词用逗号分隔

📖 n8n 集成指南（Callback 模式）

▼

🔄 数据流图（Callback 模式）

▼

🧪 一步步测试指南

▼

⏰ 48小时消息窗口说明

▼

📋 进行中的活动

🕐 最近动态 (最近24小时)

🏆 影响力排行榜

📈 活动对比分析

🎯 流量来源

📊 来源分布

📍 地域分布

📱 设备分布

🏆 最佳来源

📅 趋势与增长

🔥 活动热力图 (按日期和时间)

🎯 目标与里程碑

🏅 Milestones Achieved

📚 Analytics Reference Guide

🏆 Top Influencers Report ▼

Metrics Explained:

Use Cases:

📈 Campaign Comparison Report ▼

Metrics Explained:

Use Cases:

🎯 Traffic Sources Report ▼

Source Types:

Quality Metrics:

📅 Trends Report ▼

Charts & Visualizations:

Use Cases:

🔍 Campaign Debug Report ▼

Sections:

Scene String Format:

🔄 数据流与架构 ▼

Key Database Tables:

🔄 How Campaign Fission Works (Step-by-Step) ▼

User A Joins Campaign

Generate QR Code with Scene

User B Scans QR Code

Backend Processes Webhook

Auto-Reply Sent

User A Claims Reward

📊 Visual Flow

🔧 Debugging Guide - Common Issues ▼

Helper count not increasing

QR code not generating

Auto-reply not sending

User shows as "unfollowed"

Reward claim failing

Webhook not receiving events

📊 Key Metrics Explained ▼

📡 Webhook Event Types ▼

🗄️ Database Schema Reference ▼

campaigns

campaign_rewards

campaign_participants

campaign_helpers

campaign_reward_claims

event_logs

✅ Testing Checklist ▼

🚀 Before Launch

🧪 Test Flow

⚠️ Edge Cases

🔌 API Endpoints Reference ▼

⚡ Quick Debug Actions ▼

请选择活动

🔄 实时日志工作原理 ▼

Technology: Server-Sent Events (SSE)

Key Features:

📋 When to Use Live Logs ▼

✅ Good Use Cases

❌ Use Event History Instead

📡 Event Types You'll See ▼

🎮 Controls Guide ▼

🔧 Troubleshooting ▼

❌ "Connecting..." never changes

❌ Events not appearing

❌ Connection keeps dropping

❌ Missing some events

⚡ Quick Actions ▼

系统总体状态

📋 系统检查清单

📲 小程序开发配置指南

🔴 核心问题