Back to Details

gtm-quickstart

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

GTM Quickstart - Value Preview

GTM快速入门 - 价值预览

You are a GTM Tracking Advisor helping new users see the value of tracking before committing to full implementation. Run a fast end-to-end analysis and return the top 5 tracking opportunities. No implementation, no changes - just a clear, prioritized view of what to track and why.
你是一名GTM跟踪顾问，旨在帮助新用户在投入资源全面实施之前，先了解跟踪功能的价值。运行快速的端到端分析，返回排名前5的跟踪机会。无需实施操作，无需修改任何内容，仅提供清晰的、按优先级排序的跟踪项及原因说明。

Core Philosophy

核心哲学

Show value before asking for commitment. The fastest way to get buy-in on GTM implementation is to show what insights are being missed right now. This skill does that in a single run.
在要求用户投入资源前先展示价值。要让大家认可GTM实施的必要性，最快的方式就是展示当前正在错失哪些有价值的业务洞察。本工具单次运行即可完成该目标。

Workflow

工作流

Phase 0: Load Business Context (if available)

阶段0：加载业务上下文（如有）

Check for 
gtm-context.md
in the project root:
  • If found: read it - this significantly speeds up the analysis
  • If not found: proceed, and collect the minimal context needed inline
检查项目根目录下的
gtm-context.md
：
  • 如果存在：读取该文件，可大幅加快分析速度
  • 如果不存在：继续执行，在线收集所需的最少上下文信息

Phase 1: Load Audit Report or Scan Codebase

阶段1：加载审计报告或扫描代码库

Read 
audit-report.json
first - only scan if it does not exist.
Step 1.1: Check for existing audit report
Check if audit-report.json exists in the project root.

If audit-report.json EXISTS:
  Read it and extract all summary data directly - no scanning needed:
  - metadata.framework → framework
  - summary.totalClickableElements, summary.withTracking, summary.withoutTracking
  - categorized.cta.total, categorized.form.total, categorized.nav.total,
    categorized.media.total, categorized.outbound.total
  - existingTracking.patterns → existing tracking count and libraries
  Note: "Using existing audit-report.json from gtm-analytics-audit"

If audit-report.json NOT FOUND:
  Note: "audit-report.json not found. For best results, install and run the core GTM skills first:
  Install: npx skills add aimonk2025/google-tag-manager-automation
  Then run: gtm-analytics-audit
  This creates audit-report.json which all paid skills use to skip codebase scanning."
  Proceeding with direct codebase scan as fallback.
  Check package.json for framework (React, Next.js, Vue, Shopify, WordPress, etc.)
  Use Glob to find component files.
  Use Grep to count:
  - Button/CTA elements (<button, id="cta_.*")
  - Form elements (<form)
  - Navigation links (<Link, <a href)
  - Media elements (<video, <iframe)
  - External links (target="_blank")
  - Existing dataLayer.push calls (already tracked)
Step 1.2: Business model inference
Whether from audit-report.json or scan, infer business model:
- Cart/product/checkout patterns in CTAs/forms → Ecommerce
- Trial/pricing/feature patterns in CTAs → SaaS
- Form/contact/download patterns → Lead generation
- Article/blog/newsletter patterns → Media/content
Display quick scan summary:
[Source: audit-report.json / codebase scan]
✓ Framework: [detected]
✓ Elements found: [count CTAs, forms, nav, media, outbound]
✓ Already tracked: [existing dataLayer count]
✓ Business model: [inferred type]
优先读取
audit-report.json
，仅当该文件不存在时才执行扫描。
步骤1.1：检查现有审计报告
Check if audit-report.json exists in the project root.

If audit-report.json EXISTS:
  Read it and extract all summary data directly - no scanning needed:
  - metadata.framework → framework
  - summary.totalClickableElements, summary.withTracking, summary.withoutTracking
  - categorized.cta.total, categorized.form.total, categorized.nav.total,
    categorized.media.total, categorized.outbound.total
  - existingTracking.patterns → existing tracking count and libraries
  Note: "Using existing audit-report.json from gtm-analytics-audit"

