← Fiera IncrementalityCONTENT HISTORY
WHAT CHANGED
Update to Fiera Incrementality
Snapshot Oct 24, 2026 · 13:36 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Fiera Incrementality and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Review an incrementality or lift result someone else produced, such as a Meta or Google lift study report, a vendor's geo test, an agency deck, or an internal claim that a channel is or is not incremental. Checks design, statistics and interpretation, and says how much weight the result can carry. Use when the user shares a lift result, a test report or a screenshot and asks whether to trust it.",
"included_files": [
{
"relative_path": "assets/readout-template.md",
"size_in_bytes": 1058
},
{
"relative_path": "assets/test-plan-template.md",
"size_in_bytes": 1879
},
{
"relative_path": "references/data-format.md",
"size_in_bytes": 2479
},
{
"relative_path": "references/directional-methods.md",
"size_in_bytes": 4223
},
{
"relative_path": "references/geo-design-rules.md",
"size_in_bytes": 5553
},
{
"relative_path": "references/literature.md",
"size_in_bytes": 43626
},
{
"relative_path": "references/method-ladder.md",
"size_in_bytes": 4055
},
{
"relative_path": "references/platform-lift.md",
"size_in_bytes": 4707
},
{
"relative_path": "references/reading-results.md",
"size_in_bytes": 3462
},
{
"relative_path": "references/script-reference.md",
"size_in_bytes": 3739
},
{
"relative_path": "references/validation.md",
"size_in_bytes": 4026
},
{
"relative_path": "scripts/geolift.py",
"size_in_bytes": 61898
}
],
"name": "lift-result-review",
"skill_md_contents": "---\nname: lift-result-review\ndescription: Review an incrementality or lift result someone else produced, such as a Meta or Google lift study report, a vendor's geo test, an agency deck, or an internal claim that a channel is or is not incremental. Checks design, statistics and interpretation, and says how much weight the result can carry. Use when the user shares a lift result, a test report or a screenshot and asks whether to trust it.\n---\n\n# Lift result review\n\nGives an independent read on a lift or incrementality result: what it shows, what it does not, and whether it can support the decision being made.\n\nThe user's explicit instructions take priority over this guidance. Reply in the user's language.\n\n## Steps\n\n1. Identify what was run: platform lift study, geo experiment, switchback, pre/post, MMM output, or attribution presented as incrementality. Use `references/method-ladder.md` to place it on the ladder.\n2. Extract the facts stated in the material: KPI, source, treated and control groups, dates, sample sizes, effect, interval or p-value, spend. Mark what is missing. Never fill gaps with assumptions presented as facts.\n3. Check it against the list below.\n4. If the user has the underlying data, offer to recompute it with the `geo-test-readout` or `quick-incrementality` skills.\n5. Give the verdict.\n\n## Checklist\n\nDesign:\n\n- Was there a control group, and was assignment random (users or geos) or chosen?\n- Was the plan, including the KPI and the decision rule, set before the data came in?\n- Was the test long enough for the channel's carryover, with a cooldown for video and upper funnel?\n- Platform lift: which conversions were counted? Pixel-only events miss offline and cross-device outcomes; was CAPI or offline upload used?\n\nStatistics:\n\n- Is there an interval, and does it include zero?\n- What effect could the test detect (MDE or power)? A non-significant result from an underpowered test says little.\n- Was the result picked from several metrics, segments or windows? If so, discount it.\n- Geo tests: how many geos, how good was the pre-period fit, were placebos run?\n\nInterpretation:\n\n- Is \"incremental conversions\" being compared with attributed conversions to produce an incrementality factor? Is that factor applied to other campaigns or periods where it may not hold?\n- Is a go-dark result being used to justify a budget increase (a different question)?\n- Are lift results from different platforms being added together?\n- Is \"lift\" relative to the treated group's baseline, or to all conversions? Percentages on different bases are not comparable.\n\n## Verdict format\n\n- One line: how much weight the result can carry (decision-grade, directional, or not usable), and why.\n- What the result supports, and what it does not.\n- Missing information that would change the verdict.\n- The smallest next step that would make it decision-grade.\n\n## References\n\n- `references/platform-lift.md` for what Google and Meta lift studies measure and their thresholds.\n- `references/literature.md` for methods and published evidence.\n- `references/reading-results.md` for how results should be stated.\n\n## Rules\n\n- Be specific and fair: name the issue and its likely direction (overstates, understates, unknown).\n- Do not dismiss platform lift studies as biased by default. A randomized user-level holdout is a strong design; its limits are scope (one platform, its own conversion data), not randomization.\n- Do not invent numbers that are not in the material.\n"
}SHA-256 of public snapshot: 2345d1661a83d664aa10c5b08013cfe8a89b0bc714f1a46448209e64baab8763