Initial Daily Campaign Agent release

This commit is contained in:
joliehill294-hue
2026-09-16 21:00:13 +08:00
commit 14fc94b3f0
86 changed files with 10766 additions and 0 deletions
@@ -0,0 +1,119 @@
# Standard daily brief format
Follow this four-section structure exactly. Keep the brief decision-led, but include
exact dates, mature windows, and enough evidence to audit each action.
## 1. 是否达标
Use compact lines:
```text
1. 是否达标
- KPI 1:实际值(达标/未达标;数据日期/成熟 cohort 日期;目标)
- KPI 2:实际值(达标/未达标;数据日期/成熟 cohort 日期;目标)
- 日消耗:实际值 / 目标值,差额 xx(达标/未达标;目标类型和范围)
```
Evaluate at the confirmed portfolio/account scope unless a narrower scope was given.
Never use the same date automatically for same-day acquisition and lagged retention or
revenue KPIs. Add at most two short caveats here for material maturity or data issues.
If KPI Gate B is unsatisfied, state `无法判定` and ask one consolidated question before
producing action labels.
## 2. 问题分析
Start directly with the Ad-level learning-period and stable-period pools. Do not add a
Campaign ranking table or `Campaign层级/层级判断` subsection. Campaign and Ad Group may
appear only in an Ad identity when duplicate names require disambiguation. Keep each
decision adjacent to its evidence, using a compact labeled line rather than a separate
visual card.
### 学习期池排名
| Rank | Ad | Age / checkpoint | Spend / budget fill | Mature KPI result | Peer position | Decision |
|---|---|---|---|---|---|---|---|
Rank comparable new Ads within the same objective and launch cohort. When multiple Ads
launch together, rank them within that test cohort. Explain day-3 pruning and
day-5/day-7 observation or promotion decisions.
### 稳定期池排名
| Rank | Tier | Ad | Latest mature day | Recent 7D / prior 7D | KPI pass pattern | Stability / change | Diagnosis | Decision |
|---|---|---|---|---|---|---|---|
Use exactly these tiers:
- `S-优质`:KPI超额完成且多日稳定。
- `A-稳定`:KPI达标,样本与持续性足够。
- `B-波动待优化`:存在波动或部分KPI未达成,但仍有明确优化空间。
- `C-劣质`:KPI严重或持续不达标,属于风险项。
Rank Ads within and across tiers by primary KPI, number of KPI passes, persistence,
sample confidence, and spend impact. Every row must include a concrete `决定` such as
protect, hold, reduce, optimize/retest, pause, or replace creative, together with its
checkpoint or exit condition when observation continues.
## 3. 建议动作
Group recommendations under only the headings that have qualifying rows:
```text
3. 建议动作
- 暂停:<完整层级名称>;原因:<证据>;释放配置预算 xx。
- 下调:<完整层级名称>;表现波动,建议预算从 xx 下调至 xx;保持至 <成熟日期/样本> 后复查;退出条件:xx。
- 保持观察:<完整层级名称>;当前通过 xx/总 KPI;保持哪些变量不变;在第 5/7 天或指定成熟日复查。
- 扩量:<Ad 名称>;近 xx 个成熟日表现很好;建议采用 <可用的受控扩量方式>;回退条件:xx。
- 补量:距离日消耗目标还差 xx;现有合格扩量容量 xx;仍缺 xx,需新增 Ads <数量或“待测试预算确认”>。
- 素材预警:<Ad 名称> 已连续跑 xx 天;历史表现好但近期严重下滑;建议验证疲劳/流量变化并准备新素材。
```
Budget rules:
- `配置预算` comes only from an explicit budget field or operator-provided history.
- If only spend is available, write `预计减少/释放日消耗约 xx` and label the estimate;
never call spend a budget.
- State an exact reduction only when a configured adjustment rule or credible prior
control exists. Otherwise state the direction and the missing value needed.
- After pause/reduction recommendations, recompute the expected pacing gap.
- Estimate the number of new Ads only when a standard test budget or a defensible
observed test-spend baseline exists; otherwise request that one value.
Every observation action must include a checkpoint and exit condition. A recommendation
never implies execution.
## 4. 近7天表现好的 Ads(3–5个)
| Rank | Ad(include Campaign > Group) | Stage | Spend / sample | KPI data | Consistency | Why good | Next use |
|---|---|---|---|---|---|---|---|
Choose three to five Ads only when they genuinely qualify. Rank durable stable Ads
before learning-period candidates. A learning Ad may appear only when clearly labeled
`学习期候选`, with its checkpoint and concentration risk. Return one or two, or state
`暂无合格 Ads`, rather than pad the list with weak traffic.
Explain why each is good using confirmed KPI performance, multi-day consistency,
sample, trend, and delivery—not adjectives alone. Keep immature outcomes out of the
negative evidence.
End with `以上均为人工决策建议,未执行任何平台变更。`
## Writing rules
- Use the user's four Chinese section names and order; do not add a separate executive
summary or duplicate action table.
- Do not add a title-page or pre-section `核心判断` paragraph. Begin the report body
directly with `1. 是否达标` after the title/date block.
- Use the exact subsection titles `学习期池排名` and `稳定期池排名`; never prefix them
with `规则一` or `规则二`.
- Do not add a named-Ad `近7日专项判断` section to the standard daily brief. Insights
from prior conversation about a specific Ad belong in the reusable follow-up
template, not as hardcoded daily-report content, unless the user explicitly asks to
include that Ad's drilldown in the report.
- Use exact calendar dates and exact mature-window ranges.
- Keep each conclusion or action close to its evidence and avoid repeated colored
callout boxes. Prefer direct labels such as `预算影响` and `继续观察` over generic
analysis prose.
- Separate observed facts, inference, and unverified causes.
- Show numerator/denominator for low-sample or concentration-sensitive ratios.
- If a subsection is empty, say `无` and why.