About Content Cards
Content Cards are embedded directly into your app or website so that you can engage users with an experience that feels natural and seamless. They give you more control over your app or website experience, and let you create message inboxes, carousels, and banners, and extend the reach of other channels (such as email or push notifications).
Content Cards are an add-on feature and must be purchased. To get started with Content Cards, reach out to your Braze customer success manager or our support team.
If you’re using our News Feed tool, we recommend that you move over to our Content Cards messaging channel—it’s more flexible, customizable, and reliable. News Feed is also being deprecated. See our Migration Guide or contact your Braze account manager for more information.
Benefits of using Content Cards
Here are just a few benefits of using Content Cards versus having your developers build content into your app:
- Easier segmentation and personalization: Your user data lives in Braze, making it easy to define your audience and personalize your messages with Content Cards.
- Centralized reporting: Content Card analytics are tracked in Braze, so you have insight into all of your campaigns in one location.
- Cohesive customer journeys: You can combine Content Cards with other channels in Braze to create consistent customer experiences. A popular use case is sending a push notification, then saving that notification as a Content Card in your app for anyone who didn’t engage with the push. If the content is built directly into your app by your developers, then it’s isolated from the rest of your messaging.
- No required opt-in: Similar to in-app messages, Content Cards don’t require opt-in or permissions from your users. But while in-app messages are permissionless and short-lived, Content Cards are permissionless and permanent. This means messaging strategies that pair together in-app messages and Content Cards strike a great balance.
- More control over the messaging experience: While you’ll still need your developers to help with the initial setup of Content Cards, afterward, you can control the message, recipients, timing, and more directly from your Braze dashboard.
Content Cards by the numbers
Because you, the marketer, are building Content Cards yourself in Braze, you can make messaging updates and receive a return on investment without having to completely overhaul your app or website. Here are some helpful statistics on the ROI of Content Cards:
- Content Cards are 38X more effective than emails at boosting sales over a 72-hour window.1
- Using Content Cards in loyalty enrollment campaigns boosts conversions by 5X.1
- Sending users outreach through push notifications, in-app messages, and Content Cards results in 6.9X more sessions, compared to users engaged through push alone.2
- Sending users outreach through email, in-app messages, and Content Cards results in 3.6X longer average user lifetime, compared to users engaged through email alone.2
How it works
At their core, Content Cards are actually a payload of data, not what the data looks like. Braze provides template views (banner, modal, captioned image) to display the Content Card data, which is ultimately what your message looks like.
Now let’s get a little technical. Behind the scenes, there are three main parts of a Content Card:
- Model: What kind of data lives in the card
- View: What the card looks like
- Controller: How the user interacts with the card
For a default implementation, you add the card content—the model—either from the dashboard or through APIs, and the view and controller are handled by what is called a view controller. A view controller is the “glue” between the overall application and the screen.
Use cases
Refer to this section for some common use cases for Content Cards.
For more inspiration, we highly recommend that you check out our Content Cards Inspiration Guide, which includes over 20 customizable campaigns, including referral programs, new product launches, and subscription renewals.
Showcase Content Cards at the top of a user’s homepage to encourage event attendance, using location targeting to reach potential users where they are. Inviting users to relevant physical events makes them feel special, especially with personalized messaging that leverages their previous activity with your brand.
Use the data you have on user behaviors and preferences to surface relevant content in real time from homepage or inbox Content Cards and draw them back into your product offering.
Take advantage of Content Cards to highlight promotional messages and unclaimed offers directly on your homepage or in a dedicated promotional inbox. Pull in relevant content based on each customer’s previous purchases to deliver attention-grabbing personalized promotions.
Other use cases
Outside of these main use cases, our customers use Content Cards in so many different ways. The power of Content Cards is their flexibility. If the use case you want is not shown here, you can set up key-value pairs and send the payloads to your app or website.
Content Card placements
This section covers the three most common ways to place Content Cards within your app or website:
The logic and implementation of these placements are not a default in Braze, so your engineering team must supply and support the work for achieving these use cases. For an overview on how to implement these placements, refer to Creating custom Content Card.
Message inbox
A message inbox (also called a notification center or feed) is a persistent place in your app or website where you can display Content Cards in whatever format you prefer. Each message in the inbox is its own Content Card.
The message inbox is a default implementation with minimal development needed. Braze provides a view controller for a message inbox on iOS, Android, and web to make the creation process easy.
Benefits
- Users can receive many cards in one place
- Efficient way to resurface information missed or dismissed on other channels (especially push notifications)
- No opt-in required
Behavior
When a user is eligible for a card, it will automatically appear in their inbox. Content Cards are built to be viewed in bulk, so users can view all cards that they’re eligible for at once.
With the default implementation, Content Cards in the inbox can appear as classic (containing a title, text, and an optional image), image only, or captioned image cards. You choose where the message inbox will be located in your app.
Content Cards come with a default style, but you can choose a custom implementation to display the cards and the feed according to the look and feel of your app.
Carousel
Carousels display multiple pieces of content in a single space that your customers can swipe into view. They can be a slideshow of images, text, video, or a combination of them. This is a custom implementation and requires a bit of work from your developers.
Benefits
- Users can receive many cards in one place
- Engaging way to surface recommendations
Behavior
When a user is eligible for a card, it will appear in a carousel on whichever page of your app the carousel is added to. Users can swipe horizontally to view additional featured cards.
Because this is a custom implementation, you’ll need to work with your developers to build your own views to display the Content Cards. The default classic, image only, and captioned image cards aren’t supported with this implementation.
Banner
Content Cards can appear as a dynamic banner that persistently displays on your home page or at the top of other designated pages.
Benefits
- Persists on the page unlike an in-app message, so you have more time to reach your audience
- Great way to showcase new content in a prominent location on your home page
Behavior
Users can view and engage the most relevant content they are eligible for. Because this is a custom implementation, you’ll need to work with your developers to customize the views to display the Content Cards.
Integrating Content Cards
Your developers will integrate Content Cards when they integrate the Braze SDK. For more details on how to integrate with Content Cards, refer to the developer guide articles for your platform:
Sources