Prove what's truly incremental in your marketing
The problem with platform-reported ROAS
- Non-incremental conversionsTypically 20–60% of attributed conversions are non-incremental — they would have happened without the ad. Platform ROAS is inflated by exactly this share.
- The calibration factorTrustData measures the ratio of your true incremental conversions to platform-claimed conversions. This calibration factor — typically 0.3–0.8 — corrects your optimizer's revenue model.
- Why it changes budget decisionsA Meta campaign with reported ROAS 4.0 and calibration factor 0.45 has a true iROAS of 1.8. That changes whether you scale, hold, or cut — and changes your optimizer's recommendations entirely.
Geo holdout — the gold standard
- Matched region controlTest and control regions are selected to be as similar as possible in baseline conversion rates. TrustData uses your first-party regional conversion data from ClickHouse for matching.
- Trend extrapolation counterfactualThe counterfactual is built from pre-period trend extrapolation — not naive averaging. A permutation test with 1,000 shuffles of test/control labels provides the p-value.
- Direct calibration outputResult: lift_pct, iROAS, p_value, and calibration_factor = our_iROAS / platform_reported_ROAS. This factor is immediately applied to the budget optimizer.
Time holdout — simplest to run
- No regional data requiredTime holdouts work with any first-party conversion data — no regional breakdown needed. Best for answering "is this channel incremental at all?"
- Prophet counterfactualTrustData fits a Prophet time series model on your pre-period daily conversion data, forecasts what would have happened during the pause, and compares the forecast to actuals.
- Seasonal robustnessProphet accounts for weekly seasonality and trend changes. Where Prophet isn't available, TrustData falls back to a linear extrapolation with z-test significance calculation.
Platform lift test — least friction
- Platform handles the holdoutMeta and Google randomize audiences into test and control groups. You run the test as normal — TrustData reads your first-party results and compares against platform claims.
- Calibration from first-party datacalibration_factor = our_measured_lift / platform_claimed_lift. This ratio tells you how much to discount the platform's attribution claims for this audience type going forward.
- No geo data requiredPlatform lift tests work at the audience level — no regional conversion data needed. Best for e-commerce brands without regional tracking or for audience-level holdouts on Meta.
Calibration feeds directly into the budget optimizer
- Automatic calibration updateWhen a test concludes, TrustData updates the CalibrationFactor for that channel and immediately triggers a response curve rebuild and budget optimization run.
- Temporal decay modelCalibration factors decay over time — 50% weight at 90 days, 25% at 180 days. The optimizer degrades gracefully toward uncalibrated rather than relying on stale data.
- Re-test recommendationsWhen a calibration factor becomes stale (>90 days), TrustData automatically creates a low-urgency recommendation to run a new test. Untested channels are flagged in the budget optimizer UI.