Profile culling — self-serve filter and anonymous-only controls

Account admins can now tune profile culling directly, deciding which profiles the nightly cull job drops from the profile store without routing the change through an account manager. Author the cull rule with the same segment builder you use for audiences, see how many profiles currently match before you save, and adjust the anonymous-only retention window on your own schedule — handy for keeping the profile store focused on identifiable people and for trimming the long tail of stale anonymous traffic.

How it works

• Compose the cull rule in a segment builder that uses the same FilterQL grammar as the audience builder, with a live audience-size preview so you can sanity-check scope before committing.
• Set an independent days-old threshold for anonymous-only profiles — those with a single alias and only auto-generated _uids.
• Both controls live under Account → Settings -> Profile in a new Cull Profiles section.

Scope

• The filter takes precedence: when Cull User Filter is set, the nightly job ignores Cull Anonymous Users — the two don't stack.
• Culling removes profiles from the profile store but not the underlying event data. If new events later arrive for a culled alias, the profile is rebuilt with its prior history.

See Profile Controls for the full setting reference.