Use case - different content for subscribers vs. non-subscribers

Techniques for how to show different content for subscribers vs. non-subscribers

What to know up front

• Your app owns entitlement (who is a subscriber). Experiences don’t validate subscriptions for you.
• CMS owns packaging (labels + schedules). Your app uses that packaging to request the right content set for each viewer.

Recommended approach: two access labels

Create a simple access label scheme, for example:

• access:free — content intended for all viewers
• access:subscriber — content intended only for subscribers

Apply these labels to assets (during creation, via rules, or in CMS). See [

What content managers do in CMS

• Label assets consistently: every asset that should be gated gets one of the access labels.
• Schedule labels: content is eligible for delivery only when its label schedule window is active. See Labels mechanism

Decide the experience you want

• Hard split: non-subscribers see only access:free; subscribers see only access:subscriber.
• Subscriber-first: everyone sees access:free; subscribers also see access:subscriber and it appears first.