Channel Landing | Gastx Content Admin

Primary fields

Channel, locale, campaign

文案、CTA、追踪预设、可见语种和渠道备注都需要明确归属。

Growth angle

Paid acquisition

落地页必须保持渠道归属清晰，避免增长页野蛮扩张成第二个站。

Launch Path

渠道页上线前必须走完的路径

先在 Locale Content 确认语种和受众，再创建渠道落地页。
再在 Site Settings 读取默认 CTA、联系入口和 tracking/pixel 开关。
上线前必须在 SEO Pages 记录 noindex、canonical 和 Paid/Organic 冲突说明。

Live landing entries

5 channel landing records are now served from a local JSON file.

Last updated: 2026-05-04T15:05:00.000Z

Lower the transfer burn, keep the route predictable.

Built for users who want a cheaper and clearer way to handle repeated TRON transfers without manually guessing each transaction cost.

en · google · published

更适合聊天式下单和后续提醒的能量入口。

适合希望通过 TG 完成购买、接收提醒、减少重复沟通的中文用户和运营团队。

zh-CN · telegram · published

Partner workflows for affiliate traffic, API routing, and repeat demand.

A landing structure for partner acquisition where route clarity, support, and future agent workflows matter more than a generic brochure page.

en · affiliate · published

高级源文件维护

Source payload

