Skip to content

Use case: Carousel view

Sample news app showing carousel of Content Cards in an article.

This section covers how to implement a multi-card carousel feed where a user can swipe horizontally to view additional featured cards. To integrate a carousel view, you’ll need to use a fully customized Content Card implementation—the “run” phase of the crawl, walk, run approach.

With this approach, you will not use Braze’s views and default logic but instead, display the Content Cards in a completely custom manner by using your own views populated with data from the Braze models.

In terms of the level of development effort, the key differences between the default implementation and the carousel implementation include:

  • Building your own views
  • Logging Content Card analytics
  • Introducing additional client-side logic to dictate how many and which cards to show in the carousel


Step 1: Create a custom view controller

To create the Content Cards carousel, create your own custom view controller component (such as UICollectionViewController) and subscribe to data updates.

Step 2: Implement analytics

When creating a custom view controller, Content Card impressions, clicks, and dismissals are not automatically logged. Be sure to call the respective methods from the context object on your Braze.ContentCard to ensure impressions, dismissal events, and clicks get properly logged back to Braze’s dashboard analytics.

For information on the analytics methods, refer to Card methods.

Step 3: Create a Content Card observer

Implement logic that observes for changes in your Content Cards, handles Content Card arrival, and displays a specific number of cards in the carousel at any one time. By default, Content Cards are sorted by created date (newest first), and a user sees all cards they are eligible for.

With that said, you could order and apply additional display logic in a variety of ways. For example, you could select the first five Content Card objects from the array or introduce key-value pairs (the extras property in the data model) to build conditional logic around.

If you’re implementing a carousel as a secondary Content Cards feed, refer to Using multiple Content Card feeds to ensure you sort cards into the correct feed based on key-value pairs.

For iOS-specific developer documentation on the Content Cards class, methods, and attributes, refer to the Braze ContentCard class reference.


  • By using completely custom views, you will not be able to extend or subclass the methods used in BrazeContentCardUI.ViewController. Instead, you’ll need to integrate the data model methods and properties yourself.
  • The logic and implementation of the carousel view is not a default type of Content Card in Braze, and therefore the logic for achieving the use case must be supplied and supported by your development team.
  • You will need to implement client-side logic to display a specific number of cards in the carousel at any one time.
New Stuff!