Skip to main content
ACI preview gives reviewers a branch-specific view of saved content and its linked frontend code. Opening or refreshing a preview does not promote content, stage a release, or change the live site.

​
What a preview represents

A preview combines:
  • The current saved version of one content branch
  • The code build linked to that branch
  • The requested site route
  • The base experience or a selected personalization context
That pairing matters when content and code evolve together. A reviewer sees the component contracts and rendering implementation intended for the branch, rather than an unrelated production build.

​
Preview a branch

1

Save the content changes

Make sure the branch contains the version you want reviewers to see.
2

Link the intended code build

If the work depends on new or updated components, link the branch to the compatible code build before reviewing it.
3

Open the branch preview

Request the preview through your ACI workflow. ACI returns a branch-addressed preview URL and keeps the requested route in the URL.
4

Review representative routes

Check page content, shared fragments, navigation, responsive behavior, and any relevant base or personalized experiences.
5

Validate before landing

Resolve visual issues and compiler diagnostics before the branch is approved and landed.
A preview URL follows the branch state, so reviewers can refresh after new saved changes. If the linked code build changes, verify the branch again against that new pairing.

​
Preview and release are different checks

Preview supports review, but it is not a substitute for compilation. A release must pass the compiler even if its preview looked correct.

​
Isolation from the live site

Branch previews use a separate delivery path from the active release. They do not update main, live, or the active release, and they do not require a release activation. Treat preview URLs as review links and share them according to your organization’s access policy. Avoid using a preview URL as a production endpoint.

​
Common review cases

Content-only change

Preview updated copy or structure with the branch’s current linked code build.

Contract migration

Link the updated code build, fix incompatible content on the same branch, and review the combined result.

Shared fragment

Review several routes that reference the changed fragment, not only the page where the edit began.

Personalized experience

Review the base experience and each intended audience or experiment result before promotion.
Next: Personalization Architecture →