Analytics & Attribution
Meta Retired Total Video Consumption Rate. Rebuild the KPI Before the Trend Breaks.

Updated: November 11, 2026
Meta’s v27 launch notes retire total_video_consumption_rate across API versions, with no direct replacement. Dashboards that expect the field may show blanks, zeroes or failed jobs. Label the last valid date and preserve the original definition. Do not backfill a new formula into the old series without a visible methodology break.
A retired metric breaks the time series
Meta’s v27 launch notes retire total_video_consumption_rate across API versions, with no direct replacement. Dashboards that expect the field may show blanks, zeroes or failed jobs.
Label the last valid date and preserve the original definition. Do not backfill a new formula into the old series without a visible methodology break.
Map the decision behind the KPI
Identify whether the rate was used for creative quality, reach efficiency, audience comparison or reporting. The replacement should answer that decision, not imitate the old label.
List every dashboard, alert, client report and optimization rule that consumes the field. Remove automated actions before missing data triggers a false conclusion.
Operating control table
| Control | Evidence | Failure prevented |
|---|---|---|
| Owner | Named reviewer and decision | Unclaimed change |
| Configuration | Saved source state | Cannot reproduce |
| Validation | End-to-end fixture | Partial success accepted |
| Threshold | Success and rollback rule | Result reinterpreted |
| Evidence | Public or reporting read-back | Configured mistaken for delivered |
Choose supported component measures
Use available video starts, watch-time milestones, completed views, reach, impressions and downstream outcomes as appropriate. Confirm exact platform definitions and availability by placement.
A custom ratio is a new metric. Name its numerator, denominator, window and exclusions so analysts can reproduce it.
Rebaseline before comparing performance
Run the replacement measure on a recent historical window where component data is available. Set new thresholds instead of copying the retired benchmark.
Annotate reports at the change date and avoid year-over-year claims that join unlike definitions. Show both series separately when stakeholders need context.
Validate the business outcome
Pair viewing measures with qualified site behavior, conversions or lift evidence. A high consumption metric may reflect entertainment without valuable response.
Review the new KPI after several reporting cycles. Keep raw supported fields available so future platform changes do not require rebuilding from a derived dashboard alone.
Connect the control to the wider system
Use this process alongside the catalog video fidelity review. The platform setting, creative promise, measurement rule and downstream experience should describe the same decision.
Pre-launch checklist
- Write the decision and owner in plain language.
- Capture the source configuration and evidence.
- Test one realistic customer or reporting path end to end.
- Verify mobile presentation, links and accessibility.
- Record the success threshold and rollback trigger.
- Schedule the next review before material spend accumulates.
Run a cross-functional release review
Ask the channel owner, creative lead, analyst and conversion owner to inspect the same case. Each reviewer should state what was configured, what the customer sees, which event proves the outcome and which limitation changes the interpretation.
Repeat the test on mobile and with one adverse condition. Resolve differences in the campaign brief and measurement plan before launch.
Set the review cadence before launch
Assign a monitoring owner, review frequency and evidence threshold before the change is released. Preserve the pre-change baseline and avoid silently editing the definition after results arrive. This turns the launch into a measurable operating decision instead of a one-time interpretation of platform guidance.
At the first review, reconcile the source platform, public experience and one downstream business system. Close the change only when all three support the same conclusion, and record any limitation that future analysts must preserve.
Frequently asked questions
Should this be automated?
Automate repeatable validation and monitoring, but keep material policy, claim and budget decisions inside named approval limits.
What evidence should be preserved?
Keep the source configuration, decision owner, expected outcome, observed result and any exception that changes interpretation.
When should the team roll back?
Rollback when the control is inactive, the customer experience breaks, totals do not reconcile or the agreed threshold is breached.
