Prepare a Tracker

The modelling workflow starts from a long-format tracker. Use one row per extracted effect estimate.

Required columns

client,evidence_type,metric,value,unit,period,source_type,source_status,source_file_or_link,owner_or_contact,analysis_ready,notes

Optional uncertainty columns

study_id,estimand_note,standard_error,ci_lower,ci_upper,ci_level,ci_type,p_value,p_value_sidedness,uncertainty_scenario

Supported pooled evidence

Evidence Default treatment
geo_test Pool comparable effects on log_relative scale.
bls Pool comparable effects on percentage_point scale.
mmm, pa2, ROI, CPA, CPO, iROAS Treat as triangulation unless harmonised upstream.

Validate the tracker

marketbayesmeta-check-tracker path/to/tracker.csv
marketbayesmeta-check-tracker path/to/tracker.csv --audit --include-partial

Resolve or explicitly accept:

  • duplicate (evidence_type, client, metric, period) candidates;
  • missing source uncertainty;
  • interval rows missing ci_type or ci_level;
  • p-values without p_value_sidedness=two_sided;
  • rows marked analysis-ready but using a unit incompatible with the requested scale.

Estimand judgement

The tracker and config enforce metric names and units, but they cannot prove that studies answer the same business question. Before pooling, confirm that population, measurement window, study design, and estimand are comparable enough for a pooled effect to mean something.