Dynamic Content Blocks: Tiny Feature, Big “Wait… What?” Moment

Dynamic content blocks Feature is now available in Preview and can be enabled for use. It is one of the features that sound simple:

Create it once.
Use it everywhere.
Update it in one place.

Love that.

They are perfect for content that needs to stay consistent across multiple emails, like:

• footers
• disclaimers
• promotion banners
• reusable brand sections
• regional or product content

Static vs. Dynamic

Here is the quick way to think about it:

Static content block = copied into the email.
Dynamic content block = connected to the content block and updated from the source where the latest content is fetched when email is sent.

So if you want future updates to flow into emails automatically, the block needs to be added as dynamic.

The catch

Here is where it gets a little tricky.

You can update a content block from static to dynamic, but that does not mean every email that already used the static version will now update automatically.

Why?

Because when the block was added as static, the content was copied into the email. It is no longer truly connected to the content block for future updates.

So changing the block setting later does not magically reconnect those emails.

The confusing part

CI-Journeys may still show emails as “impacted” when you update the content block.

Helpful? Yes.
A little misleading? Also yes.

That list may show where the content block was used, but it does not guarantee the email will actually receive the updated content if the block was originally added as static.

I recommend creating a new dynamic content block and using it in the email, so you have a clear understanding which email/s will be truly impacted when the content block gets updated.

What to do

For any email that used the block as static and now needs dynamic updates:

1. Open the email.
2. Remove the static block.
3. Add the block again as dynamic.
4. Review and publish the email.

Takeaway

Dynamic content blocks are a great maintenance win — but only when the email is actually using the dynamic version.

So before you rely on the “impacted emails” list, double-check how the block was added.

Because in CI-Journeys, “listed as impacted” does not always mean “updated automatically.”

And that, my friends, is the part worth knowing before your next content update.