Personalize one page for a known audience

Make an existing page speak to a need someone has already shared with you. You'll change its headline, supporting message, and button text for one audience. Everyone else keeps the original page, and a conversion goal helps you see what people do next.

Our example business, WorkForge (opens in a new tab), could tailor its homepage for visitors who answered "Coordinate my team" in a survey. You can use an on-site answer even when the visitor hasn't shared their email address.

1. Pick your page and audience

Choose a real page with RightMessage installed. Then choose an existing question or segment that identifies the people you want to speak to. For this example, use the Coordinate my team answer from your welcome survey.

If your segment uses email-platform or CRM data, the browser needs to be identified first. Connecting the integration alone isn't enough.

Write the copy you'd like this audience to see. WorkForge could use:

• A headline saying "Give every team handoff a clear owner".
• A supporting paragraph saying "Agree who owns the next step before work moves between people".
• Button text that describes the existing destination in terms of team work.

Keep the button destination, form, price, and offer terms unchanged. Visitors who don't match this audience should keep the original content. You don't need a separate audience for them.

2. Create the campaign

A campaign holds your page changes and the audience rules that decide who sees them.

1. Open Campaigns and choose New campaign.
2. Enter WorkForge team page in Campaign name.
3. In Which page should it personalize?, enter your actual page URL.
4. Under Create an audience for each segment in these groups, select your survey's group. Its segments start selected.
5. Deselect every answer except Coordinate my team. Check that Audiences to create lists the audience you want.
6. Choose Create campaign.

Enlarge

New campaign form with a homepage URL and Customer Lifecycle audiences selectedOriginalOriginal

The campaign editor opens inside RightMessage. Your campaign is saved to the draft, not published. Every audience needs at least one segment; an empty selection won't create a campaign.

3. Change the message

1. Choose Edit and select your team audience under its question or segment group in the left panel.
2. Click the headline on the page. Check that the highlight surrounds only the content you mean to change.
3. In the floating element editor, open Content. Use Replace all content and enter your new headline.
4. Open Pages. Check Target mode and the element's CSS selector. Check Domain, set Match to equals, and set Page path to the exact page you want to personalize.
5. Choose Done, then repeat for the supporting paragraph and button text. Leave the button's destination unchanged and check the page rule for each change.
6. Select Original page in the left panel to compare the unchanged website.

Enlarge

Campaign editor with the WorkForge homepage, audience list and Edit, Matrix and Preview modesOriginalOriginal

Your edits save to the draft automatically. Done closes the element editor; it doesn't publish. Wait for saving to finish and resolve any save error before leaving.

The selected audience's changes appear under On this page. Other changes lists its changes elsewhere or changes that can't be found on this page. Review those before you publish. The page targeting guide explains Smart Match, CSS selector, and page rules.

4. Check the audience and page

Choose Preview in the campaign editor. Use Preview as to select the team segment and check its copy. Then choose None for that group to check the original page. Your preview choices don't change the audience's rules.

Check the page at desktop and mobile widths. Look for long headlines, awkward button wrapping, and separate mobile elements that need their own changes.

If the editor shows Copy of your page, you can keep editing. Page loading troubleshooting explains the notice. You'll check the real website before publishing.

Enlarge

Preview as audience controls and the outlined personalized WorkForge headlineOriginalOriginal

5. Track the next step

Choose what you'd like visitors to do after reading the page. If a successful form submission sends people to a unique confirmation page, use that real page for a conversion goal.

1. Open Conversion Goals and choose New goal.
2. Under What should count as a conversion?, choose Page view.
3. Under Which pages?, select your domain and Path is, then enter the confirmation page's path without UTM parameters.
4. Enter a Goal name, such as Walkthrough confirmation page visited.
5. Under Measure it in these campaigns, select your campaign and choose Create goal.

Enlarge

New conversion goal form with page view, click, form submission and JavaScript event types and a historical match previewOriginalOriginal

Check that successful submissions reach the page and failed submissions don't. A page-view goal counts a visit, so someone who opens a public confirmation URL directly can count too. If you don't have a suitable page, use a supported Click or Form submission goal instead. Conversion goal setup explains those choices.

Open your campaign's Testing tab to review the holdback. New campaigns with audiences start with a 10% holdback, so some matching visitors see your page as it is. The holdback is included on Scale and Pro. Comparing personalization with a holdback explains how to keep or remove that comparison.

6. Preview it on your site

Choose Preview on your site in the dashboard's bottom bar. Use Choose preview URL to open the page you're changing. Your unpublished changes load on the actual website with the debugger docked at the bottom.

Check the team audience and the original page. Test text wrapping, button wording, destinations, and your form's validation and confirmation page. Use approved test submissions only.

Then remove forced audience choices and try the survey normally. Check the team answer, another answer, no answer, and a returning visit. Visit an unrelated page too, so you can confirm the changes stay on the intended page. If the audience uses CRM data, test the real identification path.

The debugger shows why an audience matches and lets you inspect holdback. Testing your changes covers those checks in detail.

7. Publish

Once you're happy with the page, confirm the campaign is enabled. Choose Publish and review all pending changes, including other campaigns, widgets, and flows.

Visit the published page without debugger overrides and repeat the matching and original-page checks. Confirm that the goal is published, attached, and records the next step you chose.

When your audience sees the matching message and other visitors keep the original, it's working. Next, use the campaign's Results tab to see how it's doing. Wait for real visits and conversions before judging whether the new copy helps.