Braze Content Cards guide: use personalized, persistent content feeds for onboarding, discovery, promotions and retention.

Treat the feed as a product surface

Content Cards work best when customers can return to useful information over time. Design a taxonomy for onboarding tasks, recommendations, promotions, education, service notices or account actions. Define priority and expiration before adding campaigns so the feed does not become a pile of unrelated messages.

Implementation note: A feed should answer a customer need: what should I do next, what is relevant now, or what did I miss—not simply provide another stream of promotions.

Eligibility and personalization

Use behavioral state, profile attributes, lifecycle stage and product context to decide card eligibility. Keep the business rule separate from presentation so the same eligibility model can support multiple card variants. If an item has a destination, store or derive the deep link carefully and test the destination for every platform.

Implementation note: Document which fields determine eligibility and which fields only change creative; this makes debugging much faster when a card appears unexpectedly.

Web and app delivery considerations

Braze documents Content Cards for SDK-based experiences and notes that browser privacy tools can interfere with Web SDK delivery. Treat network availability and client version as part of QA rather than assuming every customer sees the feed identically.

Implementation note: For critical product notices, use a channel and delivery pattern designed for the required urgency instead of depending on a persistent feed alone.

Measure business outcomes

Track card impressions and interaction, but connect those events to a downstream action: activation, purchase, feature adoption, retention or service resolution. Compare feed engagement with alternative channels and monitor stale or ignored cards so the surface remains useful.

Implementation note: A successful Content Cards program is often defined by fewer, better cards rather than a larger message inventory.

Production scenario: onboarding checklist

A mobile app can use Content Cards for a five-step onboarding checklist. Eligibility changes after each completion event, card ordering follows the customer’s next best task, and each card deep-links to the exact product surface. QA covers fresh installs, partial completion, offline sessions, expired cards and customers who finish onboarding through another channel.