Snapshots
A realtime audience is answered from two halves: live behaviour from the event stream, and the warehouse attributes you already know. The warehouse half is not queried at read time — it is precomputed into a snapshot and rebuilt on a schedule. Snapshots is where you set that schedule, rebuild off it, and check what the last rebuild did.
Experimental — in active development. The behaviour described here may change before general availability.
Where to find it
Navigate to Personalize → Membership → Snapshots.
The rebuild schedule
The cadence is set once per workspace and drives every realtime audience in it. There is no per-audience schedule — one setting decides how fresh the warehouse half of every verdict is, so you tune freshness in one place rather than audience by audience.
Each audience is rebuilt on its own, so one that fails does not hold up the others: its own row in the history says what went wrong, and the rest of the workspace rebuilds normally.
The available cadences are every 4, 6, 8, 12, or 24 hours, or off. A workspace that has never set one rebuilds every 24 hours. Off means nothing is scheduled and snapshots change only when you rebuild by hand.
To change it, use the schedule control on the Snapshots tab and pick a new value under Rebuild every. The page also shows, in plain words, when the next scheduled rebuild will run and what the last one did — you do not have to open the dialog to see either.
Changing the cadence requires the workspace settings permission.
A longer cadence does not make membership stale in general — only the warehouse half of it. Conditions about what someone just did are still evaluated live, within about a second, no matter what the cadence is. Choose the cadence based on how quickly your attributes change, not on how live you need behaviour to be.
Rebuilding now
Rebuild all now rebuilds every audience in the workspace immediately, off schedule. Use it after changing something the warehouse half depends on — a model, a source table, an audience’s attribute conditions — when you do not want to wait for the next scheduled run.
It runs one warehouse query per audience, so it has a real cost; the confirmation says so. If a cadence is set, the scheduled rebuild would have covered the same memberships anyway.
Rebuilding requires the audience write permission.
The rebuild runs in the background. You do not have to wait on the page — Rebuild history below shows the result when it finishes.
Rebuild history
Rebuild history lists past rebuilds with their outcome, so “did it run, and what did it do?” is answerable without guessing. Check it when:
- An audience is missing from a Membership API response — an audience that has never been rebuilt has no warehouse half to answer from, so it is not served at all.
- A verdict disagrees with what you see in the warehouse — compare the time of the last rebuild against when the underlying data changed.
- You started a rebuild and want to confirm it finished rather than failed.
Next Steps
- Membership API — how snapshot freshness shows up in a verdict.
- Realtime Audiences — which conditions land in the warehouse half and which are evaluated live.