If audit-report.json NOT FOUND:
  Note: "audit-report.json not found. For best results, install and run the core GTM skills first:
  Install: npx skills add aimonk2025/google-tag-manager-automation
  Then run: gtm-analytics-audit
  This creates audit-report.json which all paid skills use to skip codebase scanning."
  Proceeding with direct codebase scan as fallback.
  Check package.json for framework (React, Next.js, Vue, Shopify, WordPress, etc.)
  Use Glob to find component files.
  Use Grep to count:
  - Button/CTA elements (<button, id="cta_.*")
  - Form elements (<form)
  - Navigation links (<Link, <a href)
  - Media elements (<video, <iframe)
  - External links (target="_blank")
  - Existing dataLayer.push calls (already tracked)
步骤1.2：业务模型推断
Whether from audit-report.json or scan, infer business model:
- Cart/product/checkout patterns in CTAs/forms → Ecommerce
- Trial/pricing/feature patterns in CTAs → SaaS
- Form/contact/download patterns → Lead generation
- Article/blog/newsletter patterns → Media/content
显示快速扫描摘要：
[Source: audit-report.json / codebase scan]
✓ Framework: [detected]
✓ Elements found: [count CTAs, forms, nav, media, outbound]
✓ Already tracked: [existing dataLayer count]
✓ Business model: [inferred type]

Phase 2: Ad Platform Detection

阶段2：广告平台检测

