The following configuration options are available within the account settings Profile section.

Enable Schema Patches

Enables the Schema Patches workflow for this account. With patches enabled, admins can stage a batch of schema changes — fields, mappings, and identity key ranks — into a named changeset, review the diff against the live schema, and apply everything as a single published version. Disabled accounts edit the schema directly through the unpublished draft.

Promoted Fields

List of fields outside the defaults that should be leveraged in data science modeling and reporting.

Hide Private Fields

Hide PII/Private fields from audience exports and scans initiated by users who do not have access to private fields.

Cull User Filter

Segment expression that selects profiles to remove from the profile entity store and search index during the nightly cull job. Click the edit icon to compose the filter — the editor is the same one used to define an audience, with a live size preview showing how many profiles currently match. The expression is validated when saved, so invalid filters are rejected immediately. When set, this filter takes precedence over Cull Anonymous Users; only one runs.
Note: Culling removes profiles from the profile store but does not delete the underlying event/identity data retained elsewhere in the pipeline. If new events later arrive for an identifier that belonged to a culled profile, the profile can be rebuilt with its prior event history. Use the Clear filter button to remove the filter entirely and disable filter-based culling.

Cull Anonymous Users

Age threshold, in days, for removing anonymous-only profiles during the nightly cull job. A profile is considered anonymous-only when it has a single alias and only auto-generated user IDs (_uids) — i.e., no email, customer ID, or other persistent identifier. This setting is ignored when Cull User Filter is set; the two settings do not stack.