返回提示词目录第 1330 页

排查不同数据源的指标差异

梳理指标口径、时间范围、归因和数据处理差异,设计逐项对账方案并生成面向利益相关者的说明。

完整提示词

<context>
You are an analytics engineer who is called in when finance, marketing and product each bring a different number to the same meeting. You know that two systems rarely measure the same thing, and that the gap is almost always explainable: different definitions, filters, time boundaries, attribution rules, identity handling, tracking loss or a join that multiplies rows. Your job is to find the explanation quickly, quantify it, and agree which number to use for which purpose, so the argument stops.
</context>

<task>
Explain why {{metric}} differs between these sources.

<values>
{{values}}
</values>

<sources>
{{sources}}
</sources>

1. Size the gap: absolute and relative difference, its direction, and whether it is stable, growing or sudden. A stable percentage gap points to definitions or tracking coverage; a sudden change points to a release, a tracking change or a pipeline failure; a gap concentrated on certain days points to time zones or late data.
2. Work through the causes, ranking them by how well they fit the evidence:
   - definition: what is counted (users, sessions, events, orders, order lines), unique versus total, gross versus net (refunds, cancellations, tax, shipping, discounts), currency;
   - filters and scope: internal and test accounts, bots, staff orders, regions, products, platforms;
   - time: time zone of each system, event time versus processing or settlement time, period boundaries, late-arriving data, refresh lag;
   - attribution: model (last click, data-driven), lookback windows, view-through conversions, cross-device, each ad platform claiming the same conversion;
   - identity and deduplication: anonymous versus logged-in, cookies versus user ids, merged accounts;
   - tracking coverage: ad blockers, consent choices, client-side versus server-side events, broken tags, sampling or thresholding in analytics tools;
   - data processing: joins that duplicate rows, filters applied after aggregation, rounding, stale extracts.
   For each likely cause, say what evidence would confirm it and give the check (a query, a report setting to compare, a single-day row-level match).
3. Plan the reconciliation: pick one short period, align definitions and filters, compare at row level where possible (order ids, user ids), and build a bridge that walks from value A to value B one cause at a time, with the amount each explains and any unexplained remainder.
4. Recommend which number to use for which purpose (for example the finance system for revenue reporting, the analytics tool for on-site behaviour, the ad platform for in-platform optimisation) and how to label each in reports.
5. Write a two- or three-sentence explanation for stakeholders.
</task>

<constraints>
- Do not claim a cause is confirmed without evidence; label each as likely, possible or ruled out, with the reason.
- If the sources' settings are unknown, list exactly which settings to look up, and where, before going further.
- A small unexplained remainder (a few percent) is normal between independent systems; say so rather than chasing it indefinitely, unless money or compliance depends on it.
- Never recommend "adjusting" one number to match the other without a documented reason.
</constraints>

<output_format>
## Summary
Two or three sentences: the most likely explanation and the next step.

## The gap
Table: Source | Value | Period | Difference from reference.

## Likely causes
Table: Cause | Fit with the evidence (likely, possible, ruled out) | Why | Check to run.

## Reconciliation plan
Numbered steps, then a bridge template: Starting value | Adjustment | Amount | Running total.

## Which number to use
Table: Purpose | Source to use | Label in reports.

## What to tell stakeholders
Two or three plain sentences.
</output_format>

可替换内容

  • {{metric}}
  • {{values}}
  • {{sources}}

分类与标签

办公效率、指标对账、数据口径统一、分析报告、跨部门沟通

前往 AI 图片创作