Skip to Content
Product guidesPreferences

Subscription lists and Preference Centers

Subscription lists are the durable preference model. Preference Centers organize those lists into localized, app-targeted UI.

Engage subscription list inventory with key, scope, channels, default state, status, and update time
Subscription lists define the durable consent vocabulary independently of any one Preference Center layout.

Subscription list

A list has a stable key, localized display name/description, supported scopes, supported channels, default subscription state, and active/archived status.

Scopes:

  • installation: choice applies to one installed app instance;
  • profile: choice follows the identified person across installations.

Channels are push, email, SMS, and WhatsApp. A list can support more than one channel. A profile may subscribe to push while unsubscribing from SMS for the same list.

Preference Center

A center defines localized display text, target apps, sections, ordered list keys, and whether it is the default. It has draft, active, or archived status plus separate draft and published revisions.

Editing an active center does not change SDK UI until publish. Only active lists should be included in a published center.

Engage Preference Center authoring view with localized sections, ordered subscription lists, app targets, drafts, and publication state
Preference Centers compose published lists into app-targeted, localized SDK interfaces without changing the underlying choices.

Client presentation

Use the ready-made SDK display method or render the headless center projection. Write choices through profile/installation subscription editors so the same durable operation and eligibility model is preserved.

Subscription choice does not override a more restrictive control. Push delivery also requires system permission, global Engage push opt-in, token registration, privacy eligibility, and provider readiness.

Governance checklist

  • Assign legal/product ownership to each list.
  • Document scope and channels.
  • Avoid silently changing the meaning of an existing key.
  • Make default subscription state explicit and lawful.
  • Preserve published revisions for audit.
  • Test locale, screen reader, and offline behavior.
Feature flagsContent system