6.1 Visual Fragments vs Expression Fragments

Adobe Certified Professional - Adobe Journey Optimizer Business Practitioner AD0-E607

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Structure & Journey Fundamentals

1.1 AD0-E607 Exam Logistics, Scope, and Adobe Journey Optimizer Architecture 1.2 Journey Lifecycle States and Canvas Management 1.3 Unitary Journeys vs Business Journeys

2 Chapter 2: Journey Triggers & Event Modeling

2.1 Audience-Based Entry with Read Audience & Audience Qualification 2.2 Unitary Event Triggers & Schema Requirements 2.3 Business Events & Audience Broadcast Execution

3 Chapter 3: Journey Orchestration, Timing & Logic

3.1 Condition Activities and Branching Logic 3.2 Wait Activities and Timing Modulation 3.3 Action Nodes and the Jump Activity

4 Chapter 4: Journey Testing, Execution & Operational Reporting

4.1 Validation, Simulation, Test Mode, and Dry Run Execution 4.2 Live & All-Time Reporting Dashboards 4.3 Error Handling, Discards, and Operational Governance

5 Chapter 5: Multi-Channel Content Design & Personalization

5.1 The Email Designer & Multi-Channel Canvas Structure 5.2 Personalization Syntax & Expression Editor 5.3 In-App Messaging & Web In-Browser Delivery

6 Chapter 6: Reusable Assets, Fragments & Content Experiments

6.1 Visual Fragments vs Expression Fragments 6.2 Assets Essentials Management and Content Templates 6.3 Content Experimentation and Pre-Deployment Proofing

7 Chapter 7: XDM Schemas, Ingestion & Real-Time Customer Profiles

7.1 Experience Data Model (XDM) Foundations for Journey Optimizer 7.2 Datasets, Profile Enablement & Ingestion Troubleshooting 7.3 Real-Time Customer Profile & Profile Merge Policies

8 Chapter 8: Identity Resolution, Segmentation & Data Governance

8.1 Identity Service, Namespaces & Identity Graphs 8.2 Segmentation Methods: Streaming, Batch, Edge & Sequential Logic 8.3 Data Usage Labeling & Enforcement (DULE), Consent, and Privacy

9 Chapter 9: Decision Management, Offer Rules & Ranking Policies

9.1 Decision Management Architecture & Offer Library Components 9.2 Offer Eligibility Rules, Constraints & Capping 9.3 Decision Policies, Ranking & Channel Integration

6.1 Visual Fragments vs Expression Fragments

Key Takeaways Explain This Topic AI

Visual fragments reuse designed email content; expression fragments reuse personalization expressions.

Fragments must be published to become Live and available for production use.

Published fragment edits are synchronized to inheriting draft and live content after the new fragment version is published.

Breaking inheritance creates a local copy that no longer receives source-fragment changes; locked fragments prevent that break.

New personalized attributes cannot be added to an existing live fragment; duplicate it and update references when new attributes are required.

Last updated: October 2026

6.1 Visual and Expression Fragments

Content fragments let authors create once and reuse consistently. The two core types solve different problems.

Visual fragments

A visual fragment is a reusable designed content block for email, such as a header, legal footer, loyalty panel, or branded call-to-action. It contains layout and components authored through the Email Designer.

Use a visual fragment when appearance and structure should be standardized across messages. The fragment can be locked so downstream authors cannot break inheritance. It can also expose approved customizable fields so a marketer changes specific text, image, or button values while retaining the rest of the centrally managed block.

Expression fragments

An expression fragment stores reusable personalization logic or text expression. Examples include a governed greeting, loyalty-tier wording, or a localized legal phrase. It is created with the personalization editor and can be inserted where that fragment type is supported.

Expression fragments should remain focused. A long, highly contextual expression can be harder to test and may not be reusable. Contextual attributes are restricted in fragment workflows, so verify the attributes the editor makes available rather than assuming an event field can be saved into a reusable fragment.

Draft and Live

A new fragment begins in Draft. Publish it to make it Live and usable in production content. Publication requires the relevant permission.

When editing a live fragment, Journey Optimizer creates an editable draft version while the current live version remains active. The existing version continues to render until the updated fragment is published. After publication, changes are synchronized to content that still inherits from the fragment, including referenced draft or live journeys and campaigns.

This is controlled propagation—not an unsaved edit instantly changing production. Review references before publication so the team understands the impact.

Inheritance

When a visual fragment is inserted, it normally remains linked to its source. A published source update is propagated to linked uses. An author can break inheritance where allowed, turning that block into local standalone content. Later fragment updates no longer affect that copy.

A fragment author can lock the fragment to prevent consumers from detaching it. Locking is useful for brand, legal, or regulatory content. Customizable fragments provide a more controlled compromise: specified fields can vary without severing the source relationship.

Adding personalization fields

After publication, the set of personalized or contextual attributes in a live fragment is locked. You cannot simply add a new personalization field to that live fragment. The supported approach is to duplicate the fragment, add the required attribute to the duplicate, publish it, and update journeys, campaigns, or templates to reference the new fragment.

Removing an existing personalization field during an edit follows the documented workflow, but new dependencies need the duplicate-and-replace process. This protects live content from an incompatible attribute change.

Content fragments versus Journey Fragments

Do not confuse content fragments with Journey Fragments .

Content fragments reuse email design or personalization expressions and remain linked unless inheritance is broken.

Journey Fragments reuse a selected set of journey nodes. Inserting one creates a static copy of those nodes; later changes to the source Journey Fragment are not propagated into journeys that already used it.

The word “fragment” alone is therefore insufficient. Ask whether the scenario is reusing content or canvas activities.

Governance workflow

Choose visual or expression type.

Name, tag, and place the fragment in an appropriate folder.

Author and preview with representative data.

Decide whether it should be locked or offer customizable fields.

Publish and inspect references.

When modifying, review every dependent journey, campaign, and template.

Publish the new fragment version and verify representative live content.

For new attributes, duplicate and deliberately migrate references.

Example

A legal footer contains mandatory company text and an unsubscribe link. Create a locked visual fragment, test it in supported email layouts, publish it, and use it across templates. A later wording update is drafted and approved; the old version remains live until the update is published, after which linked content receives the change. A locally detached footer would not receive it, which is why locking may be appropriate.

Warning

Do not break inheritance for a quick local tweak without accepting ownership of future updates. Detached copies can silently miss legal or brand changes.