Ridgetop

Guides

Switch to Ridgetop guides

Move your tours, feature tags, checklists and survey history over a few weeks, without a gap. Both tools can run on the same pages while you switch; Ridgetop's guides wait while the other tool shows one, so customers never see two at once.

Switching from Pendo

Pendo's feature tags and CSS rules work in Ridgetop as written, including :contains(). Guides are rebuilt in the designer, and NPS history comes over by CSV.

What moves, and how

Feature tags and page rules
Paste each rule into a new feature under Analytics › Features, or tag the element again in the designer. Rules with :contains() work unchanged, and past clicks count as soon as the tag is saved.
Guide anchors
Paste the guide's element rule into the step's element in the designer's Custom CSS tab.
NPS and poll history
Download each guide's poll responses as CSV in Pendo, then use Import past scores on the matching Ridgetop survey's Results tab.
Segments
Rebuild them as audience rules on the guide's Targeting tab, using the same user and account properties sent with Ridgetop.boot.
Guide content and styling
Rebuild in the designer. Set your brand once as a theme, so each guide doesn't need styling.
Resource Center
Arrange the Messenger home under Settings › Customer messenger › Home & meetings, and list tours under Take a tour.

Run both while you move

Turn on Pendo under Guides › Settings › Running alongside another tool. While a Pendo guide is on screen, Ridgetop's guides wait, so the two never stack.

The install checker on the Installation tab notices Pendo's script and reminds you.

Rebuild guides

Open the designer on your app from Guides › Design on your site. Start a guide on the page where the Pendo guide runs, and for each step pick the same element, or paste Pendo's rule into Custom CSS.

Use the matching panel's click history to check the rule matches as many clicks as it did in Pendo.

Give each guide a goal on its Goal tab, so you can compare completion and impact with what Pendo showed.

Your team's checklist

  1. Install the Ridgetop Messenger snippet on the pages your current tool covers, using the Messenger installation guide.
  2. Add your staging website under Guides › Settings, so you can publish to staging first.
  3. Turn on side-by-side mode for Pendo.
  4. Recreate your most-used feature tags under Analytics › Features, pasting Pendo's rules.
  5. Rebuild your live guides in the designer, starting with onboarding.
  6. Recreate segments as audience rules.
  7. Import NPS and poll history from Pendo's CSV exports.
  8. Arrange the Messenger home to replace the Resource Center.
  9. Publish rebuilt guides to production one area of the product at a time, and pause the old tool's version as each one goes live.
  10. After two weeks of matching numbers, turn off side-by-side mode and remove the old tool's script.

Switching from Intercom

Intercom doesn't let product tours or checklists be exported, so they're rebuilt in the designer. Survey answers come over by CSV, and conversations already live in Ridgetop's inbox.

What moves, and how

Product tours
Rebuild in the designer. Elements marked with data-intercom-target can be matched with a rule like [data-intercom-target='Export'].
Checklists
Rebuild as a Ridgetop checklist, with tasks completed from events, properties or pages rather than by hand.
Survey and NPS answers
Export responses from Intercom's survey report (the answer_combined CSV), then use Import past scores on the matching Ridgetop survey.
Banners and posts
Recreate as banner guides, or as posts in the Messenger's Updates tab.
Messenger home
Arrange the Messenger home and greeting per audience under Settings › Customer messenger.

Run both while you move

Turn on Intercom under Guides › Settings › Running alongside another tool. While an Intercom tour or banner shows, Ridgetop's guides wait.

If you keep Intercom's Messenger running for a while, leave Ridgetop's launcher hidden on those pages until you switch.

Rebuild tours and checklists

Intercom's API can trigger a tour but not read one, so there's nothing to import. Open each tour in Intercom beside Ridgetop's designer and rebuild it step by step.

Use your data-intercom-target attributes as element rules; they're stable and read well.

Your team's checklist

  1. Install the Ridgetop Messenger snippet on the pages your current tool covers, using the Messenger installation guide.
  2. Add your staging website under Guides › Settings, so you can publish to staging first.
  3. Turn on side-by-side mode for Intercom.
  4. List your live tours, checklists, banners and surveys in Intercom.
  5. Rebuild tours in the designer, using data-intercom-target attributes as element rules.
  6. Rebuild checklists with automatic completion.
  7. Import survey history from Intercom's CSV export.
  8. Arrange the Messenger home and greetings for visitors and signed-in customers.
  9. Publish rebuilt guides to production one area of the product at a time, and pause the old tool's version as each one goes live.
  10. After two weeks of matching numbers, turn off side-by-side mode and remove the old tool's script.

Switching from Appcues

Appcues flows are rebuilt in the designer, using the same CSS selectors. Checklists and NPS history carry over by hand and by CSV.

What moves, and how

Flows and pins
Rebuild in the designer, pasting each step's CSS selector into the element's Custom CSS tab.
Checklists
Recreate each checklist's items as tasks: an item that opens a flow becomes a task that starts the matching guide.
Click-to-track events
Paste the selector into a new feature under Analytics › Features; past clicks count straight away.
NPS history
Export NPS from Appcues Studio (not the Basic export), then use Import past scores on the matching Ridgetop survey.

Run both while you move

Turn on Appcues under Guides › Settings › Running alongside another tool. While an Appcues flow is on screen, Ridgetop's guides wait.

Your team's checklist

  1. Install the Ridgetop Messenger snippet on the pages your current tool covers, using the Messenger installation guide.
  2. Add your staging website under Guides › Settings, so you can publish to staging first.
  3. Turn on side-by-side mode for Appcues.
  4. Recreate click-to-track events as features.
  5. Rebuild flows and pins in the designer.
  6. Recreate checklists, linking tasks to the rebuilt guides.
  7. Import NPS history from Appcues' CSV export.
  8. Publish rebuilt guides to production one area of the product at a time, and pause the old tool's version as each one goes live.
  9. After two weeks of matching numbers, turn off side-by-side mode and remove the old tool's script.

Start with the Messenger installation guide; guides load with it.