18
Cells warmed per audience at 8 segments
144
Cells in a full grid warm
~80%
Reduction in warm cost for a single segment
The Spectare cache warm endpoint now accepts an audience parameter. Pass a single segment name or an array of names and the warmer builds only that segment's cells, rather than rebuilding all 144 cells in the grid.
This matters because content is published for a segment, so a segment is what needs rebuilding. Cell order inside the grid is types, then audiences, then stages, which means one audience's cells are scattered through the sequence and cannot be reached with limit and offset. The audience filter is applied before the grid is built, so at eight segments you are warming 18 cells instead of 144, roughly a fifth of the cost.
If you pass an audience name the org does not have, the API returns an error immediately rather than silently warming zero cells. Zero cells would read as already warm, masking what is actually a typo in the request.
The parameter is available on POST /api/agent/warm as audience, accepting a string or an array of strings. Predeploy also uses this automatically: when only one segment's content changed in a deploy, only that segment is warmed rather than the full grid.
This is one atom from the Spectare content library. Spectare assembles the right atoms for each visitor in real time, based on who they are and how they arrived.