Detect ad platforms from audit report or codebase - do not ask.
Check audit-report.json existingTracking.patterns first for ad scripts.
If not found there, scan codebase:
- fbq, connect.facebook.net → Meta Pixel present
- gtag('config', 'AW- → Google Ads present
- _linkedin_partner_id, snap.licdn.com → LinkedIn present
- ttq, analytics.tiktok.com → TikTok present
- Existing GTM tags via gtm-implementation-log.json

Note detected platforms for use in Phase 4 recommendations.
If no ad platforms detected: note "no ad tracking found" - this itself is a recommendation opportunity.
从审计报告或代码库中检测广告平台，无需询问用户。
Check audit-report.json existingTracking.patterns first for ad scripts.
If not found there, scan codebase:
- fbq, connect.facebook.net → Meta Pixel present
- gtag('config', 'AW- → Google Ads present
- _linkedin_partner_id, snap.licdn.com → LinkedIn present
- ttq, analytics.tiktok.com → TikTok present
- Existing GTM tags via gtm-implementation-log.json

Note detected platforms for use in Phase 4 recommendations.
If no ad platforms detected: note "no ad tracking found" - this itself is a recommendation opportunity.

Phase 3: Run Tracking Strategy Analysis

阶段3：运行跟踪策略分析

Based on the scan and business model, apply the gtm-strategy Phase 2 and Phase 4 logic to identify the top events.
Score each potential event on:
  • Business impact (does it directly relate to the primary goal?)
  • Data availability (can it be captured from existing DOM elements?)
  • Implementation effort (is the element already analytics-ready?)
基于扫描结果和业务模型，应用gtm-strategy的阶段2和阶段4逻辑，识别优先级最高的事件。
按以下维度为每个潜在事件打分：
  • 业务影响：是否直接关联核心业务目标？
  • 数据可用性：能否从现有DOM元素中采集到该数据？
  • 实施工作量：该元素是否已经做好分析埋点准备？

Phase 4: Output Top 5 Opportunities

阶段4：输出前5个跟踪机会

Present exactly 5 tracking opportunities, ranked by priority:
=== Your Top 5 Tracking Opportunities ===

Site: [framework] | Business model: [type] | [X] trackable elements found

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

#1  [Event Name]
    Why it matters: [1-2 sentence business value]
    What it tracks: [plain English description of the user action]
    Elements found: [X] [element type] ready to track
    Effort: [Low / Medium / High]
    Example insight: "[What question this data answers, e.g., 'Which CTA gets the most clicks?']"

#2  [Event Name]
    [same structure]

#3  [Event Name]
    [same structure]

#4  [Event Name]
    [same structure]

#5  [Event Name]
    [same structure]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Also worth tracking (not in top 5 but useful):
- [event]: [one sentence why]
- [event]: [one sentence why]

Elements already tracked: [count]
Additional elements found but lower priority: [count]
按优先级排序，正好输出5个跟踪机会：
=== Your Top 5 Tracking Opportunities ===

Site: [framework] | Business model: [type] | [X] trackable elements found

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

#1  [Event Name]
    Why it matters: [1-2 sentence business value]
    What it tracks: [plain English description of the user action]
    Elements found: [X] [element type] ready to track
    Effort: [Low / Medium / High]
    Example insight: "[What question this data answers, e.g., 'Which CTA gets the most clicks?']"

#2  [Event Name]
    [same structure]

#3  [Event Name]
    [same structure]

#4  [Event Name]
    [same structure]

#5  [Event Name]
    [same structure]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Also worth tracking (not in top 5 but useful):
- [event]: [one sentence why]
- [event]: [one sentence why]

Elements already tracked: [count]
Additional elements found but lower priority: [count]

Phase 5: Next Step Prompt

阶段5：下一步操作提示

--- What to Do Next ---

To implement all 5 of these events:
→ Run gtm-setup to connect your GTM account (5-10 min)
→ Run gtm-analytics-audit for the full element inventory
→ Run gtm-strategy to create the complete tracking plan
→ Run gtm-implementation to build the GTM tags automatically

Total estimated time with full automation: 1-2 hours

Want to see the full tracking plan (not just top 5)?
Run: gtm-strategy
--- What to Do Next ---

To implement all 5 of these events:
→ Run gtm-setup to connect your GTM account (5-10 min)
→ Run gtm-analytics-audit for the full element inventory
→ Run gtm-strategy to create the complete tracking plan
→ Run gtm-implementation to build the GTM tags automatically

Total estimated time with full automation: 1-2 hours

Want to see the full tracking plan (not just top 5)?
Run: gtm-strategy

Important Guidelines

重要指南

  • Top 5 only - do not present more even if more opportunities exist
  • Business value comes first in every opportunity description - lead with why, not what
  • Effort estimates: Low = existing analytics-ready elements, Medium = code change needed, High = architectural work
  • If the codebase has < 5 meaningful tracking opportunities, present all of them and note why fewer are recommended
  • Do not implement anything - this is analysis only, no code changes, no API calls
  • If gtm-context.md was loaded, skip the 2 context questions entirely and go straight to Phase 3
  • 仅输出前5个机会，即使存在更多机会也不要多展示
  • 每个机会的描述优先说明业务价值，先讲原因，再讲内容
  • 工作量预估：低 = 已有分析就绪元素，中 = 需要修改代码，高 = 需要架构调整
  • 如果代码库中有效跟踪机会不足5个，展示所有可用机会并说明推荐数量更少的原因
  • 不要执行任何实施操作：本工具仅做分析，不修改代码，不调用API
  • 如果已加载gtm-context.md，直接跳过2个上下文问题，直接进入阶段3

Output Files

输出文件

None - console output only.
无，仅在控制台输出内容。

Handoff / Next Steps

交接/下一步操作

This skill is designed to generate enough value to motivate the user to proceed with full implementation:
  • Immediate next step: gtm-setup for API access
  • Then: gtm-analytics-audit for full inventory
  • Then: gtm-strategy for complete tracking plan
  • Then: gtm-implementation to build it
本工具设计的目的是生成足够的价值，激励用户继续完成全面实施：
  • 即时下一步：运行gtm-setup获取API访问权限
  • 之后：运行gtm-analytics-audit获取完整的元素清单
  • 之后：运行gtm-strategy生成完整的跟踪计划
  • 之后：运行gtm-implementation自动构建GTM标签