.svg)
Braze advanced features such as Segment Extensions, Content Blocks and Catalogs each solve a different problem. Content Blocks hold reusable content, Catalogs hold item data, and Segment Extensions reach back through up to 730 days of event history. This guide sets out what each one does, where its documented boundaries sit, and the order we suggest adopting them.
Key Takeaways
- Content Blocks, Catalogs and Segment Extensions solve three separate problems: shared content, item data and long-lookback segments.
- Blocks inserted through Liquid stay linked to the original, so an edit to a live block reaches every message that uses it.
- Catalog storage is measured by the size of the catalog items, which may differ from the size of the files you upload.
- Segment Extensions look back up to 730 days, while a default segment already covers event properties from the past 30 days.
- We suggest adopting Content Blocks first, Catalogs second and Segment Extensions last.
What are Braze advanced features, and which ones does this guide cover?
"Advanced" is a loose label, so we use it narrowly here. We mean three features that sit on top of a working campaign and Canvas setup: Content Blocks, Catalogs and Segment Extensions. Every limit quoted below comes from the Braze docs as read on 27 Oct 2026.
Each feature answers a separate question. Content Blocks answer where shared content lives. Catalogs answer where item data lives, and Segment Extensions answer who did something a long time ago.
| Feature | What it holds | Documented boundary | Needs a data feed? |
|---|---|---|---|
| Content Blocks | Reusable, cross-channel content | Maximum of 50 KB per block | No |
| Catalogs | Item data you reference through Liquid | Storage is measured by the size of catalog items | Yes, imported files or API endpoints |
| Segment Extensions | Segments built on up to 730 days of history | 50 active extensions per workspace by default | Event history, plus SQL or a warehouse for the advanced types |
Why adopt Content Blocks before anything else?
We suggest starting with Content Blocks, because they need no new data and they pay back on the next campaign you build. Braze describes them as a way to "manage reusable, cross-channel content in a single, centralized location". A footer, an offer line or a legal paragraph written once removes a whole class of copy-and-paste drift.
Catalogs need a data source you trust, and Segment Extensions need a question worth asking. Content Blocks need only a piece of content you are tired of editing in several places. That makes them the lowest-risk way to build team habits around the platform.
What should you know before you edit a shared Content Block?
Braze documents two ways to place a block, and they behave differently. Blocks inserted through Liquid stay linked to the original and reflect changes to it. Blocks added by drag and drop are not linked, so later edits to the original do not reach them.
We treat that difference as the main failure mode, because a change to a Liquid-linked block updates every message that uses it. An edit to a live block is a release, not a tweak. Check the inclusion count in the block preview first: Braze shows a clickable list of the messages or blocks that use it.
Three more documented details are worth planning around:
- Nesting works once. A third level is accepted, but its content does not expand and is removed from the message.
- Links inside a nested block count toward the link total of the parent message.
- Canvas entry properties populate only in Canvases, so a block that uses them will not fill in a campaign.
Names cannot be changed after saving, and a name can never be reused, even after archiving. A block used in any message cannot be archived. Choose names for the team that will inherit them, and keep a naming convention from day one.
What do Catalogs add that Liquid alone does not?
Braze describes Catalogs as a data storage feature. The docs put the split plainly: the catalog is where the data is held, and Liquid is the language that pulls the relevant data out. You can think of a catalog as a large, shared table of items that your templates can read from.
The documented sources are imported files and API endpoints. The docs list use cases from seasonal product collections to back-in-stock notifications. For those, product information that includes inventory quantity is combined with Braze custom events to trigger a campaign or Canvas.
A release note dated 15 Oct 2026 adds that a catalog can be assigned to a Team. Users with Team-level permissions see and manage only their Team's catalogs.
In our experience the hard part of a catalog project is rarely the Liquid. It is deciding who owns the source file, how often it changes, and what happens to a message when an item is missing. Settle those three questions before the first import.
If the source data sits across several systems, that is a data question before it is a Braze question. CustomerIK's customer data management service covers CDP and pipeline integration and data governance.
How much catalog data can you store?
Storage is limited by the size of the catalog items, which may differ from the size of the files you upload. That distinction matters when you plan an import, so check item size and not file size.
The base version of catalogs allows up to 500 MB. Catalogs Pro offers storage options of 5 GB, 10 GB, 15 GB or 50 GB. Storage upgrades go through your Braze account manager, so raise the question early if your item data is large.
When do you need a Segment Extension?
Braze is direct about this: Segment Extensions are "an enhancement, not a requirement". A default segment can already use event properties from the past 30 days, or nested custom attributes, in real time. You need an extension only when the question reaches further back than that, up to the 730 days the docs describe.
Using event properties within Segment Extensions does not impact data point usage, so a long lookback does not add to it. Cost is a separate question. Each refresh of a SQL segment consumes SQL segment credits, and each refresh of a warehouse-backed extension incurs a cost in your own warehouse.
The guided Simple extension covers a single event without SQL. We would start there and move to SQL only when a question needs more than one event or table.
How do you schedule Segment Extension refreshes?
Refreshes can take up to 60 minutes because of data processing. The Braze docs give an example: for an email sent every Monday at 11 am company time, choose a weekly refresh at 10 am on Mondays. Work backwards from the send, not forwards from the build.
While an extension is processing, Braze keeps using the previous version of the segment. Refresh settings also switch off automatically for unused extensions. A workspace holds 50 active extensions by default, so retire the ones you no longer need.
What does a worked example look like?
This example is hypothetical and contains no client data. Imagine a retailer that wants to win back people who bought from one product category well over a year ago and have not bought since.
- Put the shared offer line and footer in a Content Block, inserted by Liquid, so the legal team edits one place.
- Import the product details into a catalog, so the message shows items from the category rather than hard-coded copy.
- Ask whether a default segment can answer the audience question. It cannot, because the docs describe default segments using event properties from the past 30 days, and these purchases sit well outside that.
- Build a Simple extension on the purchase event. The lookback sits comfortably inside the 730 days Braze documents.
- Set the refresh to land an hour before the campaign sends, so the audience is current when the send begins.
The order matters. The Content Block and the catalog exist before the segment goes live. The extension comes last because it carries a refresh schedule to manage, and SQL or warehouse-backed versions carry credit or warehouse costs.
How does this connect to the rest of the programme?
These features work best when the surrounding foundations are sound. Our guide to segmenting your audience in Braze covers the default segments that Segment Extensions build on. Clean event data matters just as much, which is why tracking user events comes before any long lookback.
For catalog-driven content, read Liquid tags for personalization and item recommendations. If your team is weighing automation next, using templates for marketing automation is the natural companion to Content Blocks. For the AI side of the platform, see which Braze AI features to adopt first.
As a Braze implementation partner, CustomerIK recommends adopting these three features in the order set out here: Content Blocks, then Catalogs, then Segment Extensions. Review the Braze documentation for current limits and entitlements before you plan, because storage options and quotas can change.
Frequently Asked Questions
1. Do I need Segment Extensions to use event properties in a segment?
No. The Braze docs say you do not need them to use event properties or nested custom attributes. Extensions extend the historic window used to create a default segment.
2. Does a change to a Content Block reach messages that are already live?
For blocks inserted through Liquid, yes. Braze documents that they are linked to the original and reflect its changes. Blocks added by drag and drop are not linked.
3. Can Content Blocks be nested?
Yes, but only once. Content in a third level does not expand, and the Liquid snippet is removed from the message.
4. How is catalog storage measured?
By the size of the catalog items, which may differ from the size of the files you uploaded.
5. How far back can a Segment Extension look?
Up to 730 days, which is two years of custom event or purchase event history.
Sources
- Braze, Segment Extensions. Retrieved 27 Oct 2026.
- Braze, Content Blocks. Retrieved 27 Oct 2026.
- Braze, Catalogs. Retrieved 27 Oct 2026.
- Braze, Release notes. Retrieved 27 Oct 2026.
- Written by CustomerIK, a Braze implementation partner.
CustomerIK is a Braze implementation partner working across onboarding, technical integration, marketing operations and customer data management.
If you are deciding which of these features to set up first in your workspace, let's talk.
.svg)
