# Retiring an audience without breaking pages

URL: https://kywi-docs-production.up.railway.app/targeting/retiring-an-audience-without-breaking-pages
Type: docPage

Archiving stops matching without touching a single reference; deleting is guarded by a reference check unless you force it.

Archiving and deleting an audience do very different things to the pages that still point at it. Picking the right one is the whole question this page answers.

## Archiving is reversible, and touches nothing else

Archiving is a plain status change, and nothing checks whether the audience is still bound to a live page's arm before allowing it. It stops mattering only because matching itself reads active audiences — an archived one is simply skipped when the engine looks for a winner. Every page's binding to it, and the row itself, survive untouched, which is what makes archiving reversible: reactivate the audience and whatever pointed at it resumes matching exactly as before.

## Deleting is guarded

Deleting is the one destructive path with a real check: by default it looks for the audience anywhere it might still be referenced — a page's variants, an arm inside a variant container, an active preview token — and refuses with a list of what's still using it if it finds any. Reassign or remove those references first, or use the override below once you're certain.

## A dangling reference fails silently into a working page

`?force=true` deletes the audience regardless of what still points at it, and every one of those references becomes an id that no longer resolves to anything. That's not an error at render time: an arm bound to a missing audience simply never matches, so its container falls through to the next thing in the precedence chain — a locked winner, a split, or Default. Nothing breaks visibly; the page just quietly stops personalizing for whoever that audience used to match.

## The check has a limit

The reference scan works through a capped number of candidate pages before concluding an audience is safe to delete — on a site with more bound pages than that cap, it can miss a reference. Treat a clean check as strong evidence, not an absolute guarantee, on a very large site.

In short: archive when you might still want the audience's history or might reactivate it later — nothing breaks, matching just stops. Delete only once nothing depends on it, which the guard enforces unless you force past it — and forcing past it is a deliberate choice to let those pages fall back silently, not an oversight.