{
  "version": 1,
  "collection": "landing",
  "updatedAt": "2026-05-04T15:05:00.000Z",
  "records": [
    {
      "id": "landing-google-low-cost",
      "channel": "google",
      "campaignSlug": "low-cost-transfer",
      "locale": "en",
      "audienceAngle": "low-cost-transfer",
      "heroTitle": "Lower the transfer burn, keep the route predictable.",
      "heroSummary": "Built for users who want a cheaper and clearer way to handle repeated TRON transfers without manually guessing each transaction cost.",
      "primaryCta": "to-pricing",
      "backupCta": "to-help",
      "trackingPreset": "click_buy",
      "allowedParams": [
        "utm_source",
        "utm_medium",
        "utm_campaign",
        "utm_content",
        "utm_term",
        "gclid"
      ],
      "indexationMode": "noindex-follow",
      "proofPoints": [
        "Clear route for first-time buyers",
        "Fast path to pricing and purchase intent",
        "Support content available before checkout"
      ],
      "featuredFaqSlugs": [
        "energy-vs-burn",
        "route-selection"
      ],
      "status": "published",
      "updatedAt": "2026-05-04T13:20:00.000Z"
    },
    {
      "id": "landing-telegram-chat-ordering",
      "channel": "telegram",
      "campaignSlug": "chat-ordering",
      "locale": "zh-CN",
      "audienceAngle": "chat-driven-ordering",
      "heroTitle": "更适合聊天式下单和后续提醒的能量入口。",
      "heroSummary": "适合希望通过 TG 完成购买、接收提醒、减少重复沟通的中文用户和运营团队。",
      "primaryCta": "to-tg-bot",
      "backupCta": "to-help",
      "trackingPreset": "click_tg_bot",
      "allowedParams": [
        "utm_source",
        "utm_medium",
        "utm_campaign",
        "ref"
      ],
      "indexationMode": "noindex-follow",
      "proofPoints": [
        "聊天路径更适合高频复购",
        "减少人工重复解释",
        "适合中文运营和提醒通知"
      ],
      "featuredFaqSlugs": [
        "transfer-fail-after-rental"
      ],
      "status": "published",
      "updatedAt": "2026-05-04T13:20:00.000Z"
    },
    {
      "id": "landing-affiliate-partner-scale",
      "channel": "affiliate",
      "campaignSlug": "partner-scale",
      "locale": "en",
      "audienceAngle": "partner-scale",
      "heroTitle": "Partner workflows for affiliate traffic, API routing, and repeat demand.",
      "heroSummary": "A landing structure for partner acquisition where route clarity, support, and future agent workflows matter more than a generic brochure page.",
      "primaryCta": "to-partners",
      "backupCta": "to-api",
      "trackingPreset": "click_partner_apply",
      "allowedParams": [
        "utm_source",
        "utm_medium",
        "utm_campaign",
        "aff_id",
        "ref"
      ],
      "indexationMode": "noindex-follow",
      "proofPoints": [
        "Partner-focused routing and support expectations",
        "API path available for operational scale",
        "Built to grow into agent and reseller systems later"
      ],
      "featuredFaqSlugs": [
        "route-selection"
      ],
      "status": "published",
      "updatedAt": "2026-05-04T13:20:00.000Z"
    },
    {
      "id": "landing-google-low-cost-zh",
      "channel": "google",
      "campaignSlug": "low-cost-transfer-zh",
      "locale": "zh-CN",
      "audienceAngle": "low-cost-transfer",
      "heroTitle": "少烧 TRX，先看清路径，再下单。",
      "heroSummary": "面向先比较成本、再决定购买方式的中文用户，优先承接价格判断、FAQ 排疑和 TG/页面转化动作。",
      "primaryCta": "to-pricing",
      "backupCta": "to-help",
      "trackingPreset": "click_buy",
      "allowedParams": [
        "utm_source",
        "utm_medium",
        "utm_campaign",
        "utm_content",
        "utm_term",
        "gclid"
      ],
      "indexationMode": "noindex-follow",
      "proofPoints": [
        "先看价格和常见转账成本对比",
        "适合中文搜索和投放转化承接",
        "支持继续进入 FAQ 或 TG 咨询"
      ],
      "featuredFaqSlugs": [
        "energy-vs-burn",
        "transfer-fail-after-rental"
      ],
      "status": "published",
      "updatedAt": "2026-05-04T15:05:00.000Z"
    },
    {
      "id": "landing-api-batch-routing-en",
      "channel": "api",
      "campaignSlug": "batch-routing",
      "locale": "en",
      "audienceAngle": "batch-api-operators",
      "heroTitle": "Route repeated energy demand through a cleaner API entry.",
      "heroSummary": "Built for teams that need batch energy requests, clearer integration expectations, and a faster path from landing traffic to API onboarding.",
      "primaryCta": "to-api",
      "backupCta": "to-pricing",
      "trackingPreset": "click_api_apply",
      "allowedParams": [
        "utm_source",
        "utm_medium",
        "utm_campaign",
        "utm_content",
        "agent_id",
        "ref"
      ],
      "indexationMode": "noindex-follow",
      "proofPoints": [
        "Direct handoff from campaign to API onboarding",
        "Better fit for repeated or operational demand",
        "Pricing and support remain one click away"
      ],
      "featuredFaqSlugs": [
        "route-selection",
        "energy-vs-burn"
      ],
      "status": "published",
      "updatedAt": "2026-05-04T15:05:00.000Z"
    }
  ]
}

Frontend Contract

前台接线目标

服务投放页、联盟页和 TG 渠道页的结构化内容源。

Consumer

gastx-web /[locale]/landing/[channel] 与投放模板

Primary key: campaignSlug

Status field: status

Collection shape

后续前台应按这个集合形状取数，而不是继续在页面里硬编码文案常量。

Fields: 12

Records: 3

Schema

统一内容 schema

Field	Type	Required	Notes
channel Channel	enum	Required	google、facebook、tiktok、telegram、affiliate。
campaignSlug Campaign slug	string	Required	前台落地页唯一键。
locale Locale	enum	Required	渠道页语种。
audienceAngle Audience angle	string	Required	例如 cheap-usdt-transfer、api-reliability。
heroTitle Hero title	string	Required	落地页首屏标题。
heroSummary Hero summary	text	Required	首屏描述。
primaryCta Primary CTA	string	Required	主转化动作。
backupCta Backup CTA	string	Optional	次级引导。
trackingPreset Tracking preset	enum	Required	调用 tracking-core 的事件预设。
allowedParams Allowed params	string[]	Required	前台保留的 query 参数白名单。
indexationMode Indexation mode	enum	Required	通常 noindex-follow。
status Status	enum	Required	draft、ready、published。

