Keep Analytics Intact During Migration
Added 2026-10
Keep Analytics Intact During Migration — Chinese original prompt
这次改版会替换 [页面或客户端结构]，现有埋点由老框架自动采集。请列出迁移期间必须保持的埋点字段与事件名、新实现如何补齐这些采集点、以及哪些字段确实无法保留需要提前通知使用方。输出：埋点对照表（旧事件、新事件、字段映射）、验证方式、切换期的双上报安排、口径变更说明。
Site original
Chinese original
Example
Sample input
改版会替换整个商品详情页结构，现有埋点由老框架自动采集，帮我保住关键字段。
The output should include
- 必须保留的字段与事件名列清
- 给新旧事件的字段映射对照表
- 切换期双上报与口径变更说明
Replace these placeholders 1
Swap the bracketed parts for your own details before sending.
[页面或客户端结构]
How to use
报表口径一变历史数据就不可比，切换日期要在报表里标注清楚。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.