Review and publish project changes

Publishing makes your saved changes available to visitors. You'll review the whole project draft first, including changes to other items and edits from your collaborators. RightMessage publishes those pending changes together.

You need access to the project, and the project needs an active trial or plan. Every project gets its own 14-day trial when it's created, so you can publish while it runs. Install the project's snippet so visitors can receive its behavior. The public demo can't publish.

Check what's about to go live

1. Finish editing and let the draft save.
2. Choose the unpublished changes count in the bottom bar.
3. Expand each category to inspect its items. Use the change-type filters or Show more when the list is long.
4. Open any linked item that needs more work.

Enlarge

Publish bar with an unpublished conversion goal and the Publish buttonOriginalOriginal

The popover shows the autosave time when available. Filters only change the list you see. You can't select individual changes to publish.

If you'd rather return to an earlier setup, Roll back… opens Project Backups. Opening it doesn't discard your draft or change your live site.

Preview it on your site

1. Choose Preview on your site in the bottom bar.
2. To start on another page, open Choose preview URL beside it.
3. Select a suggested page, or choose Enter URL…, enter the full HTTP or HTTPS URL, and choose Open Preview.

Your real website opens with your unpublished changes and the debugger docked at the bottom. Check that Draft is selected. Preview requires an authorized session and isn't available until the tracking snippet is installed.

Follow testing your changes before returning to the dashboard. Try the real path visitors will take as well as any simulated audiences.

Review and describe your changes

1. Choose Publish in the bottom bar, or Review in the changes popover.
2. If a validation dialog appears, fix each listed issue and try again.
3. Expand the grouped changes and check the before-and-after fields. The heading includes the count, such as Publish 3 changes.
4. Read any plan warning before continuing.

Some features won't go live on your current plan means publication will exclude those features. Campaigns and conversion goals require Scale or Pro. If you intend those features to go live, choose Upgrade and resolve the plan requirement first. A successful publish of the rest of the project doesn't mean the excluded features were activated.

Read the Publish note and edit it to describe what you're changing. If it says Righty is drafting…, wait for the field to become editable.

For example, Show the agency headline on the homepage and update the assessment's final offer tells your team more than Updates.

Righty can draft this note, but publishing doesn't have to wait for it. If you publish while the note loads, or Righty's draft isn't available, RightMessage uses a change summary instead. The note is saved in publish history. Review the changes themselves, not just the note.

Go live

1. Choose Publish in the confirmation dialog.
2. If a billing screen appears, review its plan and billing terms before completing it. It appears when a payment needs attention or the project's billing setup didn't finish when it was created. Start 14-day trial & publish starts that project's trial and publishes your changes in one step.
3. Wait for the success message that your changes are live.
4. Choose Done.

Cancel closes the review without publishing. It leaves your saved draft edits in place.

Visitors receive the new setup on their next page view. Reload the page for your own check rather than checking a page that was already open.

If validation, billing, a save conflict, or a server error blocks you, see publishing troubleshooting.

Start any draft tests

Question, offer, and flow tests have a separate start action. If one is still in draft, the bottom bar shows test not yet started - Review and start.

Follow that link to review and start the test. Publishing doesn't choose Start test for you. Campaign holdback settings don't use this same separate test lifecycle.

Check it as a visitor

Open the intended entry URL without the debugger or forced segments. Use a fresh browser session for a new visitor and a dedicated test contact for an identified visitor.

Check that the page shows the right content, the flow follows the right path, and any contact update reaches your connected platform. Those checks tell you whether visitors qualify for your rules and whether the platform accepts their data.

If you need to reverse the release, restore an earlier version to the draft, review it, and publish the recovery.