Records

用于前台替换静态内容的记录

面向搜索广告，强调节省 TRX 消耗和快速到账。

Channelgoogle
Anglelow-cost-transfer
Primary CTAto-pricing
Trackingclick_buy

面向 TG 用户，突出机器人下单和提醒通知路径。

Channeltelegram
Anglechat-driven-ordering
Backup CTAto-bot
Indexationnoindex-follow

面向合作方和分销方，解释 API 接入与合作入口。

Channelaffiliate
Anglepartner-scale
Primary CTAto-partners
Allowed paramsutm_*, aff_id, ref

Editor

编辑面板

先把编辑器分区收口，后续不论接真实 CMS 还是 API，都能按这个面板结构推进。

Campaign identity

落地页先固定渠道、slug、语种和受众角度。

channel
campaignSlug
locale
audienceAngle

Hero and CTA payload

把页面文案与主备 CTA 结构化，便于前台模板复用。

heroTitle
heroSummary
primaryCta
backupCta

Tracking and SEO guardrail

增长页只声明跟踪预设和索引模式，不做广告账户后台。

trackingPreset
allowedParams
indexationMode
status

Module Flow

上下游协作关系

Upstream inputs

Site Settings统一品牌语气、TG/API/合作 CTA 与 tracking/pixel 默认项。Locale Content按市场和语种决定投放页覆盖范围。

Feeds into

SEO Pages声明 noindex、canonical 和 Paid/Organic 冲突备注。FAQ高频投放疑虑回落到 FAQ。

Checkpoints

运营收口要求

每个渠道页必须有受众角度、参数白名单和主/备 CTA。
像素位和事件命名来自统一配置，不散落在落地页备注里。
不要把广告账户管理、归因报表或联盟结算做进这个模块。

Field Planning

第一阶段字段边界

Campaign identity

Channel
Campaign slug
Locale
Audience angle
Offer type

Conversion setup

Hero copy
Primary CTA
Backup CTA
Tracking preset
Allowed params

Tracking & routing

Primary event
Pixel groups
Lead destination
Support fallback
Redirect rule

Guardrails

Indexation mode
Compliance note
Owner
Sunset date

Workflow

内容工作流说明

Draft

Content editor

录入文案、FAQ、SEO 字段和基础 CTA，不在这里接真实业务执行。

Review

SEO / Growth ops

检查索引策略、多语言一致性、渠道文案边界和合规提示。

Ready

Site owner

确认发布窗口、关联页面和投放节奏，避免内容与渠道错配。

Publish

System hook later

后续由 CMS 发布流或内容 API 接管；当前阶段只保留流程说明。

Future Hooks

后续扩展预留

后续可接 tracking preset、aff_id、agent_id、utm 模板，但不做广告平台账户管理。
可为 TikTok、Meta、Google、Telegram、联盟预留差异化 CTA 和合规备注。
允许落地页生命周期字段，例如上线窗口和停投日期。

Channel landing page management

渠道页上线前必须走完的路径

Live landing entries

Lower the transfer burn, keep the route predictable.

更适合聊天式下单和后续提醒的能量入口。

Partner workflows for affiliate traffic, API routing, and repeat demand.

Channel Landing JSON editor

前台接线目标

Consumer

Collection shape

统一内容 schema

用于前台替换静态内容的记录

Google / low-cost transfer

Telegram / zh-CN

Affiliate / API partner

编辑面板

Campaign identity

Hero and CTA payload

Tracking and SEO guardrail

上下游协作关系

Upstream inputs

Feeds into

运营收口要求

第一阶段字段边界

Campaign identity

Conversion setup

Tracking & routing

Guardrails

内容工作流说明

后续扩展预留