# Analyze performance
Source: https://docs.navattic.com/analyze/index

Understand the performance of your product demos and visitor behavior.

<Icon icon="chart-no-axes-column-increasing" /> **Analyze** the performance of your product demos to
understand what's working and double down on your visitors are most interested in.

Navattic offers demo and visitor-level engagement insights via the Analytics and Visitors tabs. Additionally, within each Product Demo, users can access Flow completion rates under the Activity tab. To send Navattic data to another platform or your marketing website, visit [Integrations](/integrations).

## Product Demo Analyze tab

The <Icon icon="chart-no-axes-column-increasing" /> **Analyze tab** for each demo contains this specific demo's Visitors and Step completion rates. Click into a Visitor to view details about their form submissions and the actions they have taken throughout your demo and examine which steps visitors are dropping off at under **Step breakdown**.

<Frame>
  <img alt="Analyze tab" />
</Frame>

If your demo contains video steps, you can see playback analytics below the step breakdown chart. The chart shows the number of views for every 5-second interval of the video. Visitors who re-watch portions of the video will be counted multiple times.

<Frame>
  <img alt="Video playback analytics" />
</Frame>

<br />

<MediaCard title="Analyze tab" />

**If you identify a step with greater drop-off than others:**

* Investigate the appearance of the step: Could customers be confused by the text or other elements at this step?
* Consider adding a CTA before this step to engage viewers before they exit the demo
* Let us know - our team is happy to provide tailored guidance for your demo!

## Analytics Dashboard

The <Icon icon="chart-no-axes-column-increasing" /> **Analytics Dashboard** is a way to understand the performance of all your demos across the workspace.

<Frame>
  <img alt="Analytics Dashboard" />
</Frame>

<br />

<MediaCard title="Analyze dashboard" type="video" />

#### Metric definitions

Use this to identify changes over time that may correspond with marketing initiatives. For example, did your click-through rate increase singificantly due to a seasonal campaign?

Use Filters to see the following metrics for a particular Product Demo or Timeframe.

| Metric                     | Description                                                                                                                                         |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Unique visitors**        | The total number of visitors to step 1 of your demo                                                                                                 |
| **Engaged visitors**       | Unique visitors who advance 1+ steps in your demo                                                                                                   |
| **Engagement rate**        | The percentage of unique visitors who advance 1+ steps in your demo (engaged visitors ÷ unique visitors)                                            |
| **Identification rate**    | The percentage of unique visitors whose identity (name or email) was captured during their session                                                  |
| **CTA clicks**             | The total number of visitor engagements with a CTA in your demo (we recommend adding CTAs at [these conversion points](/build/flows#click-actions)) |
| **Time spent per session** | How long the average user spends on a browser tab containing your demo                                                                              |
| **Click-through rate**     | The total number of times a Visitor clicked a CTA on the demos divided by the total number of engage events.                                        |
| **Steps viewed**           | The total number of demo steps viewed across your workspace                                                                                         |

## Pipeline Impact

The <Icon icon="chart-no-axes-column-increasing" /> **Pipeline Impact** dashboard provides visibility into how your demos influence pipeline and revenue, connecting demo engagement to business outcomes through CRM integration.

<Frame>
  <img alt="Pipeline Impact Dashboard" />
</Frame>

<Frame>
  <img alt="Top Accounts Impacted by Demos" />
</Frame>

#### Metric definitions

Use the Pipeline Impact dashboard to understand how demo engagement translates to pipeline creation and revenue impact. Filter by date range to see metrics for a specific time period.

| Metric                               | Description                                                                                                                                                             |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Total Accounts**                   | Counts unique accounts that have viewed any demos within the selected date range.                                                                                       |
| **Total Engaged Accounts**           | Counts accounts that have advanced past the first step of a demo or engaged with a checklist.                                                                           |
| **Total Converted Accounts**         | Counts accounts that have interacted with a CTA within the demo.                                                                                                        |
| **Sourced Pipeline**\*               | Shows opportunities where the account's first demo view occurred before the opportunity was created.                                                                    |
| **New Accounts Sourced**\*           | Counts CRM accounts that were created after the contact's first demo view.                                                                                              |
| **Engaged Leads**\*                  | Counts individual contacts who have viewed demos. Breaks down into "sourced" (demo before contact creation) vs "influenced" (demo after).                               |
| **Influenced Pipeline**\*            | Shows opportunities where a demo view occurred at any point during the deal cycle.                                                                                      |
| **Total Revenue Impacted**\*         | Time-series line chart showing pipeline value over the selected date range. Plots Total Revenue, New Pipeline (sourced), and Influenced Pipeline.                       |
| **Value with Demos**\*               | Shows the dollar value of influenced pipeline as a percentage of total impacted pipeline.                                                                               |
| **Top Accounts Impacted by Demos**\* | Table showing the top 10 accounts sorted by deal value where demos had impact. Displays account name, deal value, deal stage, and whether it was "new" or "influenced". |

<Note>
  \* These metrics require a connected CRM. If Pipeline Impact or Sales Impact shows a **Connect your CRM** prompt, use the dropdown to select <img alt="Salesforce Logo" /> [Salesforce](/integrations/salesforce) or <img alt="HubSpot Logo" /> [HubSpot](/integrations/hubspot) and follow the setup steps in your workspace settings.
</Note>

## Compare Product Demo Analytics

To compare the Analytics of two Product Demos, visit **Analytics** > **Compare** > **Product demos** > Select demo 1 and Select demo 2. You can also adjust the time period you would like to view using the calendar drop down. One of your demos will have a blue dot and one will have a gray dot next to the title which is the graph key.

### View Highest Performing Demos

To identify your highest-performing demos in Analytics, visit the Analytics tab and select **Compare** > **Highest Performing Demos** from the dropdown menu to view your top five demos for each section.

### A/B Testing

<Info>
  A/B Testing is available on the **Base** plan and above.
</Info>

<Icon icon="split" /> **A/B testing** allows you to compare two different demo variations to determine which one performs better with your audience. By splitting traffic between two demos, you can make data-driven decisions about which demo experiences resonate most with visitors.

#### Creating an A/B Test

To create an A/B test:

1. Navigate to **Settings** in your workspace
2. Select **A/B Tests** from the settings menu
3. Click **Create test**
4. Select your two demo variations:
   * **Demo A**: Choose your first demo variation
   * **Demo B**: Choose your second demo variation
5. Configure your traffic split using the slider
   * Adjust the percentage of visitors who will see each demo
   * The split must total 100% (e.g., 50% Demo A, 50% Demo B)
6. Click **Create** to generate your A/B test

<Note>
  You must select two different demos for your A/B test. Each demo should represent a distinct variation you want to test.
</Note>

#### Sharing Your A/B Test

Once you create an A/B test, Navattic generates a unique link that automatically routes visitors to the appropriate demo variation:

1. From the A/B Tests list, click the **link icon** or select **Copy Link** from the menu
2. Copy the provided URL
3. Share this link on your website, in emails, or anywhere you want to run the test

<Tip>
  The link format is: `https://[your-domain]/split/[test-id]`. This single link handles all traffic routing automatically.
</Tip>

#### Analyzing A/B Test Results

View your A/B test performance by clicking **Analyze** on any test:

1. Navigate to **Analytics** in your workspace
2. Select your A/B test from the comparison options
3. Review key metrics for both demo variations:
   * View counts
   * Engagement rates
   * Completion rates
   * Time spent in demo
   * Form submissions
   * Any custom metrics you track

The analytics view displays metrics side-by-side, making it easy to identify which demo variation performs better.

## Visitor Data and CSV Exports

The **Visitors page** within Navattic contains a full list of all users who have engaged with your demos. Identified visitors will include their name and email (if provided via a Navattic form or query strings); anonymous visitors will be assigned an unique ID that is tied to their browser profile.

<MediaCard title="Visitor Analytics" />

<img alt="" />

**Engagement Details** for each visitor includes all the demos they have engaged with. Visitors who viewed multiple demos or conducted multiple sessions will have all their information consolidated here.

**Conversion Events** indicate that a visitor "Navigated to URL", or clicked a CTA that redirected them outside of your demo.

**From the Visitors tab, you can also:**

* **Sort** the table by clicking any column header. Click again to reverse the sort order.
* **Filter** Visitors by Engagement, Demos, Flows, or Emails (if using Forms).
* **Export** a .CSV file of your 5,000 most-recent visitors. For Visitors who have completed multiple Flows, Navattic will export the most-recently completed Flow or Demo to avoid creating duplicate records.

<Note>
  Tip: Explore our [Integrations](/integrations) to send Visitor data to other tools like Slack,
  Salesforce, Hubspot, Marketo, and more.
</Note>

<Info>
  Read the Blog: [5 Ways to Get More out of Your Interactive Demo
  Data](https://www.navattic.com/blog/interactive-demo-data)
</Info>

### FAQs

<AccordionGroup>
  <Accordion title="How do I track converted Visitors in Navattic?">
    First, add a' ' ["Mark as Converted"](/build#A_TJC)' ' click action to the primary CTA button in
    your demo. Next, visit your Navattic Workspace > **Visitors** > **Filters** > Events:
    **Converted**. If you only want to see converted Visitors for a specific demo, you can also add
    a Product Demo Filter.
  </Accordion>

  <Accordion title="How do I see the total number of Visitors for a Demo?">
    From your Visitors tab, Filter by your Product Demo name to see only the Visitors who have
    engaged with this Demo.
  </Accordion>

  <Accordion title="How do I separate Product Demo Analytics for different embeds or links?">
    There are several ways to separate engagement data if you are using the same demo in multiple
    places. **Our recommendation** is to create [different share links](/product-updates#k7xAg) for
    your product demo and to view the /path in your CSV export.
  </Accordion>

  <Accordion title="Do demos with or without Forms see more user engagement?">
    Form-gated demos may see a higher % of conversion events, as viewers who complete a Form are
    oftentimes higher-intent. However, we have found ungated demos had about on average 12% higher
    completion and 5% higher engagement rates.
  </Accordion>

  <Accordion title="Why are there a lot of Step 1 views?">
    If your demo is embedded as an iFrame on a high-traffic landing page **and** does not include a
    third-party form, each website visitor is "loading" the first step of your demo. In this case,
    Step 1 views represent each time your webpage has been loaded and may include users who do not
    click into your demo; for ungated embedded demos, Step 2 views would provide a better
    representation for how many users have interacted with each Demo.
  </Accordion>

  <Accordion title="Why are there more Views for later steps?">
    Within the Product Demo page, each step view represents a time that page has been loaded. If a
    user refreshes a particular step of your demo, this will count this as two views. If present,
    this discrepancy is usually small.
  </Accordion>

  <Accordion title="How do I add UTMs to an embedded demo?">
    To track UTMs for Visitors to an embedded demo, add your UTMs to the **end of the src link** in
    your Navattic Website Embed code (the highlighted section below). Note that Navattic does not
    pull UTMs from the top frame of the page for embedded demos.
  </Accordion>

  <Accordion title="How can I configure my Navattic form to accept only business/work emails?">
    To ensure visitors enter their work email in a Navattic form, navigate to the Form > Select
    **Email** > form field to open the settings > toggle on **Require work email**.
  </Accordion>
</AccordionGroup>


# Media captures
Source: https://docs.navattic.com/build/captures/media

Images, videos, and GIFs of your desktop or mobile app.

<Frame>
  <img alt="Media Capture Editor" />
</Frame>

Navattic makes it easy to create demos of Desktop or Mobile native apps by uploading any screenshots, videos or GIFS you already have.

## Taking Media Captures

Follow these instructions for taking media captures across different platforms:

<Tabs>
  <Tab title="Capturing">
    The **Navattic Capture Extension** can be used to <Icon icon="aperture" /> **Capture** screenshots and video of any application that can be opened in a browser. When capturing with the extension, select `Screenshot` or `Video`.
  </Tab>

  <Tab title="Uploading media">
    If you already have screenshots, videos or GIFS, of your application, you can <Icon icon="upload" /> **Upload** them to Navattic. When creating a demo, select `Uploading media` and drag and drop the files from your computer.
  </Tab>

  <Tab title="Desktop">
    If your application can be opened in a browser, use the <a href="/build/captures/media#capturing"><Icon icon="aperture" />Capture</a> method instead.

    For applications that can only be accessed as a native desktop app, use the [Navattic Desktop app](#desktop-capture). Download links and setup instructions are in the Desktop Capture section below.
  </Tab>

  <Tab title="Figma">
    To use Figma designs as media captures, export them as PNG files and upload them to Navattic.

    <Steps>
      <Step title="Export your frames">
        In Figma Design, select the frames you want to export. Go to **File** > **Export**, choose **PNG** as the format, and click **Export**. See [Figma's export guide](https://help.figma.com/hc/en-us/articles/360040028114-Export-from-Figma-Design) for full details.
      </Step>

      <Step title="Upload to Navattic">
        When creating a new demo, select **Upload media** and drag and drop the exported PNG files from your computer.
      </Step>
    </Steps>
  </Tab>

  <Tab title="iPhone">
    Follow these instructions for [taking a screenshot of your iPhone app](https://support.apple.com/en-us/102616)

    on your mobile device. After you've taken all of the screenshots, send them to your desktop computer and add them to a folder. When creating a new demo, select `Upload media`,  and drag and drop the screenshots from the folder.
  </Tab>

  <Tab title="Android">
    Follow these instructions for [taking a screenshot or recording of your Android app](https://support.google.com/android/answer/9075928) on your mobile device. After you've taken all of the screenshots, send them to your desktop computer and add them to a folder. When creating a new demo, select `Upload media`,  and drag and drop the screenshots from the folder.
  </Tab>
</Tabs>

## Desktop Capture

The **Navattic Desktop app** lets you capture screenshots of applications that can't be opened in a browser, including native Windows and macOS apps.

Download the app for your platform:

| Platform            | Download                                                                                         |
| ------------------- | ------------------------------------------------------------------------------------------------ |
| Mac (Apple Silicon) | [Navattic.dmg](https://downloads.navattic.com/desktop/production/arm64/Navattic.dmg)             |
| Mac (Intel)         | [Navattic.dmg](https://downloads.navattic.com/desktop/production/x64/Navattic.dmg)               |
| Windows             | [Navattic Setup.exe](https://downloads.navattic.com/desktop/production/x64/Navattic%20Setup.exe) |

After installing, open the app and sign in with your Navattic account. Choose a capture mode:

* **Display** — captures your full screen
* **Window** — hover over a window to highlight it, then click to confirm your selection
* **Area** — drag to define a capture region on your screen
* **Device** — captures a connected iOS or Android device via a screen mirroring app

Click **Start recording**, then click through your application. Each click captures a screenshot. When done, click **Stop recording** in the floating toolbar — your captures are automatically saved to a new project in your Navattic workspace.

### Recovering missing captures

If a capture session fails to start, screenshots and recordings may be saved to a temporary folder without being uploaded. You can recover these files from the app's Troubleshooting screen.

<Steps>
  <Step title="Open Settings">
    In the Desktop app, click the settings icon to open **Settings**.
  </Step>

  <Step title="Open Troubleshooting">
    Click **Troubleshooting** at the bottom of the Settings screen.
  </Step>

  <Step title="Recover your captures">
    The **Recover missing captures** tool shows how many files are waiting. Click **Recover** to upload them.
  </Step>

  <Step title="View your demo">
    If recovery succeeds, the captures open automatically in your browser as a new demo.
  </Step>
</Steps>

<Note>
  Click the refresh icon next to the file count to re-check for missing captures at any time.
</Note>

## Edit Media Captures

**Media Captures** can be edited to tell the perfect story for your demo. Open a **Media Capture** and click `Edit` to open the **Media Capture Editor**.

The **Media Capture Editor** gives you controls for editing any of the following:

<Tabs>
  <Tab title="Device Frames">
    Display your demo inside a realistic <Icon icon="monitor-smartphone" /> **Device frame**, such as a **Mobile**, **Desktop**, or **Tablet**, to match the application's platform. This helps visitors imagine using your product on their own device and adds visual polish. You can also switch orientations and device types to best suit the flow of your demo.

    <Info>
      See how Mobile Device Frames look in action by viewing [Calm's demo](https://info.calm.com/WR-Calm-Partner-Portal-Tour.html).
    </Info>

    For the best results, use images that match the aspect ratio of the device frame you plan to use. Images that don't match will either be letterboxed or require scrolling.

    **Mobile frames (portrait)**

    | Device frame            | Recommended aspect ratio |
    | ----------------------- | ------------------------ |
    | Apple iPhone 16 Pro Max | 9:19.5                   |
    | Apple iPhone 16 Pro     | 9:19.5                   |
    | Apple iPhone 11 Pro Max | 9:19.5                   |
    | Samsung Galaxy S25      | 9:20                     |
    | Samsung Galaxy S9       | 9:18.5                   |
    | Google Pixel 9          | 9:19.5                   |
    | Google Pixel 3          | 9:18                     |
    | Nexus 6P                | 9:16                     |

    **Tablet frames (portrait)**

    | Device frame       | Recommended aspect ratio |
    | ------------------ | ------------------------ |
    | Apple iPad Pro 13  | 3:4                      |
    | Apple iPad Silver  | 3:4                      |
    | Samsung Galaxy Tab | 2:3                      |

    **Desktop frames**

    | Device frame      | Recommended aspect ratio |
    | ----------------- | ------------------------ |
    | Apple iMac Pro    | 16:9                     |
    | Apple iMac Retina | 16:9                     |
    | Apple MacBook Pro | 16:10                    |
    | Dell XPS 13       | 16:9                     |
    | PC Laptop 15      | 16:9                     |

    <Note>
      The plain **Mobile**, **Tablet**, and **Desktop** shadow frames scale to fill the available space and don't require a specific aspect ratio.
    </Note>
  </Tab>

  <Tab title="Background">
    Set a custom background color behind your capture to match your brand or make your demo stand out. This is especially useful when embedding your demo on a webpage where the background should blend seamlessly. Consistent branding helps keep the viewing experience professional and cohesive.
  </Tab>

  <Tab title="Edit">
    Use blur, crop, or draw tools to clean up and annotate your capture. This allows you to hide sensitive data, focus attention on specific areas, or add callouts for clarity. Quick edits like these make your demo look polished without leaving the editor.
  </Tab>

  <Tab title="Scroll">
    Lock vertical or horizontal scrolling to control how viewers navigate your demo. This ensures users focus on the intended content without accidentally moving off-screen. It's especially useful when demonstrating fixed interfaces or static layouts.
  </Tab>

  <Tab title="Accessibility">
    Add alt-text that make your demo usable for all viewers, including those with assistive technologies. Accessibility settings ensure your content is readable, navigable, and inclusive.
  </Tab>
</Tabs>

## Video Editor

For video captures, Navattic includes a built-in **Video Editor** that lets you trim and crop your footage before it's added to your demo -- no external tools required.

To open the Video Editor, upload a video file and click **Edit** before finalizing the upload. You can trim and crop in any order, then save when you're ready.

### Trim

Trimming lets you cut out the beginning or end of a video so your demo starts and ends exactly where you want.

The **timeline** at the bottom of the editor shows your full video along with an audio waveform. Use the **drag handles** on either end of the timeline to set your trim points -- everything outside the handles will be removed. As you drag, the timestamp display updates to reflect your current position within the trimmed range.

Use these controls to navigate and fine-tune your trim:

* **Play/Pause** -- Preview your video to find the right cut points
* **Mute/Unmute** -- Toggle audio while previewing
* **Zoom slider** -- Zoom the timeline from 1x up to 4x for more precise control over short clips

The red **playhead** shows where the video is currently playing. Hover over the timeline to see a gray indicator that helps you preview a position before clicking.

### Crop

Cropping lets you define a specific region of the video frame to keep, removing any surrounding areas you don't want to show.

To enter crop mode, click the <Icon icon="crop" /> **Crop** button in the playback controls. A crop overlay with drag handles will appear over the video preview. Drag the handles to adjust the crop area. The current dimensions are shown in pixels as you resize.

Use the **aspect ratio** dropdown to constrain your crop to a common format:

| Preset     | Ratio                                 |
| ---------- | ------------------------------------- |
| Freeform   | No constraint                         |
| Original   | Matches the video's native dimensions |
| Widescreen | 16:9                                  |
| Fullscreen | 4:3                                   |
| Square     | 1:1                                   |
| Vertical   | 9:16                                  |

When you're satisfied with the crop area, click **Apply** to confirm. To exit crop mode without making changes, click **Discard**.

### Saving your edits

Once you've finished trimming and cropping, click **Save** to apply your edits. The edited video replaces the original and is ready to use in your demo.

<Info>
  Trim and crop are applied together when you save. You can adjust either at any point before clicking Save.
</Info>

## Video capture controls

Video captures can be a good option for showcasing dynamic content, such as animations or user interactions like drag-and-drop.

Select **Video options** from the Capture dropdown in the Demo Builder, or select **Advanced** on a Video capture in the Flow builder to control the following settings:

<Tabs>
  <Tab title="Auto play">
    <Icon icon="circle-play" /> **Auto play** your video capture when a viewer lands on the step. This creates a smooth, immediate viewing experience without requiring the user to click play.

    <Info>
      If the video capture is on the first step, audio will not play until the visitor has interacted with the demo (such as clicking or scrolling) due to browser restrictions.
    </Info>
  </Tab>

  <Tab title="Playback controls">
    Use <Icon icon="film" /> **Playback controls** to display standard video controls like play, pause, and mute so viewers can control their own pace.
  </Tab>

  <Tab title="Audio">
    Enable or disable <Icon icon="volume-2" /> **Audio** for your video capture. Enabling audio can add context and personality to your walkthrough, while disabling it ensures the focus stays on visuals—especially in quiet or public settings.
  </Tab>

  <Tab title="Loop video">
    Enable **Loop** to automatically restart the video when it finishes.
  </Tab>
</Tabs>

#### Example Media capture demos

<CardGroup>
  <Card title="Slack Mobile App Demo" href="https://capture.navattic.com/cl6waudcn05060hl29tm4rcrq" />

  <Card title="SwipedOn Employee App" href="https://swipedon.navattic.com/product-tour-2023" />

  <Card title="Duolingo" href="https://emily-staging.navattic.com/2910rr4" />
</CardGroup>

#### FAQ

<AccordionGroup>
  <Accordion title="Can I add device borders to a screenshot?">
    Navattic includes mobile, tablet, and desktop borders for Apple and non-Apple devices. Adding a device border helps end users best visualize your desktop or mobile application. Learn more about' ' [adding a device border](/captures#M2cYM) to a media capture.
  </Accordion>

  <Accordion title="Can I use a PDF in my demo?">
    Yes, to add a PDF to your demo, you'll have to convert the file to a .PNG or .JPEG file before uploading it as a Media Capture. We recommend using this free online converter: [https://www.freeconvert.com/pdf-converter/download](https://www.freeconvert.com/pdf-converter/download).

    [Watch a 1-minute tutorial](https://www.loom.com/share/3aee01f369764ab0837901fb455ee6c9?sid=00576aa6-1538-4791-beaf-75e1cab15659) on converting and uploading PDFs in Navattic.
  </Accordion>

  <Accordion title="How can I get my screenshot to better fit the device borders?">
    Using [device mode](https://developer.chrome.com/docs/devtools/device-mode) in Google Chrome paired with a [tool like this](https://chromewebstore.google.com/detail/gofullpage-full-page-scre/fdpohaocaechififmbbbbbknoalclacl) , you are able to take screenshots that better fit with the device borders.
  </Accordion>

  <Accordion title="Can I edit a media capture using the Capture Editor?">
    No. Navattic does not currently support image editing. We recommend using a tool like Figma or Adobe to make modifications prior to uploading.
  </Accordion>

  <Accordion title="What are the best practices for uploading media to Navattic?">
    Follow these guidelines to get the best results when uploading images or videos to Navattic:

    **Resolution**

    Use images with a width of at least 1200px. Images narrower than this will appear blurry at full size. For retina or high-DPI screens, aim for 2x your target display size (e.g., 2400px wide for a 1200px display slot).

    **Aspect ratio**

    Match your image's aspect ratio to the device frame you plan to use. Mismatched ratios result in letterboxing (black bars) or require visitors to scroll. Common ratios by device type:

    | Device type                 | Recommended aspect ratio |
    | --------------------------- | ------------------------ |
    | Desktop (16:9)              | 16:9                     |
    | Desktop (MacBook Pro frame) | 16:10                    |
    | Desktop (other frames)      | 3:2                      |
    | Mobile (portrait)           | 9:19.5                   |
    | Tablet (portrait)           | 3:4                      |

    An easy way to export at the right ratio is to create a Google Slides deck set to the target dimensions and place your screenshots in each slide, then export as PNG.

    **Video**

    For video uploads, use MP4 or WebM format. The built-in Video Editor lets you trim and crop footage after uploading, so you can clean up extra content without needing an external tool.
  </Accordion>

  <Accordion title="How do I avoid the need to scroll when using a device border?">
    Match your image's aspect ratio to the device frame before uploading. For example, the Desktop border uses a 3:2 ratio — screenshots that don't match this ratio will require scrolling inside the frame.

    One approach: create a Google Slides deck set to the same ratio as your target device border, add your screenshots to each slide, and export as PNG. See the FAQ above for a full list of aspect ratios by device type.
  </Accordion>
</AccordionGroup>


# Personalizing captures
Source: https://docs.navattic.com/build/captures/personalization

Customize text, images, colors, and styles in captures using custom properties.

Capture personalization lets you make parts of a demo dynamic — replacing text, images, colors, or styles with values specific to each viewer. You configure personalization in the capture editor, and the values are supplied when you share the demo through a share link or presentation.

<Note>
  Personalization requires custom properties to be configured in your workspace first. Go to **Settings > Custom properties** to set them up. The property type you need depends on what you are personalizing.
</Note>

## Types of personalization

You can personalize four types of elements in a capture:

| Type      | What it changes                                                   | Custom property type |
| --------- | ----------------------------------------------------------------- | -------------------- |
| **Text**  | Any text element in the capture                                   | String               |
| **Image** | Any image element in the capture                                  | Image                |
| **Color** | Color CSS properties (background color, text color, border color) | Color                |
| **Style** | Non-color CSS properties (font size, padding, border radius)      | String               |

## Personalizing text

<Steps>
  <Step title="Open the capture editor">
    From your demo, open the capture you want to personalize.
  </Step>

  <Step title="Select a text element">
    Click the text element you want to personalize. In the **Magic Editors** panel, open **Personalization**.
  </Step>

  <Step title="Add a variable">
    Click **Add personalization** and select a custom property from the list. You can optionally set a fallback value — text that appears when no variable is supplied for a visitor.
  </Step>

  <Step title="Apply to the collection (optional)">
    To apply the same personalization to matching elements across all captures in the collection, check **Replace all instances** before saving.
  </Step>
</Steps>

## Personalizing images

Image personalization replaces any image element with a custom image you supply per account or audience. It uses custom properties of the **Image** type.

<Note>
  Images for personalization are uploaded manually — Navattic does not automatically fetch logos or images from a company name or domain. If you want to personalize a company logo automatically from a domain or visitor email, use the built-in **Company Logo** property instead. See [Personalized demos](/demos/personalized) for details.
</Note>

<Steps>
  <Step title="Open the capture editor">
    Open the capture that contains the image you want to personalize.
  </Step>

  <Step title="Select the image element">
    Click the image you want to replace. In the **Magic Editors** panel, open **Personalization**.
  </Step>

  <Step title="Choose an image-type custom property">
    Click **Add personalization**. Only custom properties of the **Image** type appear here. Select the property you want to use.
  </Step>

  <Step title="Set a fallback image">
    Upload a fallback image. This is shown to visitors when no custom image variable is provided for their session.
  </Step>

  <Step title="Apply to the collection (optional)">
    Check **Replace all instances** to apply the same personalization setup to matching image elements across the capture collection.
  </Step>
</Steps>

## Personalizing colors

Color personalization lets you swap the colors of elements in a capture — such as background colors, text colors, or border colors — using a Color-type custom property. This is the recommended way to apply a customer's brand colors to a demo.

<MediaCard title="Color personalization demo" />

<Note>
  Color personalization requires at least one custom property of the **Color** type. Go to **Settings > Custom properties** and create a new property with the type set to **Color**. You can set a fallback hex color that is shown when no value is supplied.
</Note>

<Steps>
  <Step title="Select an element in the capture editor">
    Click the element whose color you want to personalize.
  </Step>

  <Step title="Open Style personalization">
    In the **Magic Editors** panel, open **Personalization**, then select **Style**.
  </Step>

  <Step title="Choose a color CSS property">
    Select the CSS property you want to change — for example, **background-color**, **color**, or **border-color**.
  </Step>

  <Step title="Select a Color custom property">
    Choose a Color-type custom property from the list. Only Color-type properties are available for color CSS properties. If none appear, create one in **Settings > Custom properties**.
  </Step>
</Steps>

When you share the demo, recipients with a matching color value see their brand color applied across all personalized elements.

## Personalizing styles

Style personalization lets you change non-color CSS properties — such as font size, padding, or border radius — using String custom property values.

<Steps>
  <Step title="Select an element in the capture editor">
    Click the element whose style you want to personalize.
  </Step>

  <Step title="Open Style personalization">
    In the **Magic Editors** panel, open **Personalization**, then select **Style**.
  </Step>

  <Step title="Configure the style rule">
    Choose the CSS property to change (for example, **font-size** or **border-radius**), then select a String-type custom property that will supply the value. Set a fallback value for when no variable is provided.
  </Step>
</Steps>

## Fallback behavior

Every personalization field should have a fallback. If a visitor accesses a demo without a personalization variable being supplied — for example, via an unparameterized link — the fallback value is shown instead.

* **Text fallback** — Plain text displayed in place of the variable
* **Image fallback** — A default image uploaded to Navattic
* **Style fallback** — A default CSS value (e.g., a hex color)

Without a fallback, the element may appear blank or unstyled for visitors who don't receive a personalized value.

## Sharing personalized demos

Once captures are personalized, you supply values when creating a share link or presentation in Launchpad.

<Steps>
  <Step title="Open Share link settings">
    From your demo, go to **Share link settings** (or create a new share link in Launchpad).
  </Step>

  <Step title="Enter personalization values">
    Fill in the custom property values for the recipient — for example, their company name, logo, or brand color.
  </Step>

  <Step title="Share the link">
    The link is now personalized for that recipient. You can create separate links for different accounts, each with their own values.
  </Step>
</Steps>

## Troubleshooting

**The personalized value isn't appearing**

Check that:

* A custom property value was supplied when creating the share link.
* The correct custom property is assigned to the element in the capture editor.
* A fallback is set — if no value is supplied and no fallback exists, the element may appear empty.

**I can't find an image-type custom property in the list**

Image personalization only shows custom properties of the **Image** type. If none appear, go to **Settings > Custom properties** and create a new property with the type set to **Image**.

**My style personalization isn't applying**

Confirm that the fallback value is a valid CSS value for the property you selected (for example, a valid hex code for a color property). Invalid fallback values may cause the style to appear unstyled.

**I can't find a Color custom property when personalizing a color CSS property**

Color CSS properties (background-color, color, border-color) only accept Color-type custom properties. If none appear in the list, go to **Settings > Custom properties** and create a new property with the type set to **Color**.


# Capture Troubleshooting
Source: https://docs.navattic.com/build/captures/troubleshooting

Tips and solutions for working with web captures

Please follow these steps to resolve any issues:

1. Check that the [Navattic Chrome Extension](https://chromewebstore.google.com/detail/navattic/lbecioncobbndebbfdopnpinnibemoon) is updated. You may have to remove and re-add it to force update it.
2. Follow [these instructions](https://support.google.com/chrome/answer/95414?hl=en\&co=GENIE.Platform%3DDesktop) to check that your Chrome browser is updated.
3. After updating the Chrome extension and your browser, please try to re-take the Captures.
4. If the issue persists after updating everything, please toggle on the Advanced Settings of the Chrome extension one at a time and try to take Captures. The Advanced Settings can be found by clicking the Chrome extension > Select Settings > Advanced.
5. If you are still experiencing an issue after testing the Advanced Settings, please email [support@navattic.com](mailto:support@navattic.com), message us in the In-App chat, or report an issue within the Capture Editor.

### FAQs

Below are resolutions to a variety of Capture FAQs. If these instructions do not resolve your problem, please email [support@navattic.com](mailto:support@navattic.com) or message us in the In-App chat and include a link to the broken Capture. Alternatively, you can create an issue report directly from the Capture Editor.

<AccordionGroup>
  <Accordion title="Floating Dropdown">
    If you notice that a dropdown is floating around depending on your screen size, you can either use the **Fit Width** responsive strategy or manually tether the dropdown with the Capture Editor. To tether a dropdown to an element, open up the Capture Editor > Select the entire Dropdown > Select **Magic Editors** > Click **Tether** > Click **Tether to Element** > Select the element the Dropdown should be attached to. From here, you can customize the dropdown's position and click **Save & Exit**.

    <MediaCard type="video" title="Web Capture Technical Guide" />
  </Accordion>

  <Accordion title="Missing Stylesheets or Inconsistent Formatting">
    If you notice that your Capture is missing a stylesheet when you preview it, it is possible that the Capture was taken with an outdated version of the [Navattic Chrome Extension](https://chromewebstore.google.com/detail/navattic/lbecioncobbndebbfdopnpinnibemoon) and/or Chrome browser. Please update your Chrome extension (you may have to remove and re-add it to force update it) and browser before taking the Captures again. If this does not resolve the issue, please email [support@navattic.com](mailto:support@navattic.com) and include a link to the broken Capture or create an issue report from the Capture Editor.
  </Accordion>

  <Accordion title="The page won't load before taking a Capture">
    If you notice that your website won't load with the Navattic Chrome extension, please try toggling on **Disable HTML Patch** in the Advanced Settings of the Navattic Chrome extension. The Advanced Settings can be found by clicking the Chrome extension > Select Settings in the top right > Advanced.If this does not resolve the issue, please email [support@navattic.com](mailto:support@navattic.com) and share a screen recording of the issue. Additionally, if possible, please give our team access to your product's environment or a similar environment where you are taking these captures.
  </Accordion>

  <Accordion title="Popup won't load">
    If your website has a popup window that won't load with the Navattic Chrome extension, please try toggling on **Popup Window** in the Advanced Settings of the Chrome Extension. The Advanced Settings can be found by clicking the Chrome extension > Select Settings in the top right > Advanced.If this does not resolve the issue, please email [support@navattic.com](mailto:support@navattic.com) and share a screen recording. Additionally, if possible, please give our team access to your product's environment or a similar environment where you are taking these captures.
  </Accordion>

  <Accordion title="Unable to select the correct element">
    The element selector uses the same HTML element groups as the original application, so you might not be able to select specific elements. Instead, we recommend using [Beacons](/flows#YRzY6) to bring attention to specific areas of your application.
  </Accordion>

  <Accordion title="Can't edit the text behind the dropdown or popup">
    If you cannot edit elements behind a dropdown menu or popup/modal, it may be because there is an Overlay. You can remove the Overlay using the Capture Editor by selecting the element > Click Magic Editors > Overlay > Remove Overlay.If an Overlay is detected, you will often see a "Remove Overlay" message in the Capture Editor. You may have to remove multiple Overlays to reach the element you'd like to edit.

    <MediaCard type="video" title="Web Capture Technical Guide" />
  </Accordion>

  <Accordion title="Captures look different depending on the screen size">
    If your Captures look different on varying screen sizes, we suggest using the **Fit Width** Responsive strategy. Learn more about [Responsive Strategies](/build/responsive).

    <Note>
      If you are embedding your demo, we also recommend using the \*\*Fit Width \*\*Responsive Strategy.
    </Note>
  </Accordion>

  <Accordion title="Missing image or need to update an image">
    If you notice that an image wasn't captured or you want to update an image, you can use the Capture Editor to replace the image. To replace an image, open the Capture Editor > Select the image you want to replace > Click **Upload Image** > Select an image from your local storage > Click **Save & Exit.** If the image is part of the background, you can select the empty element and use the Background feature to upload the image.

    <MediaCard type="demo" title="Web Capture Technical Guide" />
  </Accordion>
</AccordionGroup>


# Web captures
Source: https://docs.navattic.com/build/captures/web

Interactive copies of your application.

<img alt="" />

Captures are interactive copies of your application that set the foundation for your demo. Navattic supports two types of Captures to help you demo any app:

1. **Web Captures** are HTML-based copies of any application that is accessed on a browser. This provides an interactive experience that looks and feels just like your app, including scrolling abilities, hover states, and more. Web App captures may be edited using Navattic's no-code HTML editor.
2. **Media Captures** are most often used to create demos of Mobile or Desktop native apps. Images, .GIFs, or Videos can be used for just a few steps or your entire demo.

<MediaCard title="Web and Media Captures example" />

<MediaCard type="video" title="Capture Tutorial" />

Web Captures are HTML-based copies of any application that is accessed on a browser. This provides an interactive experience that includes scrolling abilities, hover states, and more. Web App captures may be edited using Navattic's no-code HTML editor.

<Steps>
  <Step title="Take Captures">
    Follow the in-app prompt to [install the Navattic chrome extension](https://chrome.google.com/webstore/detail/navattic/lbecioncobbndebbfdopnpinnibemoon) if needed. Visit Product Demos > \*\*\*\* **Create demo**. Select **Creating new captures** and enter your **App URL**. Click **Start Capturing.**

    If you are working in an existing demo, visit the **Captures** tab > click **New Collection** > select **Start Capturing** > Enter in the name for the collection and add your App URL > click **Start capturing.**

    <img />

    This will open a new tab containing your application as well as the Navattic extension.

    Take Captures using these three steps:

    1. Click **Capture** to save the contents onscreen
    2. Once the Capture finishes loading, navigate to the next page and repeat the process
    3. Click **Finish** > Begin building demo to return to view your completed Capture Collection

    Captures within your Collection appear like this. Now you are ready to generate a Flow!

    <Frame>
      <img alt="" />
    </Frame>

    <Note>
      **Tip: Navattic introduced the ability to Click to Capture**. This is an option to automatically Capture the content on each screen, in order to save time while building your Flow. Click to Capture is best used for demos that primarily use Tooltips, Beacons, or Triggers.
    </Note>

    **Keeping captures consistent when adding to an existing collection**

    When you add captures to an existing collection, Navattic checks whether your browser viewport matches the dimensions already saved for that collection. If they don't match, a **"Resize to match collection?"** notification appears in the capture bar. Click **Resize** to automatically adjust your browser window — the tooltip shows the exact size change (for example, `1325x819 → 1512x288`). The prompt is shown once per session and dismisses automatically after you take your first capture.

    You can also set or update a collection's default dimensions manually. Open the collection, click **Edit collection details**, and enter your preferred **Width** and **Height** values. When you're capturing into that collection later, a **Collection** preset button appears in the viewport sizing panel so you can quickly resize to match.
  </Step>

  <Step title="Add Captures to a Flow">
    Flows combine Captures with dialog boxes to tell a story about your product. From your Capture collection, click **Generate flow**. This will automatically arrange Captures in the order in which they were taken.

    This video demonstrates how to create a flow and the different step types within the Flow builder.

    <MediaCard title="Captures" type="video" />
  </Step>

  <Step title="Edit Captures (optional)">
    The Navattic Capture Editor is used to make no-code adjustments to HTML-based captures. You may launch the Editor in two ways:

    1. From within a **Capture Collection**, click on any Capture and select "Edit"
    2. From the **Flow Builder**, click on any Capture as it appears in a Step and select "Edit"

    <button>Try a demo</button>

    When the Capture Editor launches, select any element to view the various editing options in the sidebar. Use the **element traversal arrows** demonstrated below to select elements with precision.

    <Expandable title="preview">
      <img />
    </Expandable>

    <Warning>
      While the Capture Editor is an effective way to change the visual appearance of captures, please be careful not to include sensitive information when taking captures.
    </Warning>

    ### Edit Text

    Replace or reformat text anywhere in your Captures. From the Capture Editor > select any text field > type within the Text / HTML container in the upper right or directly in the Capture.

    <Expandable title="preview">
      <img alt="" />
    </Expandable>

    ### Change Element Appearance

    Blur, Hide, or Delete elements in your Capture to provide the cleanest demo environment.

    <Expandable title="preview">
      <img alt="" />
    </Expandable>

    ### Replace Images

    Replace a profile image or icon to customize your Captures. You can also use the **Background** feature to replace background images.

    You can also use **Edit with Copilot** to modify images using AI prompts directly within the editor.

    <Expandable title="preview">
      <img alt="" />
    </Expandable>

    ### Lock Element Scrolling

    To limit the scrolling abilities of an element, select the element > Scroll > lock Vertical or Horizontal scroll.

    <Expandable title="preview">
      <img alt="" />
    </Expandable>

    ### Copy/Paste Elements within a Capture

    Copy and paste a similar element in your Capture. You can also copy similar elements across different Captures.

    <Expandable title="preview">
      <img alt="" />
    </Expandable>

    ### Magic Editor

    The Magic Editor is a powerful suite of tools that allow you to make advanced, dynamic edits to your captures. From personalizing content to animating text, these features help you create more engaging and realistic interactive demos without needing to write any code.

    <Expandable title="Personalization">
      Personalization allows you to insert user attributes, like a name or company, that are dynamically populated for each visitor viewing your demo. This makes every demo feel unique and relevant to the viewer. Learn more about [identifying Visitors](/tracking/identify/visitors).

      <iframe title="Loom video player" />
    </Expandable>

    <Expandable title="Dynamic Embed">
      This tool lets you insert an iframe into your capture that will fetch and display content from an external source.
    </Expandable>

    <Expandable title="Up-to-date">
      The Up-to-date feature automatically finds dates in your Capture and keeps them fresh relative to the current day.

      <iframe title="Loom video player" />
    </Expandable>

    <Expandable title="Tether">
      Tether locks the position of one element relative to another. This is useful for elements like dropdown menus or pop-ups that should move with their parent element when the user scrolls.

      <iframe title="Loom video player" />
    </Expandable>

    <Expandable title="Overlay">
      The Overlay feature lets you see and edit content that is hidden behind an overlay, such as a pop-up modal or a dropdown menu.

      <iframe title="Loom video player" />
    </Expandable>

    <Expandable title="Find & Replace">
      Find & Replace allows you to quickly replace all instances of a specific word, phrase, or image across an entire capture, saving you from having to make manual edits one by one.

      <iframe title="Loom video player" />
    </Expandable>

    <Expandable title="Table AI">
      Table AI uses artificial intelligence to edit the content within your tables. Simply write a prompt describing the changes you want, and the AI will update the table for you.

      <iframe title="Loom video player" />
    </Expandable>

    <Expandable title="Animating Text">
      Animating Text creates a "typing" animation for any text element, making your demo feel more dynamic and alive.

      <iframe title="Loom video player" />
    </Expandable>

    <Expandable title="Scroll Sync">
      Scroll Sync links two scrollable elements together, so that when a user scrolls one, the other scrolls with it. This is perfect for side-by-side panels or tables that need to stay aligned.
    </Expandable>

    <Expandable title="Force Hover">
      Force Hover keeps hover-triggered UI elements (such as dropdown menus or tooltips) visible by locking them in a hover state. Use this when you need to capture or edit content that only appears on hover and would otherwise disappear when you move your cursor away to make edits.
    </Expandable>
  </Step>
</Steps>

## Collection edits

Collection edits let you apply a change you've made to one capture across all matching captures in the same collection — without having to repeat the edit manually on each one.

When you save changes in the capture editor, the **Save** button offers two options:

* **Save** — Apply changes to this capture only.
* **Save and review collection edit** — Save this capture, then review which other captures in the collection match your changes before applying them.

Choosing **Save and review** opens a confirmation screen that shows how many other captures match. Click **Review changes** to see each matching capture side-by-side. You can toggle individual captures on or off, then click **Apply to N captures** to apply the edit only to the ones you've selected.

If no other captures match, the screen notes that the edit applies only to the current capture.

## Capturing multiple flows in one session

During a capture session, you can record screens for multiple flows without stopping and restarting. This lets you build all the flows for a demo in one go.

### Starting a new flow

While capturing, click **New flow** in the capture bar to begin a new flow. Give the flow a name and continue capturing. A badge on the capture list marks which flow is currently active, and a notification appears each time a new flow starts.

<Note>
  Keep each flow focused on a single topic or user journey. A notification appears in the capture bar if a flow has too many captures — split the content into a new flow to keep your demos easy to follow.
</Note>

### Reviewing and finishing the session

When you're done capturing all flows, click **Complete session**. A review screen shows every flow you recorded. You can rename any flow before finalizing. Click **Create** to save all flows at once and return to the demo builder.

<Note>
  For Navattic Agent environments, multi-flow capture is always on — every capture session creates flows that feed directly into the environment's flow list.
</Note>

#### FAQs

<AccordionGroup>
  <Accordion title="How do I capture a dropdown or popup menu?">
    If you are having trouble capturing an onscreen element, try using the keyboard command Ctrl+C (or Command+C for Mac) to take the capture.
  </Accordion>

  <Accordion title="How do I edit a Capture after adding it to a Flow?">
    From the Flow Builder, locate the Capture you would like to edit > click the arrows icon to expand the Capture > click "Edit". Save & Exit when complete. Keep in mind that your edits will be applied to every step that references this Capture (to avoid applying edits to every step with this Capture, first duplicate the Capture you are editing).
  </Accordion>

  <Accordion title="How do I edit the background of a Capture when a popup message or modal is present?">
    In the capture editor, use the up and down arrows to select the background element > open **Magic Editors** > **Overlay** > **Ignore Overlay.** You may have to remove the Overlay on a few different layers before being able to access the element you are hoping to edit.
  </Accordion>

  <Accordion title="How do I edit text in my Captures?">
    **First, please never capture sensitive data**. While the Capture Editor can be used to quickly replace simple strings of text or to alter the appearance of distracting elements, we ask our customers to avoid capturing sensitive data altogether.

    To edit non-sensitive text, open the Capture Editor > select your text field > and type something new in the Text / HTML box. Most text fields are easily accessible in the Editor; [this tutorial](https://www.loom.com/share/33f5904569434c319480e683e8108bee) shows you a workaround if you are having trouble selecting a given "text" field.
  </Accordion>

  <Accordion title="How can I add an image as the background of a captured element?">
    To add an image to the background of a captured element (a DIV, NAV, or other non-IMG element type), open the Capture Editor > Select the element where you want to add the image > **Background** > **Upload image** > Upload the image from your local storage. Use the **Position**, **Size**, and \*\*Repeat \*\*dropdowns to adjust the image if needed.
  </Accordion>

  <Accordion title="Can I capture an app running locally or in a staging environment?">
    In most cases, yes. Captures are taken from whatever page is open in your browser tab, so any
    environment you can load — a local dev server (for example, `localhost:3000`), a staging URL, or
    a page behind your login — can typically be captured the same way as a production site.

    * **Web Captures:** Open your local or staging app in the browser, then run the
      [Navattic Chrome extension](/build/captures/web) against it. If the extension doesn't activate,
      confirm it has permission for that domain — set it to "On all sites" or add the specific host
      (see "I am unable to load the Chrome Extension" below).
    * **Media Captures:** Take screenshots or a screen recording of your local build and
      [upload them as media](/build/captures/media).

    Because captures are static copies, a locally captured screen keeps working in your demo even
    after you take the local server down.

    <Warning>
      Local and staging environments often contain test or sensitive data. Review every capture and
      blur, hide, or delete anything that shouldn't ship in a demo before publishing.
    </Warning>
  </Accordion>

  <Accordion title="Which browsers does the Navattic extension support?">
    The Navattic extension works in Google Chrome and most Chromium-based browsers, including Microsoft Edge, Brave, and Opera.

    Some Chromium-based browsers require you to enable extensions from the Chrome Web Store before installing:

    * **Microsoft Edge**: Go to **Settings** > **Extensions** > **Manage extensions**, then toggle on **Allow extensions from other stores**.
    * **Brave**: Go to **Settings** > **Extensions** and enable **Allow extensions from the Chrome Web Store**.
    * **Opera**: Go to **Extensions** > **Manage extensions**, then click **Allow from other stores** when prompted.

    Once enabled, install the extension from the [Chrome Web Store](https://chrome.google.com/webstore/detail/navattic/lbecioncobbndebbfdopnpinnibemoon) as you normally would.
  </Accordion>

  <Accordion title="I am unable to load the Navattic extension.">
    When you start capturing a new domain, the Navattic extension automatically requests permission to access that site. A browser dialog appears — click **Allow** to grant access. Once access is granted, the extension activates on that page and the capture session begins.

    If the permission dialog does not appear, or you previously declined it, you can grant access manually:

    1. Click the Navattic icon in the extension bar. If it's not visible, click the puzzle icon and select it from the dropdown (click the pin to add it to the extension bar).
    2. Open the **This Can Read and Change Site Data** tab.
    3. Select the appropriate sites.
    4. Refresh app.navattic.com and any pages where you want to run the extension.

       <img alt="" />
  </Accordion>
</AccordionGroup>


# Checklist demos
Source: https://docs.navattic.com/build/checklist

Learn how to create and use Checklists in your demos.

<Frame>
  <img alt="Checklist" />
</Frame>

<Icon icon="list-checks" /> **Checklists** are great for organizing multiple flows from a demo into a series of tasks. This enables the visitor to decide which flow to engage with next at any time.

## Creating a checklist demo

Follow these steps to create your first demo with a Checklist:

<Steps>
  <Step title="Create a Checklist">
    Within your demo's **Build** tab, select **+Element** > **Checklist** to get started. Most Checklists will incorporate 4-6 Tasks that start different Flows. When using a Checklist, we recommend keeping individual Flows to 5-9 steps each.
  </Step>

  <Step title="Select either floating or sidebar">
    Checklists are automatically displayed using the **Floating** layout, which includes the Checklist launcher. The Checklist can be opened by clicking the Checklist Launcher, using the **Launch after flow start** Setting, or through various buttons, beacons, or triggers configured with the **Open Checklist** action.

    Alternatively, you can choose the **Sidebar** Layout, where the checklist stays open permanently on the side of your demo, providing continuous access throughout.
  </Step>

  <Step title="Add a title and tasks">
    A blank checklist will appear with the option to add a title, description (optional), and various Tasks. Tasks are the individual components of a Checklist, which appear when the Checklist is expanded. Similar to how Buttons behave in a Flow, Tasks in a Checklist can support a variety of Click Actions.

    | Click Action                   | Description                                                                                                    |
    | ------------------------------ | -------------------------------------------------------------------------------------------------------------- |
    | **Start a Flow** (most common) | Link the task to a Flow in your demo. Select from any Flows within your demo.                                  |
    | **Navigate to URL**            | Takes the end user to an external link (e.g., a Knowledge Base or Sign-up page)                                |
    | **Mark as Converted**          | For reporting purposes (i.e., not visible to the end user), this indicates that an end user has clicked a CTA. |
  </Step>

  <Step title="Edit the Launcher (optional)">
    Within the Checklist Settings, you can edit the **Checklist launcher value** to change the text. You can further customize the Launcher in [Themes](/build/themes).
  </Step>

  <Step title="Configure behavior (Optional)">
    Add a Progress bar, estimated completion time, a Checklist logo and/or Remaining count under Advanced in the Checklist builder.
  </Step>

  <Step title="Add CTA button(s) (Optional)">
    Add CTA button(s) to your Checklist by clicking **+ Add CTA button**. Then, enter the URL and optionally edit the text.
  </Step>

  <Step title="Edit settings (optional)">
    From the Checklist editor, click **Settings** to view additional options. Here, you can add a Backdrop, determine whether you would like the checklist to launch automatically upon Flow start or Flow completion, and select to reset it each time the demo is loaded.
  </Step>

  <Step title="Opening the Checklist from a Flow (optional)">
    Once a checklist has been created and associated with a demo, you can choose how you want a user to engage with it.

    **Launch Checklist After Flow Start**

    If you want a user to see the checklist immediately, you will use the **Launch after flow start** option found in the Checklist Settings.

    **Expand Checklist Action**

    Add **Expand Checklist** to any Beacon, Trigger, or Button in your flow to prompt a Checklist to open at a specific point in your demo, including after the last step. **Expand Checklist** can be paired with any condition, including a [Timer Trigger](/flows#JJQON).

    **Start Hidden Setting & Show Checklist Action**

    If you want to hide your Checklist before a user reaches a certain point in the demo, visit your Checklist Settings > Toggle on **Start hidden under Behavior.** Once this is toggled on, visit the Flow with the Form > locate the Form Step > add the **Show checklist** action to "When form is submitted."

    <Info>
      Pair the **Start hidden** Checklist Setting and **Show Checklist** action with your Form step to prevent Visitors from navigating through the Checklist before submitting the Form.
    </Info>
  </Step>
</Steps>

### FAQs

<AccordionGroup>
  <Accordion title="How do I make a Checklist appear for the viewer?">
    While viewers can manually expand at any point, you can also add an action to any Beacon, Trigger, or Button in your flow to prompt a Checklist to open automatically at a certain point, including after the last step. **Expand Checklist** can be paired with any condition, including **Timer**.

    <img alt={true} />
  </Accordion>

  <Accordion title="How do I adjust the appearance of my Checklist?">
    Visit [Themes](/build/themes) to adjust the appearance of your Checklist. Common adjustments may be:

    * Adjust the shape and size of your Checklist Launcher
    * Change the color of the checkmark
  </Accordion>

  <Accordion title="How do I view the Checklist created?">
    The Checklist will appear in your demo's **Build** tab. You can also preview the checklist when previewing the flow.
  </Accordion>

  <Accordion title="How do I move my Checklist to the left or right of the screen?">
    To move the Checklist position, hover over the Checklist in the\*\* Build\*\* tab, click on\*\* Reposition\*\*, and drag it to the one side.
  </Accordion>

  <Accordion title="How do I reset my progress in a Checklist?">
    When testing a Product Demo that contains a Checklist, you may notice that the Checklist tasks are already completed or include a strikethrough. This is due to your browser caching each previously completed step of the demo.

    To restart your Checklist each time, visit your Checklist Settings > **Always reset completed tasks**.

    <img />
  </Accordion>

  <Accordion title="How do I hide my Checklist until after a Form is submitted?">
    To prevent Visitors from skipping the Form by using the Checklist, visit your Checklist > Settings > Toggle on **Start hidden**.

    Once this is toggled on, visit the Flow with the Form > locate the Form Step > add the **Show checklist** action to **When form is submitted**.

    <img alt="Checklist Demos 10 Pn" title="Checklist Demos 10 Pn" />
  </Accordion>
</AccordionGroup>


# Build your first demo
Source: https://docs.navattic.com/build/demo

Learn how to build your first demo with Navattic.

<Frame>
  <img alt="Demo page" />
</Frame>

Empower your teams to share and deliver top-performing demos with confidence. To do that, first create and organize your best demos so that your team knows what to look for. Follow the video or the steps below to prepare the demos in your workspace:

<MediaCard type="video" title="Build a demo" />

<Steps>
  <Step title="Create a demo">
    Click `+ Create demo` on the <Icon icon="layout-grid" /> [Product demos page](https://app.navattic.com/w/product-demos).

    Enter the **URL** of the app that you'd like to demo - you'll be taking captures of it next.

    Enable <Icon icon="sparkle" /> **Copilot** to have your demo be generated from the captures that you take.

    <img alt="Create demo" />
  </Step>

  <Step title="Take captures">
    Your app will open in a new tab. Click through your key pages of your app to take captures. Captures are interactive copies of your application.

    Learn more about <Icon icon="app-window" /> [Captures](/build/captures/web).

    <img alt="Capture app" />

    <Tip>
      We recommend taking **10-15 captures** for your first demo. Focus on showing off key aha-moments of your app.
    </Tip>
  </Step>

  <Step title="Generate a demo">
    Click the `Finish` button on the floating Capture bar when you are done taking 10-15 captures.

    If you selected Copilot, your demo will be automatically generated from your captures.

    <img alt="Copilot generating" />

    Once your demo is generated, you can click through the steps to preview it - it's ready for review!
  </Step>

  <Step title="Make edits">
    Click on the `Edit` button in the top right corner to make any adjustments to the demo.

    Clicking on Edit will take you to the **Build** tab. Click on any of the generated flows to open the Flow builder and make copy or style changes to the demo. Learn more about [building flows](/build/flows).

    <img alt="Create demo" />
  </Step>

  <Step title="Publish your demo">
    After you're done making edits, click the `Publish` button in the top right corner to publish your changes. Click publish anytime that you want your changes to be live on the public version.

    <img alt="Publish button" />
  </Step>
</Steps>

<Icon icon="party-popper" /> **Congratulations** -- you've finished building your first
<Icon icon="layout-grid" /> **product demo** and it's ready to share! Follow the steps below to
learn how and where to use your new demo.

## Next steps

### Sharing your demo

Use cases can help you decide when and where to share a demo in your customer journey. Reviewing common patterns can make it easier to tailor your approach for different teams or workflows.

Embedding demos makes it easy for visitors to interact with your product directly on your marketing website. Follow the steps below to add a demo onto your website.

<CardGroup>
  <Card icon="building-2" title="Use cases" href="/use-cases">
    Tips and best practices for sharing demos.
  </Card>

  <Card title="Embed your demo" icon="panels-top-left" href="/share/embed">
    Embed your demo on your marketing website or product.
  </Card>
</CardGroup>

### Building advanced demos

Take your demos to the next level by building purpose-built demos for each use case.

<CardGroup>
  <Card title="Personalized demos" icon="user-pen" href="/demos/personalized">
    Make demos personalized by adding user and account variables
  </Card>

  <Card title="Mobile demos" icon="tablet-smartphone" href="/build/mobile">
    Showcase your mobile app in a demo.
  </Card>

  <Card title="Multilingual demos" icon="languages" href="/demos/multilingual">
    Support multiple languages in your demos.
  </Card>

  <Card title="Interest demos" icon="square-check-big" href="/demos/interest">
    Unlock a powerful insight - what features prospects are interested in seeing.
  </Card>

  <Card title="Offline demos" icon="wifi-off" href="/demos/offline">
    Use your demos offline at tradeshows and conferences.
  </Card>
</CardGroup>


# Demo builder
Source: https://docs.navattic.com/build/demo-builder

Create and edit interactive demos in the Demo builder.

<Note>
  If you don't have access, email [success@navattic.com](mailto:success@navattic.com) to enable the Demo builder in your workspace.
</Note>

<Frame>
  <img alt="Demo Builder interface" />
</Frame>

The Demo builder is a single interface for editing, managing, and analyzing your demos.

<MediaCard type="demo" title="Explore the Demo builder" />

<MediaCard type="video" title="Demo builder walkthrough" />

## Understanding the layout

When you open the Demo builder, there are four main areas:

### Main navigation tabs

At the top of the page, you can switch between three tabs:

<Frame>
  <img alt="Build, Manage, and Analyze tabs" />
</Frame>

* **Build** - Design your interactive demo with steps, tooltips, and media
* **Manage** - Configure sharing settings, organize flows, publish your demo, and access version history
* **Analyze** - Track visitor engagement, completion rates, and performance

### Flows list sidebar

On the left side of the Build tab, you'll find a list of all the Flows and steps in your demo. Click on any step in any Flow to edit it in the main canvas.

<Frame>
  <img alt="Flows list sidebar" />
</Frame>

You can resize the sidebar by dragging its right edge. Drag it all the way to the left to collapse it. The **Add flow** button is pinned to the bottom of the sidebar.

### Step editor

The central area where you edit the content, appearance, and behavior of a selected step.

### Theme panel

On the right, you can adjust the look and feel of your demo by applying and customizing themes. Changes here apply across your entire demo.

### Preview

Switch to the Preview tab at any time to see how your demo will appear to viewers. Your latest changes are always reflected in the preview.

## Switch builder layout

The Demo builder offers two layouts for editing. Switch between them using the toggle in the top navigation, or press <kbd>Shift</kbd> + <kbd>.</kbd> to toggle from the keyboard.

<Frame>
  <img alt="Demo builder layout" />
</Frame>

<Tabs>
  <Tab title="Single step view">
    The default view, designed for editing one step at a time. It works with the Flows list sidebar, so you can focus on a single step while navigating to any other step in your demo.

    **When to use single step view:**

    * You want to focus on individual steps
    * You need to jump between steps across different Flows
    * You're making detailed edits to specific elements

    <Tip>
      Single step view is ideal for making quick edits across your demo. Use the Flows list sidebar to navigate between steps.
    </Tip>
  </Tab>

  <Tab title="Multi-step view">
    The classic Flow builder layout, available as multi-step view. This mode shows the entire sequence of a single Flow at once, making it easier to understand the narrative arc of your demo.

    **When to use multi-step view:**

    * You want to see the full story of a Flow from start to finish
    * You're reordering or reorganizing steps within a Flow
    * You prefer the classic Flow builder experience

    <Note>
      Multi-step view focuses on one Flow at a time. To edit steps in different Flows, you'll need to switch between them.
    </Note>
  </Tab>
</Tabs>

## What you can edit

The Demo builder provides a unified experience for building Flows. You can edit the following directly in the **Build** tab:

* <Icon icon="list-checks" /> Checklist builder
* <Icon icon="move-diagonal" /> Responsiveness settings
* <Icon icon="languages" /> Language and tracking settings
* <Icon icon="palette" /> Themes

<Note>
  Version history is accessible from any tab. Open the options menu in the top navigation bar and select **Version history**.
</Note>

## Reordering buttons

In the Build tab, you can change the order of buttons within a step by dragging them. Click and hold the drag handle to the left of any button, then move it up or down to reposition it. The new order is saved automatically.

## Deleting a demo

Once archived, to permanently delete a demo, open the demo in the Demo builder and select **Delete demo** from the options menu in the top navigation bar.

<Warning>
  Deleting a demo is permanent and cannot be undone. All flows, captures, share links, and analytics data associated with the demo will be removed.
</Warning>

## FAQs

<AccordionGroup>
  <Accordion title="What is the main difference between single step and multi-step view?">
    Single step view is designed for editing one step at a time and works with the Flows list sidebar, making it easy to navigate across your entire demo. Multi-step view shows the entire sequence of a single Flow, which is helpful for understanding the story and reordering steps within that Flow.

    Both views offer the same editing capabilities — the difference is in how you navigate and view your content.
  </Accordion>

  <Accordion title="Can I still use the classic Flow builder?">
    Yes. The classic Flow builder is available as multi-step view. Use the toggle in the top navigation (or press <kbd>Shift</kbd> + <kbd>.</kbd>) to switch from single step view to multi-step view.
  </Accordion>

  <Accordion title="How do I switch between different Flows?">
    In single step view, use the Flows list sidebar on the left to see all your Flows and click on any step to edit it. In multi-step view, use the Flow dropdown to switch between different Flows.
  </Accordion>

  <Accordion title="Can I resize or collapse the Flows list sidebar?">
    Yes. Drag the right edge of the Flows list sidebar to resize it. Drag it all the way to the left to collapse the sidebar and give more space to the step editor.
  </Accordion>

  <Accordion title="Will my existing demos work in the Demo builder?">
    Yes. All your existing demos work in the Demo builder. You can edit them using either single step or multi-step view.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup>
  <Card title="Creating flows" icon="workflow" href="/build/flows">
    Learn how to create engaging step-by-step flows in your demos.
  </Card>

  <Card title="Themes" icon="palette" href="/build/themes">
    Customize the look and feel of your demos with themes.
  </Card>
</CardGroup>


# Creating flows
Source: https://docs.navattic.com/build/flows

Demos are composed of step-by-step flows.

<Frame>
  <img alt="Demo builder" />
</Frame>

Flows are step-by-step demos that a user progresses through at their own pace. Top-performing Flows are concise (8-15 steps) and include one or more conversion opportunities. Consider:

1. Is your goal to create a high-level overview or to showcase a detailed portion of your product?
2. How do you want users to interact with your product during the demo? (ex. Click a button, type a string of text, explore a dashboard)
3. This [storyboard template](https://docs.google.com/spreadsheets/d/1-TUqe5KsVgxMtUxopdXq-2r6bwhLix2TxwF0t3sKtmg/copy) may help plan the steps for your Flow.

## Step Appearance

The Flow Builder contains different step types to help create an engaging demo. To change step types, click the description on your desired step and select an option from the right-hand menu that appears.

<Tabs>
  <Tab title="Modal">
    Best used for welcome or closing messages, a Modal is a dialog box that appears on top of your Capture. Modals include a button to help viewers move to the next step. Modals can be positioned in the center or corners of the screen and encourage the end user to explore on their own.

    **Custom Modal Position**

    To change the positioning of your Modal, select **Modal** > **Custom position**. You can then select where you would like the modal to appear on the screen.
  </Tab>

  <Tab title="Tooltip">
    Best used to promote interactivity with your product, a Tooltip is small dialog box that anchors to a specific onscreen element. Clicking the selected element will automatically advance users to the next step.

    Tooltips can be positioned Above/Below/Right/Left of the selected element and combined with a backdrop (e.g., a light shadow on unselected elements) to best highlight your selected element.

    ### Anchor your Tooltip

    After adding the capture to your step, click **Select element** > Use your mouse to select an element > Use arrows to span element > **Save anchor.**

    ### Custom Tooltip Position

    To change the positioning of your Tooltip, open the position dropdown in the step toolbar. Select where the Tooltip should appear (Above, Below, Left, or Right) and use the fit-mode options in the same dropdown to control placement behavior when space is limited.

    <Tip>
      Use the fit-mode options to control how the Tooltip behaves when its selected position doesn't have enough space:

      * **Best-fit** — Default. The Tooltip tries all other sides (top, bottom, left, right) to find the best available space and stay on screen.
      * **Main axis** — The Tooltip shifts along the main axis (the direction it is placed) to stay on screen without flipping to the opposite side.
      * **Don't Flip** — Prevents the Tooltip from moving from its selected position, even if it is cut off at the screen edge.
    </Tip>

    ### Add a Backdrop with your Tooltip

    Adding a backdrop with your Tooltip can help highlight important elements, even on a smaller mobile screen. To add a backdrop open the **Step Settings** > **Tooltip**> toggle on **Backdrop** > select **Light, Medium** or **Heavy**

    <img alt="" />

    ### Customize Tooltip Width

    To customize the tooltip width, you can resize the tooltip directly in the flow builder by clicking and dragging the edges of the tooltip.

    You can also set default widths by going to **Themes** > Select **Theme** > **Tooltip** > Use the arrows to set the Width for **Small**, **Medium** and **Large** Tooltips. You can also edit the tooltip pointer size here.

    Once you have set your custom tooltip widths, go to your Product Demo > open the **Step Settings** > toggle on **Custom dimensions** > Select **Small**, **Medium**, or **Large.**

    <img alt={true} />

    ### Customize Tooltip Height

    To set a custom height for your Tooltip, open the **Step Settings** > toggle on **Custom dimensions** > Select **Set specific height.**

    ### Show Tooltip on Hover

    To make the Tooltip hidden by default and show it only when the Visitor hovers over the anchor element, open **Step Settings** > toggle on **Show on hover**.
  </Tab>

  <Tab title="Capture only">
    **Capture only** steps are used when you don't want any dialog boxes present on a particular step. These are combined with Triggers or Beacons to support the [live presentation / sales enablement use case](/use-cases/sales-enablement), but rarely used for marketing demos.

    *Demos with capture only steps are not recommended for sharing directly with viewers as they are a mostly unguided experience.*
  </Tab>

  <Tab title="Form">
    <CardGroup>
      <Card title="Navattic Forms" icon="file-text" href="/tracking/forms">
        Capture and track visitor information through forms in your demos.
      </Card>
    </CardGroup>
  </Tab>

  <Tab title="Embed">
    <CardGroup>
      <Card title="Embedded forms" icon="square-code" href="/tracking/forms/embedded">
        Integrate third-party forms and scheduling tools directly in your demo.
      </Card>
    </CardGroup>
  </Tab>

  <Tab title="Video">
    The **Video Step** feature lets you incorporate videos into your demo experiences. Teams use this to showcase customer case studies, highlight key use cases, and present branded content.

    To add a video step, select **Video** from the Step type dropdown in the Flow Builder. Once you've added a Video step, you can click **+ Select video** and select how you want to add your video:

    * **Upload**: Upload a video file directly from your computer.
    * **Insert Link**: Add a video from an external platform by pasting its URL. We support links from YouTube, Vimeo, Loom, Wistia, Vidyard, and Highspot.
    * **Record**: Create a new video right from Navattic using your webcam.
    * **Recently Used**: Quickly find and reuse a video you've already added to another demo.

    Uploaded videos, as well as videos from YouTube, Vimeo, or Wistia, use our themeable video player that includes playback analytics. This new player is on by default for uploaded videos and can be enabled for other providers under **Advanced** settings in the Video step. Once your demo is published, you can see playback analytics for your videos on the [demo analyze tab](/analyze#product-demo-analyze-tab).
  </Tab>
</Tabs>

## Interactive Elements

Interactive elements provide additional ways for users to interact with your product. By default, engaging with these elements will send the user to the next step (this is a "click action"). You can adjust the click action to be one or more of the following:

<Tabs>
  <Tab title="Beacon">
    A Beacon is a small pulsing dot next to an element within your Capture. A step may contain multiple Beacons.

    To add a Beacon, navigate to the bottom of your desired step and click **Add element** > **Beacon.** Select the onscreen element you would like to highlight. Clicking the purple "Beacon" bar to open the Beacon settings menu will let you assign a default position, custom size (set at the Theme) as well as one or more click actions for the Beacon.

    Anchor highlights (a pulsing element border visual) can also be enabled from the Beacon settings menu. Anchor highlights can be used with or without Beacons. Anchor highlight opacity can be set at the Theme.
  </Tab>

  <Tab title="Input Trigger">
    **Text input** - this will require users to enter a string of text to progress. This is applicable to Web Captures with HTML text input fields (ex. a search bar) and contenteditable elements.

    To add a Trigger, locate your desired step and click **Add element.** Select your Trigger Condition and Click Action(s).

    <Note>
      Tip: By default, Tooltips include a "progress on click" click action. This advances to the next step when the element is clicked. When using an Input Trigger and Tooltip on the same step, **deactivate** the Tooltip's **Progress on click** action by clicking \*\*Advanced \*\*under the Tooltip anchor > toggle off **Progress on click**.
    </Note>
  </Tab>

  <Tab title="Timer Trigger">
    **Timer trigger** - this will automatically trigger the click action after a specified amount of time.

    To add a Trigger, locate your desired step and click **Add element.** Select your Trigger Condition and Click Action(s).
  </Tab>

  <Tab title="Element Trigger">
    **Element trigger** - this will wait until an element has been clicked to progress. This can be used on any Capture or step type.

    To add a Trigger, locate your desired step and click **Add element.** Select your Trigger Condition and Click Action(s).
  </Tab>

  <Tab title="Voiceover">
    Enhance your demos with dynamic narration through various options, including reading from the individual steps, custom text-to-speech, or uploaded audio.

    To add voiceover to specific steps in your demo, in the Flow Builder click **Add element** > **Voiceover**. From here, use the dropdown to select the option you want to use:

    1. **Read from text**: Add in custom text to read from (tip: use this with a [*Capture only step*](/build/flows))
    2. **Read from step**: Read directly from the text in the Modal or Tooltip
    3. **Upload audio**: Upload audio files from your local storage. Supported formats include MP3, M4A, WAV, and MIDI files.

    <Note>
      If you select **Read from text** or **Read from step**, use the dropdown to select your preferred Voice.
    </Note>
  </Tab>

  <Tab title="Avatar">
    Avatars can be added to your demos to provide a personalized touch. Configure avatars in your demo settings to display a virtual guide throughout the experience.

    Once you add an Avatar to a step follow these instructions:

    1. Choose your preferred method to create the video:
       * **AI Avatar**: Generate a video from text.
       * **Recording**: Record a new video of yourself directly in Navattic.
       * **Upload**: Select a pre-existing video.
    2. Customize the avatar's appearance and behavior:
       * **Position**: Place the bubble in various locations on the screen (e.g., bottom-left).
       * **Avatar Size**: Adjust the size of the bubble.
       * **Autoplay**: Have the video play automatically when the step loads.
       * **When video finishes**: Configure actions that trigger after the video completes, such as automatically advancing to the next step.
  </Tab>
</Tabs>

<Expandable title="Actions">
  | **Click Action**  | **Description**                                                                                                                                                                                                                                    |
  | :---------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  | Continue          | Takes the end user to the next step in this Flow. If it is the last step, it will use the 'Last step continue behavior' that is set in the Flow Settings.                                                                                          |
  | Go back a step    | Takes the end user to the previous step in this Flow                                                                                                                                                                                               |
  | Jump to a step    | Allows visitors to jump to any step in the demo.                                                                                                                                                                                                   |
  | Start a Flow      | Begins a new Flow. Select from any Flows within your workspace.                                                                                                                                                                                    |
  | Open Checklist    | Prompts a Checklist to open at a specific point in the demo.                                                                                                                                                                                       |
  | Complete Flow     | Launches a Checklist if a Checklist is present in the Project                                                                                                                                                                                      |
  | Navigate to URL   | Takes the end user to an external link (e.g., a Book Demo page)                                                                                                                                                                                    |
  | Mark as Converted | For reporting purposes (i.e., not visible to the end user), this indicates that an end user has engaged with a specific CTA within your demo. Automatically added to CTA buttons within [Escape View](https://navattic-docs.navattic.com/cov09e1). |
</Expandable>

## Editing Rich Text

The **Rich Text** editor allows you to format the content inside of the Dialog. You can add headings, lists, links, and use **Copilot** to improve writing, fix grammar, or adjust length.

<Tabs>
  <Tab title="Button">
    Add additional buttons to your Dialog to present additional options such as a CTA or an option to continue the demo.

    If you'd like to enable `Next` and `Back` buttons to every step, you can enable this within settings.
  </Tab>

  <Tab title="Image">
    Add images to your Dialog to provide visual context or to illustrate a point.
  </Tab>

  <Tab title="Video">
    Add videos inline in your Dialog.
  </Tab>

  <Tab title="Personalization">
    <CardGroup>
      <Card title="Personalized demos" icon="user-pen">
        Make demos personalized by adding user and account properties.
      </Card>
    </CardGroup>
  </Tab>
</Tabs>

## Flow Settings

From the Flow Builder, click **Settings** to customize your demo further. Here you can:

<Tabs>
  <Tab title="Next + Back buttons">
    Add a `Next` and `Back` button to each step to allow the user to navigate through the demo.
  </Tab>

  <Tab title="Escape view">
    Allow the user to exit at any step and present a CTA step.
  </Tab>

  <Tab title="Keyboard navigation">
    Use your keyboard arrows `<- ->` to navigate through the demo.
  </Tab>

  <Tab title="Continue behavior">
    On the last step of a flow, configure whether to open a checklist or continue to the next flow.
  </Tab>
</Tabs>

## Capturing multiple flows at once

During a capture session, you can record screens for multiple flows without stopping and restarting. Click **New flow** in the capture bar to start recording a new flow while the session is still active — each flow gets its own name and captures.

When you're done, click **Complete session** to review all recorded flows and create them at once.

See [capturing multiple flows in one session](/build/captures/web#capturing-multiple-flows-in-one-session) in the web captures guide for full step-by-step instructions.

## FAQs

<AccordionGroup>
  <Accordion title="How do I add additional media files to a Flow?">
    You can add images, videos, and audio clips in Modals and Tooltips. From the Flow Builder, navigate to your desired step > click the dialog box > click "+" in the dialog header that appears > select and upload your media.

    Images and audio recordings will be uploaded directly from your device. Videos will require a link to a public video on Youtube, Vimeo, Loom, Wistia or Vidyard. We recommend keeping media attachments short to encourage users to explore your product on their own.
  </Accordion>

  <Accordion title="How should I end my Flow?">
    We recommend adding dual CTAs to the last step of your Flow. You may click "+" to add a Button to the Modal or Tooltip, or [hide Navigation Buttons](https://www.loom.com/share/dde828c52d4e4e4e820ddf64b2db5550) on the last step if needed. This will make it clear to your end user that they have completed the demo and encourage them to convert!
  </Accordion>

  <Accordion title="How do I use Navigation Buttons and CTA Buttons together?">
    To hide Navigation Buttons, click your step heading (ex. "Modal" or "Tooltip") > toggle on **Hide navigation** in the right-hand menu. Now that the navigation buttons aren't visible on this step, click the + button in the step and select **Button**. If you want to add more than one button, repeat this step.

    <img alt={true} />
  </Accordion>

  <Accordion title="How can I highlight multiple elements in a single step?">
    While each step can only include one Tooltip or Modal, **Beacons** can be used to highlight multiple elements at once. To do this, find your Step in the Flow Builder and simply [add Beacons](/flows#YRzY6) . We recommend including a Tooltip on this Step to communicate the intended workflow with users.
  </Accordion>

  <Accordion title="How do I fix a Tooltip that appears to run offscreen?">
    Tooltips may run off screen if the selected anchor element is too large and does not leave enough room to display the Tooltip fully. You can [change the tooltip position](/flows#2WZL5), [edit the tooltip height](/flows#AASb1) and/or [edit the tooltip width](/flows#_T4ZM) to try and get the Tooltip to fit.

    If these edits do not solve the problem, please select a smaller anchor element for this step.

    <img alt="" />

    <img alt="" />
  </Accordion>

  <Accordion title="How do I replace Captures within a Flow?">
    From the Flow Builder, locate the step where you want to switch the Capture and click on **Replace Capture**. This will open a dropdown menu where you can select a Capture from the current Collection, Add to the Collection, or select Captures from a different Collection in your workspace. If the new Capture has similar elements to the old Capture, the anchor element will automatically be updated.

    <img />
  </Accordion>

  <Accordion title="How will the Escape View appear in a Flow?">
    Escape View will match the Escape step that can be found at the end of your flow builder. To turn on [Escape view](https://navattic-docs.navattic.com/cov09e1), click settings > toggle on Escape view.

    <img />
  </Accordion>

  <Accordion title="When should I include a Form in my demo?">
    Forms are used to gather user information such as name, email, company, and more. If the goal of your demo is to directly generate leads, a Form may be helpful for gathering information. Typically, about 20% of demo Visitors will fill out a Form on the first step.

    If using a Form, we recommend introducing this early in your demo and keeping it brief (**1-2 fields if possible**). Remember, your demo likely also includes other CTAs and conversion points that help high-intent viewers make their interest known.
  </Accordion>

  <Accordion title="I am unable to select elements within the Flow builder.">
    The [Navattic Chrome Extension](https://chrome.google.com/webstore/detail/navattic/lbecioncobbndebbfdopnpinnibemoon) is required in order to select elements within the Flow builder. Be sure to install this extension first. If it is already installed, please remove and re-add it to update it.
  </Accordion>

  <Accordion title="How do I enable a text input trigger?">
    [Text input has value condition](/flows#JJQON) can be used to have viewers engage with the capture by adding a text string to a text input field. If a text input condition is used in conjunction with a tooltip on the same step, you will also want to toggle off the **Progress on click** option on the step (found by clicking on the Anchor > Advnaced) so that the demo does not move to the next step when the element is clicked.
  </Accordion>

  <Accordion title="Can I highlight elements without using Tooltips?">
    While most Navattic demos benefit from dialog boxes that tell a story about your product,' ' [Beacons](/flows#YRzY6) can be used to highlight standalone elements in your Captures. From your Flow > add a Beacon. By default, a Beacon is a blinking dot next to an element.
  </Accordion>

  <Accordion title="Can I make edits across multiple steps at once?">
    With the Bulk Editor, you can apply edits across multiple steps at once. Bulk edits include:

    * Updating all beacons to triggers
    * Turning multiple modals into tooltips
    * Changing all beacons to have a highlight appearance instead of pulse
    * Deleting multiple beacons or triggers at the same time
    * Copying or Moving Steps to other Flows within your demo or to other Demos
    * Deleting multiple steps at the same time
    * and more!
  </Accordion>

  <Accordion title="Can I copy or move steps into another Flow?">
    With the Bulk Editor, you can copy or move steps into another Flow within the same demo or to another Demo in your Workspace.

    To do this, check off the steps you want to move or copy and then select the **Copy to...** or **Move to...** icon at the bottom of your screen. From here, you'll be prompted to select whether you want to copy the steps into a Flow within this demo or in another demo. Once you select the Flow you want to move it to, click **Copy # step.**

    [View a 2-minute tutorial here](https://www.loom.com/share/b844f27c6f444054afa5790c65adfa7c?sid=b4e95e64-3e59-47cd-9d2b-3083d04ef645) .

    <img alt={true} />
  </Accordion>

  <Accordion title="How do I copy or move a flow to another Demo?">
    With Product Demos, you can copy over Flows from existing Product Demos. To do this, visit **Flows** > **+ Create Flow** > **Copy**. Select the target Product Demo and desired Flow to copy into your new Product Demo.

    You can also copy or move multiple Flows at once by selecting the Flows you want to Copy and then selecting the **Copy to...** or **Move to...** icon at the bottom of the screen. From here, you'll be prompted to select which Demo you want to add the Flows to.

    [View a 2-minute tutorial here](https://www.loom.com/share/b844f27c6f444054afa5790c65adfa7c?sid=b4e95e64-3e59-47cd-9d2b-3083d04ef645) .

    <img />

    ### Can I add navigation buttons to my demo without using a Modal or Tooltip?

    Yes, you can add navigation buttons without using a modal or tooltip by creating a Theme with a transparent dialog box and border.

    To create a Theme, visit **Themes** > **+ Create theme**. From here, select **Dialog** > **Dialog Background Color** > use the opacity slider under the color picker to make the dialog box transparent. Repeat this step with the **Dialog border color**.

    Learn more about [Themes](/build/themes).
  </Accordion>

  <Accordion title="Can I add navigation buttons to my demo without using a Modal or Tooltip?">
    Yes, you can add navigation buttons without using a modal or tooltip by creating a Theme with a transparent dialog box and border.

    To create a Theme, visit **Themes** > **+ Create theme**. From here, select **Dialog** > **Dialog Background Color** > use the opacity slider under the color picker to make the dialog box transparent. Repeat this step with the **Dialog border color**.

    Learn more about [Themes](/build/themes).
  </Accordion>

  <Accordion title="Can I include superscript formatting in a Modal or Tooltip?">
    Yes, to add superscript formatting to a Modal or Tooltip follow the instructions below:

    1. Use [https://lingojam.com/SuperscriptGenerator](https://lingojam.com/SuperscriptGenerator) to generate the superscript.
    2. Copy/paste it into the Tooltip or Modal directly. No additional formatting is needed.
  </Accordion>
</AccordionGroup>


# Demos on mobile
Source: https://docs.navattic.com/build/mobile

Configure how your demos appear on mobile devices and smaller screens.

<Frame>
  <img alt="Mobile swipe demo" />
</Frame>

Navattic provides multiple options for viewing demos on devices smaller than 800px wide - this includes most smart phones and smaller tablets.

To configure your mobile setting, open the `Mobile` tab on the Product demo page.

<MediaCard type="demo" title="Demos on mobile" />

<MediaCard title="Demos on mobile" type="video" />

## Mobile options

There are a few different options for viewing interactive demos on mobile devices:

<Tabs>
  <Tab title="Mobile zoom">
    The **Mobile zoom** option allows you to serve your standard desktop demo directly to users on mobile devices. When enabled, viewers can use familiar pinch-to-zoom gestures to enlarge, navigate, and interact with the product on their smaller screens. This provides a simple way to maintain your original layout while ensuring mobile visitors can comfortably explore your demo.
  </Tab>

  <Tab title="Mobile swipe demo">
    The Mobile swipe demo is used to engage your mobile visitors with a short and visual experience they can *swipe* through.

    `+ Copy from Flow` allows you to reuse Captures and copy from your existing demo.

    All Mobile swipe demos start with a Welcome and Farewell step. Click +Add to add steps in between. Each step contains an image, title, and description.

    **Best Practices**

    1. Include **no more than 8 steps.**
    2. Upload an Image or existing Capture to the **Welcome step.**
    3. If you are uploading your own image, use dimensions similar to height: `16rem` or `256px` and width: `24rem` or `384px`, allowing the image to cover a larger portion of the screen. Accepted file types include **.PNG**, **.GIF**, and **.JPEG**.
    4. Keep the text minimal and clear and focus on short, impactful sentences. The **Description** should complement the **Title**, but keep it to a minimum since it’s often skimmed.
    5. Edit the **Theme** of your Mobile swipe demo to match your brand. To do this, visit the **Theme** tab in your demo > **Edit Theme** > **Mobile Swipe**.

    **Additional Mobile Swipe settings**

    1. **Auto Progress**: Enabling **Auto Progress** for your Mobile Swipe Demo will automatically guide visitors through the demo by advancing to the next step after 4 seconds.
    2. **Confetti**: Toggle on **Completion confetti** to allow visitors to celebrate once they complete their final step!
    3. **Crop the Captures**: Crop the Captures or upload a new Image to ensure the images are colorful and eye-catching.
    4. **CTA Button**: Toggle on the **CTA button** and use **Open in new tab** to ensure Visitors can easily access it throughout the mobile swipe demo.
  </Tab>

  <Tab title="Mobile alert">
    The Mobile alert is a good option if you prefer not to present your demo to mobile viewers or do not expect heavy mobile traffic to your demo.

    **Message, Custom Image, or Video**

    You can either use the default mobile alert or create your own. The Mobile alert includes a title and description which can be edited in Build > Mobile > Mobile alert > Edit > **Message**.

    If you'd prefer to upload a custom image, select **Custom Image**. You can then upload an image from your local storage. Alternatively, select **Video** to upload a video from your local storage.
  </Tab>

  <Tab title="Mobile scaled view">
    With **Mobile scaled view** enabled, the Capture will appear on top of any dialog that is present on this step, while maintaining the proportions of your original app. We recommend taking Captures on a smaller window if you plan to use Mobile scaled view to ensure that elements remain legible on smaller devices.

    <Info>
      Check out [Klue's Demo Arena](https://klue.com/demo-arena) in a window below 800px wide or use a mobile simulator like [this Chrome
      extension](https://chromewebstore.google.com/detail/mobile-simulator-responsi/ckejmhbmlajgoklhgbapkiccekfoccmk)' ' to see examples of Mobile scaled view.
    </Info>
  </Tab>

  <Tab title="Show desktop demo">
    **Show desktop demo** is just what it sounds like -- a scaled-down version of your desktop demo will show on mobile devices.
  </Tab>
</Tabs>

#### Customer examples of mobile demos

<CardGroup>
  <Card href="https://www.getmeez.com/" title="Meez: Take a Tour">
    Mobile swipe demo
  </Card>

  <Card href="https://www.doppler.com/" title="Doppler: Take a self-guided tour">
    Mobile swipe demo
  </Card>

  <Card href="https://www.snaplogic.com/products/application-integration" title="SnapLogic: Take a tour">
    Mobile swipe demo
  </Card>

  <Card href="https://navattic-docs.navattic.com/m1860spg" title="Navattic: Single step view">
    Mobile zoom
  </Card>
</CardGroup>

<Info>
  View these examples in a window below 800px wide to activate the Mobile swipe view or use a mobile simulator like [this Chrome
  extension](https://chromewebstore.google.com/detail/mobile-simulator-responsi/ckejmhbmlajgoklhgbapkiccekfoccmk) .
</Info>


# Responsive strategies
Source: https://docs.navattic.com/build/responsive

Learn how to make your demos look great on every screen size.

Navattic provides four different responsive strategies that determine how your Navattic demo appears on viewports of different sizes. Visit your Demo > Build > Responsive to adjust.

<Tabs>
  <Tab title="Scale width">
    This option will fit the width of the capture to the width of the visitor's screen. This is a good option if you are embedding a demo in a smaller iFrame or expect it to be viewed on a variety of devices.

    <Info>
      **Tip**: Resize your window to **1440 x 900px or smaller** when taking Captures for a consistent
      experience with Scale Width.
    </Info>

    <Expandable title="preview">
      <img alt="Scale Width" />
    </Expandable>
  </Tab>

  <Tab title="Responsive">
    The default setting for new Product Demos, **Responsive** will apply your application's default styles for different viewports. This provides the most realistic look and feel for your demos and is recommended if you plan to share a Product Demo Link directly with end users.

    <Expandable title="preview">
      ![Responsive](https://archbee-image-uploads.s3.amazonaws.com/YYk8JOCMmxT-GPN-0CkK6/2aMJeNj7ApHGRFM6w-2mu_responsive.gif)
    </Expandable>
  </Tab>

  <Tab title="Scale width+height">
    This option will fill the entire screen while maintaining the relative sizes of the original screen.

    <Expandable title="preview">
      <img alt="" />
    </Expandable>
  </Tab>

  <Tab title="Fixed">
    A Fixed strategy presents Captures at their original dimensions, regardless of the end user's viewport dimensions. Visitors will scroll if there is overflow.

    <Expandable title="preview">
      ![](https://archbee-image-uploads.s3.amazonaws.com/YYk8JOCMmxT-GPN-0CkK6/9fv7FesJk-yZMSHQld8ET_fixed-responsiveness-strategy.gif "\"Fixed\" behavior will present Captures at their original dimensions")
    </Expandable>
  </Tab>

  <Tab title="Contain">
    The **Contain** strategy scales the capture to fit within the visitor's viewport while preserving the original aspect ratio. The entire capture is always visible — no cropping and no scrolling — but letterboxing (empty space on the sides or top/bottom) may appear on screens that don't match the capture's proportions.

    <Note>
      Contain is a good choice when it's important that visitors always see the full capture, such as when using fixed-size screenshots or when your demo layout relies on precise positioning.
    </Note>
  </Tab>
</Tabs>

<Icon icon="party-popper" /> **Congratulations** -- you've learned how to make your demo
**Responsive** to different screen sizes.

Next, learn how to customize how your demo appears on mobile devices and smaller screens

<CardGroup>
  <Card title="Demos on mobile" icon="smartphone" href="/build/mobile">
    Configure how your demos appear on mobile devices and smaller screens.
  </Card>
</CardGroup>


# Customize your theme
Source: https://docs.navattic.com/build/themes

Learn how to customize your theme with your company brand.

<Frame>
  <img alt="Themes card" />
</Frame>

Themes allow you to customize your demo with your company brand.

<Note>
  The **Themes** section is only visible to members whose role has theme permission enabled. Workspace admins can manage theme permissions per role at **Settings** > **Roles**. Setting a theme as your workspace default requires the Admin role.
</Note>

<Expandable title="theme properties">
  **Themes allow you to:**

  * Change the font
  * Add a watermark
  * Add a progress bar
  * Update the Dialog border color and radius
  * Change the Modal width
  * Change the Tooltip width and pointer size
  * Edit Buttons
  * Edit Beacons
  * Change the Checklist checkmark color and task completion opacity
  * Change the Checklist launcher placement, padding, and color
  * Add a CTA banner
  * Change the backdrop border color
  * Change the Modal and Tooltip margins
  * Customize the Mobile Swipe Demo theme.
</Expandable>

<Steps>
  <Step title="Create a Theme">
    Navattic comes prepared with a Light Theme and a Dark Theme. You can duplicate an existing Theme to make edits, or select **+ Create theme** to start from scratch. Themes are available to all members of your Workspace. Once created, apply your Theme to any Flow or Checklist in order to view changes.
  </Step>

  <Step title="Apply a Theme">
    To apply a Theme to your demo, navigate to a Product Demo > Build > Theme. Apply a single theme throughout your entire demo, or select a different theme for each flow.

    <Frame>
      <img alt="Apply a Theme" />
    </Frame>
  </Step>
</Steps>

### FAQs

<AccordionGroup>
  <Accordion title="How can I autogenerate a Theme using my company colors?">
    To autogenerate a Theme, go to Themes > Quick Builder. From here, you can choose a primary color and a secondary color > Click "Generate theme". If you want one of the colors to be the default background color, toggle on "background".

    These colors will automatically apply to all of the elements in Themes including buttons, beacons, tooltips, etc.

    <img alt="" />
  </Accordion>

  <Accordion title="How can I change the font?">
    To edit the font used in your demo, go to Themes > Font. You can edit the font color, size, line height, link color, and link hover color. You can also select a custom font.

    <img alt="" />
  </Accordion>

  <Accordion title="How do I edit the Button color and size?">
    To customize the Button, go to Themes > Select "Buttons" in the menu on the right. From here you can edit the Button border, text color, background color, font weight, and padding.

    <img />
  </Accordion>

  <Accordion title="How do I edit the Beacon color and size?">
    To edit the color and size of the Beacon, go to Themes > Select "Beacons" in the menu on the right.

    <img alt="" />
  </Accordion>

  <Accordion title="How can I change the modal width?">
    To edit the modal width, go to Themes > Select "Modal" in the menu on the right. Use the arrows to change the modal width. This will change the width off all modals in demos with this Theme.

    <img />
  </Accordion>

  <Accordion title="How can I customize the width of my Tooltips?">
    To edit the Tooltip width, go to Themes > Tooltip. Use the arrows to change the Tooltip widths for
    Small, Medium, and Large. Check out
    [Customize Tooltip Width](/build#Np-Mf)
    for more details.
  </Accordion>

  <Accordion title="How do I edit the Checklist background color, border, and font?">
    To edit your Checklist background color and border, go to Themes > Use the drop down to select Checklist > Select Dialog.

    You can also edit the Font in your Checklist directly above Dialog. Make sure to Publish & Exit after making changes to your Checklist.

    <img alt="" />
  </Accordion>

  <Accordion title="How do I edit the Checklist checkmark color and task completion decoration?">
    To edit the Checklist checkmark color visit Themes > Select Checklist in the righthand menu.

    <img alt="" />
  </Accordion>

  <Accordion title="How do I edit the Checklist Launcher?">
    To edit the Checklist Launcher visit Themes > Select Checklist Launcher in the righthand menu.

    You can edit the placement, the horizontal and vertical padding, the border radius, the background color, the text color, and the font weight.

    <img />
  </Accordion>

  <Accordion title="How do I edit the Progress Bar?">
    To edit the Progress Bar (for your Modals, Tooltips and Checklist), visit Themes > Select Progress Bar in the righthand menu. Select "Show checklist progress bar" to turn on the Progress Bar for Checklists or "Show dialog progress bar" to turn on the Progress Bar for Modals and Tooltips.

    <Note>
      To preview what the Progress Bar will look like for Modals, Tooltips, or the Checklist you can use
      the dropdown menu in the top lefthand corner.
    </Note>

    <img alt="" />
  </Accordion>

  <Accordion title="How can I add a CTA banner to my demo?">
    Visit Themes > Banner to create a custom CTA Banner for your demos. Customize the banner's colors, text, and linked resources. Publish & Exit to add your banner to existing projects.

    <img alt="" />
  </Accordion>

  <Accordion title="How can I add a custom watermark to Tooltips and Modals?">
    Visit Themes > Watermark to upload an image to be used in Modals and Tooltips, and set your watermark's position, CTA link, and opacity.

    <img alt="" />
  </Accordion>

  <Accordion title="How can I change the Tooltip Border Color when paired with a Backdrop?">
    Visit Themes > Tooltip > Anchor backdrop highlight color to change the backdrop border color.
    Check out how to
    [add a backdrop to your Tooltip](/flows#OX0vQ).
  </Accordion>
</AccordionGroup>


# Product updates
Source: https://docs.navattic.com/changelog/index

New product updates and announcements

<Update label="June 2026">
  ## Voiceover improvements

  Custom pronunciations ensure voiceovers pronounce your product and brand names correctly. Add a pronunciation once and it applies across all demos with voiceovers.

  Speaking rate controls let you adjust how fast the voiceover reads — per step or across every step in a demo.

  You can also set a workspace default voice per language, or a single default across all your demos.

  [See a demo of voiceover improvements](https://navattic-website.navattic.com/e46i0uiv)

  <Frame>
    <img alt="Voiceover improvements" />
  </Frame>

  ## Media captures in sandbox demos

  Photos and videos can now be added to Sandbox demos as media captures. Capture a screen recording or image directly in a Sandbox flow, then wire NavLinks to use them in your clickable navigation — just like web captures.

  <Frame>
    <img alt="Media captures in Sandbox demos" />
  </Frame>

  ## Agent Demo avatar improvements

  AI avatars in Agent Demos can now be fixed to the side or expanded to fill the screen while the agent is talking, then move into a sidebar during a product flow. New AI avatars are also available to choose from.

  <Frame>
    <img alt="Agent Demo avatar improvements" />
  </Frame>

  ## Agent Demo qualification outcomes

  Qualification questions in Agent Demos can be mapped to any custom property in your CRM. After a session ends, the AI extracts the visitor's answer from the conversation and writes it to the property.

  You can also configure the Agent to dynamically change the demo CTA based on a visitor's answers — for example, routing enterprise prospects directly to a sales rep.

  <Frame>
    <img alt="Agent Demo qualification outcomes" />
  </Frame>

  ## Launchpad MCP

  Create custom Launchpad share links for specific prospects directly from your AI tool of choice. Connect the Navattic MCP to Claude, ChatGPT, or Cursor to build targeted share links without opening the app.

  <Frame>
    <img alt="Launchpad MCP" />
  </Frame>

  ## Changelog in app

  The changelog is now available directly in Navattic. Find it in the account avatar dropdown or the support dropdown.

  <Frame>
    <img alt="Changelog in app" />
  </Frame>
</Update>

<Update label="May 2026">
  ## Workspace Capture Collections

  Reuse captures across demos without duplicating work.\
  \
  Store capture collections in a shared workspace library, so your team can build multiple demos without having to re-take or duplicate captures.\
  \
  Edit or recapture once, and it will instantly update all associated demos using the shared collection. When updating, the capture will also show which demos it's associated with.

  For Growth and Enterprise customers, Workspace Collections are now live! We also support custom permissions for controlled access to Workspace Collections.

  <Frame>
    <img alt="Workspace Collections" />
  </Frame>

  ## Navattic MCP

  The Navattic MCP is now out of Beta. Connect to Claude or ChatGPT to report on demo performance, see high-intent demo leads, or quickly monitor which demos haven't been updated in a bit.

  For Base, Growth, or Enterprise customers, start using the MCP by [following these instructions.](https://docs.navattic.com/workspace/mcp-server) Note that a Claude or ChatGPT admin will need to set up the MCP.

  If you use Launchpad, you can use the MCP to view and build custom share links.

  <Frame>
    <img alt="Navattic MCP" />
  </Frame>

  ## Upload Content

  Copilot can now read your brand guidelines directly from a website or file.

  Add a URL or upload a PDF, DOCX, TXT, or MD file, and Copilot extracts your brand voice, product context, and GTM context into Workspace Knowledge.

  <Frame>
    <img alt="Upload Content" />
  </Frame>

  ## Voiceover Defaults

  Set a default voice for each of your demo languages at the Workspace Level, and new steps inherit it automatically.

  You can also bulk-sync all flows to the workspace default from the flow builder.

  <Frame>
    <img alt="Voiceover Defaults" />
  </Frame>

  ## Team-level Permissions

  Directory Sync (SCIM) now provisions teams automatically. Map directory groups from your identity provider to Navattic teams, and membership stays in sync.

  When a group changes, Navattic reflects it, and you control whether to keep or remove members when a mapping is removed.

  Available for Growth and Enterprise customers with Directory Sync enabled.

  <Frame>
    <img alt="Team-level Permissions" />
  </Frame>
</Update>

<Update label="April 2026">
  ## Navattic MCP server (Beta)

  The Navattic MCP server lets teams connect Navattic directly to AI tools like Claude, Cursor, and ChatGPT. Query demo analytics, pull workspace data, and trigger Navattic actions like create flow without leaving your LLM of choice.

  [See a demo of the MCP](https://navattic-website.navattic.com/5br0fab)

  We are looking for beta testers and feedback on new tools to add to the MCP.

  Email [team@navattic.com](mailto:team@navattic.com) to get early access.

  <Frame>
    <img alt="Video Controls" />

    <img alt="Video Controls" />
  </Frame>

  ## Capture translation

  Translate an entire demo for an international campaign in a few clicks. Captures, voiceovers, and AI avatars can now be translated alongside step text, so every part of the experience speaks the viewer's language.

  Use the new Glossary to fine-tune terminology and standardize specific words and phrases across all your demos at once.\
  \
  [**See a demo of Capture translation**](https://navattic-website.navattic.com/e26b50uow)

  Capture translation is part of our Enterprise plan. Reach out to your CSM if you are interested in adding this to your workspace.

  <Frame>
    <img alt="Capture translation" />
  </Frame>

  ## Narrated demos

  Narrated demos let you capture your screen alongside a live voice narration, then use Copilot to generate a demo with synced audio and screen. \
  \
  Choose to display your Narrated demo with voiceovers or custom AI avatars.\
  \
  For Growth and Enterprise customers, when you go to build a new demo, you'll be prompted to create an Interactive demo, Sandbox demo, or Narrated demo.

  <Frame>
    <img alt="Narrated demos" />
  </Frame>

  ## Document export as PDF

  Share demos as a PDF with step screenshots and copy, or as a plain numbered text list.\
  \
  Convert your demo into a one-pager in seconds for async reviews, stakeholder sign-offs, or buyers who want something to reference later.

  <Frame>
    <img alt="PDF export" />
  </Frame>
</Update>

<Update label="March 2026">
  ## Video Controls in Single Step View

  Video duration settings, playback options, actions, and an advanced settings menu are now accessible directly in the single step view. This applies to both video steps (uploaded/embedded videos) and video captures.

  You can configure autoplay behavior, looping, duration limits, and post-video actions all from the same panel where you're editing the step – the full set of video controls lives right alongside your other step settings.

  <Frame>
    <img alt="Video Controls" />
  </Frame>

  ## HubSpot on Sales & Pipeline Impact Dashboards

  The Sales Impact and Pipeline Impact dashboards now work with HubSpot in addition to Salesforce. HubSpot integrations can opt into a "deal mode" in their integration settings, which syncs opportunity and pipeline data through the same attribution engine that powers Salesforce analytics.

  Once enabled, your HubSpot deals flow into the same dashboards – pipeline created, deals influenced, revenue attributed to demos. If your workspace has both Salesforce and a deal-mode HubSpot connected, a CRM source dropdown appears on both dashboards so you can toggle between data sources. Your selection persists across sessions.

  Learn more about the [HubSpot Integration](/integrations/hubspot).

  <Frame>
    <img alt="HubSpot Pipeline" />
  </Frame>

  ## Workspace Knowledge for Copilot

  Copilot now draws on workspace-level knowledge to deliver more tailored suggestions across all review features – writing, CTAs, flow structure, and full demo reviews.

  A new settings panel lets you define three types of context: brand voice (tone, terminology, style guidelines), product context (what your product does, key features, differentiators), and go-to-market positioning (target audience, use cases, competitive landscape).

  An "Auto-populate with AI" button generates a starting point from your company's domain, pulling from trained data and falling back to web search for newer products. This knowledge is stored at the project level, so workspaces with multiple products can maintain separate context for each.

  Learn more about [Copilot](/copilot/generate).

  <Frame>
    <img alt="Workspace knowledge" />
  </Frame>
</Update>

<Update label="February 2026">
  ## Single-Step Demo View

  Introducing a **new, more intuitive demo building experience**.\
  \
  Captures, Flows, Checklists, Mobile settings, and Themes - previously spread across multiple pages - are now accessible from a single building view.

  Use the sidebar to move between steps in different flows and keep your story consistent across the entire demo.

  Prefer the previous layout? Toggle back to the multi-step view at any time.

  <Frame>
    <img alt="Single-Step Demo" />
  </Frame>

  ## Mobile Zoom

  Let mobile viewers explore your full desktop demo.\
  \
  Mobile Zoom is a new strategy in the Mobile tab that gives mobile viewers full access to your desktop demo with **pinch-to-zoom and panning.**

  Zoom in to read text, explore details, and navigate the product.

  There are now three main Mobile Strategies available:

  * Mobile Zoom: Shows the full desktop demo with pinch-to-zoom and panning
  * Mobile Swipe Demos: Shows a swipable demo experience built for mobile
  * Mobile Alert: Shows a custom fallback message, video, or image

  <Frame>
    <img alt="Mobile Zoom" />
  </Frame>
</Update>

<Update label="January 2026">
  ## Copilot Review

  Run demos through Review to instantly analyze your demo for structure, clarity, and engagement, and flag any issues missing, such as CTAs or unclear copy.

  Get a demo score based on our highest-performing demo benchmarks. Apply step-by-step suggestions like "improve writing in step 11" or "shorten this step for clarity" with one click.

  <Frame>
    <img alt="Copilot Review" />
  </Frame>

  ## Highspot Integration

  If you're using Highspot, you can now embed Navattic interactive demos directly into their Digital Sales Rooms and Spots.

  Sellers can browse, select, and personalize demos without leaving Highspot, giving buyers hands-on product experiences alongside decks, case studies, and other sales content.

  <Frame>
    <img alt="Highspot Integration" />
  </Frame>
</Update>

<Update label="December 2025">
  ## Copilot Generate

  Let Copilot build a first draft of your demo for you.\
  \
  Choose a relevant Use Case, and Copilot will automatically write demo copy, anchors, tooltips, and craft a compelling demo story.

  <Frame>
    <img alt="Copilot Generate" />
  </Frame>

  ## Copilot Brand & Tone

  Add Brand and Tone context to build all your demos with brand consistency.

  Adjust prompts to match your messaging style, so every team member can build, edit, and personalize demos with set guardrails for brand tone.

  <Frame>
    <img alt="Copilot Brand & Tone" />
  </Frame>

  ## Copilot Prompt

  Make bulk edits or quick fixes without touching individual steps.

  Whether you need to rename steps, update CTAs, or insert new steps, Copilot Prompt understands natural language and handles the updates for you.

  <Frame>
    <img alt="Copilot Prompt" />
  </Frame>
</Update>

<Update label="November 2025">
  ## Gong Integration

  Share demos directly inside Gong and track engagement alongside your call recordings.

  Create and send personalized demo links without leaving Gong. All demo engagement data syncs automatically to visitor and account records for full visibility.

  <Frame>
    <img alt="Gong integration" />
  </Frame>

  ## Copilot: AI Theme generator

  Auto-generate demo themes based on any website.

  Provide a URL and Copilot will pull brand colors, typography, button styles, and other design tokens to generate a cohesive demo theme, ideal for account-specific personalization.

  Generate via Settings → Themes → Generate with Copilot.

  <Frame>
    <img alt="Copilot: AI Theme generator" />
  </Frame>

  ## Edit SVG charts in Capture Editor

  Edit SVG charts directly in the Capture Editor.

  Click to update values, labels, and data points in chart elements, no external tools needed.

  Perfect for customizing metrics in your demo to match specific scenarios or audiences.

  <Frame>
    <img alt="Edit SVG charts in Capture Editor" />
  </Frame>

  ## Video step engagement analytics

  Analyze where viewers engage with your video steps.

  The new playback breakdown chart shows engagement at 5-second intervals so you can identify high-attention moments and drop-off points.

  Find it under Analyze → Step Breakdown.

  <Frame>
    <img alt="Video step engagement analytics" />
  </Frame>

  ## Record intro videos from Launchpad

  Record personalized intro videos directly in Launchpad.

  Use the new Record Video option in your Personal Intro Video settings to capture webcam and microphone recordings on the spot.

  Add context or prospect-specific messaging or use-case explanations without needing pre-recorded files.

  <Frame>
    <img alt="Record intro videos from Launchpad" />
  </Frame>

  ## Filter audiences by email source

  Target visitors with precision using the new email source filter.

  Build audiences based on how emails were collected: form fills, CRM syncs, manual uploads, or API imports.

  Use this in Audiences → Create Audience → Email Source to tailor demo experiences or refine analytics.

  <Frame>
    <img alt="Filter audiences by email source" />
  </Frame>

  ## Expanded AI avatar library + avatar cloning

  Choose from an expanded library of AI avatars with preview headshots and voice samples.

  Access beta features for avatar and voice cloning to match your brand tone or feature internal team members.

  Contact your account team to enable custom avatars or custom voiceovers.

  <Frame>
    <img alt="Expanded AI avatar library + avatar cloning" />
  </Frame>

  ## New in-app Sidebar

  The sidebar has been redesigned to simplify navigation and provide dedicated views for Interactive Demos, Launchpad, and more.

  To open Launchpad, click on the Launchpad icon on the far left of the sidebar.

  <MediaCard type="demo" title="In-app sidebar" />

  <Frame>
    <img alt="New in-app sidebar" />
  </Frame>
</Update>

<Update label="October 2025">
  ## Analytics table view

  Evaluate all your workspace demos in one simple table view.\
  \
  Go to Analytics → Compare → All Demos, you can now view and sort all your demo visitor data at once. Track key metrics like:

  * Visitors
  * Engaged visitors
  * CTA clicks
  * Click-through rate
  * Time spent
  * Total steps

  Export this table data to combine with your full funnel reporting.

  <Frame>
    <img alt="Analytics table view" />
  </Frame>

  ## Analyze all versions

  Understand holistically how your demos have performed over time. \
  \
  Under the Analyze tab → Step breakdown toggle on "Aggregate versions" to see drop-off rates across every version of your demo.

  <Frame>
    <img alt="Analyze all versions" />
  </Frame>

  ## Outreach integration

  Add demos directly into Outreach templates and sequences to scale consistent product messaging. \
  \
  With the Navattic Outreach app, sellers can share personalized interactive demos with specific recipients or add to a general outbound campaign.

  <Frame>
    <img alt="Outreach integration" />
  </Frame>

  ## Outlook integration

  Inject demo previews directly into your Outlook emails. \
  \
  With the new Navattic button in the Outlook toolbar, you can insert demos in one click and auto-detect recipients for personalization variables.

  <Frame>
    <img alt="Outlook integration" />
  </Frame>

  ## HubSpot account timeline events

  See timeline events in HubSpot based on accounts or deals, not just contacts.\
  \
  Configure playbooks to track and segment your accounts by company-level engagement or ICP criteria.

  <Frame>
    <img alt="HubSpot account timeline events" />
  </Frame>

  ## Last edited history

  Instantly see who's editing what demo. On any demo, see edit history by hovering over the "Edited x days ago" label.

  <Frame>
    <img alt="Last edited history" />
  </Frame>
</Update>

<Update label="September 2025">
  ## Video fallback on mobile

  Add a full-screen video as a fallback option for mobile users.

  In your mobile settings, upload or select a video to display when visitors view your demo on a phone. \
  \
  We automatically detect device type, so desktop users still see the full-screen interactive demo, while mobile users will see a video.

  <Frame>
    <img alt="Video fallback" />
  </Frame>

  ## Media capture editing

  Adjust how screenshots appear inside device frames.\
  \
  In the media capture editor, select "Position" to align content to the top, center, or bottom to better fill the screen. Tooltips and annotations will also follow your selected alignment.

  <Frame>
    <img alt="Media capture editing" />
  </Frame>

  ## Tooltip selector preview

  Preview tooltip step placement directly when building your demo. \
  \
  When you go to add a tooltip, you'll now see a live preview of what your tooltip looks like in your demo. The builder automatically suggests a default position, which you can adjust directly from the editor.

  <Frame>
    <img alt="Tooltip selector preview" />
  </Frame>

  ## Sandbox editing

  Create and refine demos faster from directly within Sandbox mode.\
  \
  You can now re-capture individual steps without starting over or edit, delete, and reorder steps in the Sandbox builder.

  ## Bulk editing for product demos

  Clean up your demo workspace in a few clicks.

  Use the bulk editor to select multiple demos to mass publish, archive, or apply boards and labels.
</Update>

<Update label="August 2025">
  ## Copilot: Generate

  Copilot: Generate is now available for all workspaces. Generate builds on top of our existing AI writing assistant to help you create end-to-end demos based on Navattic best practices.

  To use Generate, select a Use Case the next time you take new Captures. After capturing, Copilot will add copy for each step, select step types, and anchor tooltips using relevant information from your Captures.

  Copilot is built with best practices from 30,000 demos built on Navattic, so you know each demo is out-of-the-box optimized.\
  \
  [**See an interactive demo of Copilot**](https://navattic-website.navattic.com/rlfy08a5)

  We have more Copilot features coming - contact [success@navattic.com](mailto:success@navattic.com) if you have feedback or would like early access.

  <Frame>
    <img alt="Copilot: Generate" />
  </Frame>

  ## Copilot: Use Cases

  Copilot comes with default prompts with built-in use-case-specific best practices.\
  \
  You also have the option to add on additional use case prompts or adjust prompts to match your exact brand messaging, voice, and tone.

  <Frame>
    <img alt="Copilot: Use Cases" />
  </Frame>

  ## Recapture

  Simplify how you replace Captures in existing demos. Select Recapture to automatically take you back to your original product page URL at the Capture or Collection level.\
  \
  While recapturing, preview the old vs the new Capture to see how your product has changed. Recapture will also preserve anchors from the original Capture.

  <Frame>
    <img alt="Recapture" />
  </Frame>

  ## Animating Text with Magic Editor

  Need to simulate an AI chat or mimic typing inside your demo? With our Animating Text Magic Editor, you can now show animated text within a Capture.\
  \
  In the demo, the Capture will show the text being typed out automatically to recreate live interactions like AI chatbots.

  <Frame>
    <img alt="Animating Text" />
  </Frame>
</Update>

<Update label="July 2025">
  ## Share demos from the Launchpad Chrome Extension

  Empower reps to build and send demos directly from their existing workflow:

  * **Access a library of pre-approved demos** that reps can mix and match
  * **View prospect and account activity** directly from the Chrome Extension
  * **Create custom demos** to deliver tailored experiences for each prospect

  <Frame>
    <img alt="Launchpad Chrome Extension" />
  </Frame>

  ## See interests and new stakeholders

  Add interest levels to demos to understand buyer intent before your first call:

  * **Get alerted via Slack or email** when prospects go through your demos
  * **Track buyer interest** to inform smarter, more strategic follow-ups
  * **Uncover new members** of the buying circle when demos are shared internally

  <Frame>
    <img alt="Interest Demos" />
  </Frame>

  ## Create and present lightweight Sandbox demos

  Quickly build Sandboxes with auto-linked screens that reps can use live on calls:

  * **Personalize demo data** to specific prospects, accounts, or verticals
  * **Present demos** in a stable, standardized environment with confidence
  * **Stay on track** with optional presenter notes or click guidance
    <Frame>
      <img alt="Sandbox Demos" />
    </Frame>
</Update>

<Update label="June 2025">
  ## A/B Tests

  Wondering which button copy drives more engagement? Or what opening message converts better? Now you can test it.

  With Navattic A/B Tests, you can experiment with:

  * Gated vs. ungated demos
  * Which use cases to include in your demos
  * CTA color, modal text, and step variations

  Run A/B tests and view performance metrics side-by-side to find what works best. See [an interactive demo](https://navattic-website.navattic.com/u41n0yvg) on how to set up an A/B Test.

  This feature is available on our Growth and Enterprise plans. Please reach out to [success@navattic.com](mailto:success@navattic.com) to get set up.

  <Frame>
    <img alt="A/B Testing" />
  </Frame>

  ## Mobile Forms

  Capture lead information from your Mobile Swipe Demos.

  For any step in your Mobile Swipe Demo, choose Form and select any existing form in your workspace.

  <Frame>
    <img alt="" />
  </Frame>

  ## Export Form Submissions

  View and export form submissions directly in our new Forms Table to see all leads that filled out that form and which demo they filled out the form on.

  If you're using Interest-Level demos, you can also quickly see each submission's level of interest.

  <Frame>
    <img alt="" />
  </Frame>

  ## AI Up-to-Date

  Keep demos current by updating dates in old captures with today's date. Use AI Detection to help easily find and mass replace old dates hiding in your captures.

  <Frame>
    <img alt="" />
  </Frame>

  ## Custom Analytics Timeframes

  Compare and analyze demo performance for custom date ranges within the Analytics, Visitors, and Accounts views.

  To access custom timeframes, click the Analytics, Visitors or Accounts tab > select the timeframe in the top right corner.

  <Frame>
    <img alt="" />
  </Frame>
</Update>

<Update label="May 2025">
  ## AI Voiceover

  Enhance your demos with dynamic narration through various options, including reading from the individual steps, custom text-to-speech, or uploaded audio.

  To add voiceover to specific steps in your demo, in the Flow Builder click **Add element** > **Voiceover**. From here, use the dropdown to select the option you want to use:

  1. **Read from text**: Add in custom text to read from (\_tip: use this with an \_[*Invisible step*](/flows#0KIKW))
  2. **Read from step**: Read directly from the text in the Modal or Tooltip
  3. **Upload audio**: Upload audio files from your local storage. Supported formats include MP3, M4A, WAV, and MIDI files.

  ## Version Comparison

  Track changes at a glance across your Product Demos.

  With Demo Version Comparison, easily see what's changed between versions—whether text edits, step reordering, or updated captures—making it easier to review and approve updates.

  To view changes, you can either visit Versions or click the **Publish button** > **View changes**

  <Frame>
    <img alt="Version Comparison" />
  </Frame>

  ## Email Blacklisting

  Improve lead quality by blocking unwanted email domains from accessing your interactive demos.

  With Email Blacklisting, you can prevent Visitors with specified email domains from accessing gated demos or completing forms.

  To enable this feature, visit your Form Builder > select the **email** field > toggle on **Blacklisted Domains** > Add the domains you want to block.

  This feature is available for Growth and Enterprise workspaces.

  <Frame>
    <img alt="" />
  </Frame>

  ## Combined Media and Web Capture Collections

  Simplify your capture workflow with a unified Capture Collection system. All Captures, whether web-based or media uploads, now live together in a single, streamlined structure—making it easier to manage and edit your demos.

  No action required—your collections have already been updated.

  <Frame>
    <img />
  </Frame>
</Update>

<Update label="April 2025">
  ## HubSpot Meetings, Default, and RevenueHero Embed Step Types

  Expand your scheduling and conversion options inside demos.

  Embed HubSpot Meetings links, set a Default Scheduler, or integrate RevenueHero meeting links directly within your demos to drive faster booking.

  To add an embed, create a new **Embed Step** > Choose **HubSpot Meetings**, **Default**, or **RevenueHero** > Insert your scheduling link.

  <Frame>
    <img alt="HubSpot Meetings, Default, and RevenueHero Embed Step Types" />
  </Frame>

  ## Estimated Completion Time

  Set clear expectations for demo Visitors with estimated completion times.

  Automatically display how long a Flow or Checklist task will take, helping users plan and complete demos more efficiently.

  To enable estimated completion time, visit the Checklist builder > toggle on **Estimated completion time** under **Advanced**.

  <Frame>
    <img alt="" />
  </Frame>

  ## On Hover Tooltips

  Use the **On Hover Tooltip** setting to display tooltips automatically when users hover over anchor elements. This feature provides optional context while maintaining a clean and readable interface.

  Learn more about the [On Hover Tooltip Setting](/flows#mFtaZ).

  <Frame>
    <img alt="" />
  </Frame>
</Update>

<Update label="March 2025">
  ## Table AI

  Instantly update table values in bulk using simple AI-powered prompts.

  No more manual adjustments—describe the changes you need to make large-scale data edits. Keep your data accurate and up to date in seconds.

  To use Table AI, edit a Capture with a table > select the table element > click **Magic Editors** > **Table AI** > Write a prompt and click **Submit**.

  <Frame>
    <img alt="" />
  </Frame>

  ## Preserve Anchors when Replacing Captures

  Maintain anchor positions when replacing captures.

  Keep tooltips, beacons, and triggers precisely placed, simplifying demo updates when adding or replacing steps across your interactive demos.

  <Frame>
    <img alt="" />
  </Frame>

  ## Collection Global Edits

  Make edits once and automatically apply changes across all captures in a collection, quickly personalizing demos for different industries or personas.

  Whether updating text, images, or styling, keep demo styling and messaging consistent across all your captures.

  To apply bulk edits, open the Capture Editor > Make an edit to the Capture > Click **Save** > Select **Apply edits to collection** > **Confirm**.

  <Frame>
    <img alt="" />
  </Frame>

  ## AI Writing Assistant

  Create a first draft copy for your demo steps pulled directly from your captures.

  The AI Writing Assistant is trained on our interactive demo best practices to help you write an engaging and value-driven demo.

  To use the Writing Assistant, generate a Flow from a Capture Collection > Select **Use Writing Assistant** > Click **Next** > Enter a brief summary of what you'd like the demo to focus on > **Generate Flow**.

  Writing Assistant is an early-release feature. Contact [**success@navattic.com**](mailto:success@navattic.com) to enable this in your workspace.

  <Frame>
    <img alt="" />
  </Frame>

  ## Click-and-Drag Flow Reordering

  Get more flexibility with how you order flows within your demos.

  Rearrange demo flows by clicking and dragging steps directly on the Product Demo Flows page.

  Pair this with the [**Last step continue behavior**](/flows#bweW5) in the Flow Settings to automatically continue to the next Flow.

  <Frame>
    <img alt="" />
  </Frame>
</Update>

<Update label="February 2025">
  ## Updated Navattic Extension

  The updated [Navattic extension](https://chromewebstore.google.com/detail/navattic/lbecioncobbndebbfdopnpinnibemoon) streamlines the capture process, allowing you to see Capture snapshots, change step types, and edit step text in real-time.

  ## Sandbox Demos

  Nav Links allows you to apply the same Trigger or Beacon to identical elements across multiple steps, saving time and simplifying the process. Teams are using Nav Links to create lightweight sandbox environments for sales teams. Learn more about [Sandbox Demos]().

  Nav Links is an add-on feature. Contact [**success@navattic.com**](mailto:success@navattic.com) to enable this in your workspace.

  ## Navattic Academy

  View our new Navattic Academy, a learning hub featuring introductory courses designed to turn you into a Navattic Power User. Each course takes 30-60 minutes and includes how-to videos, written guides, and (of course) interactive demos. You'll learn the fundamentals of demo-building, best practices for various Navattic use cases, and how to integrate Navattic seamlessly with your tech stack.

  <Frame>
    <img alt="Navattic Academy" />
  </Frame>

  ## Skip Form Setting

  Add an optional setting to bypass or pre-fill a Navattic Form if a demo Visitor has already been identified.

  Learn more about [Form Settings]().

  <Frame>
    <img alt="Form Settings" />
  </Frame>
</Update>

<Update label="January 2025">
  ## Conditional Demos

  Add **Conditions** to your demo to allow Visitors to build their own demo experiences based on what matters most to them. Select from one or more interest areas to create a bespoke demo path for every Visitor. Teams can quickly convert an existing interactive demo with multiple Flows into a branching Conditional Demo using the Conditional Demos generator.

  ## Sidebar Checklist

  Using the sidebar layout, display your **Checklist** on the side of the demo to create a persistent guide for your Visitors. Also, keep your Visitors informed of other demo options or paths they can select from.

  Drive additional conversions directly from the Checklist with a CTA button in the Checklist footer.

  Learn more about [Checklists]().

  ## Generate Branded Theme

  Automatically generate a branded Theme using your website domain that matches your brand guidelines to expedite the demo creation process.

  To create a branded theme, visit **Themes** > **Generate branded theme** > Add your website > **Generate.** You can also choose between a Light or Dark mode and set this as the default Theme.

  ## Hide Internal Visitor Activity

  Use **Hidden Accounts** to exclude certain domains (including internal users) from Visitors, Accounts, and Analytics to declutter your workspace reporting.

  To set this up, visit **Settings** > **Hidden Accounts** > Add **Domains to exclude.**
</Update>

<Update label="December 2024">
  ## Video Step Type

  Create high-impact sales and marketing materials that resonate with your prospects by seamlessly combining video within interactive demos. With our new **Video Step** feature, you can easily incorporate videos into your demo experiences. Teams are leveraging this to showcase customer case studies, highlight key use cases, and present branded content.

  To add a video step, select **Video** from the Step type dropdown in the Flow Builder. Once you've added a Video step, you can click **+ Select video** to either upload a video from your local storage or insert a link from YouTube, Vimeo, Loom, Wistia, or Vidyard.

  ## Demo Voiceover

  Elevate your interactive demos by adding voiceovers to individual demo steps. Teams can now enhance their presentations with dynamic narration through various options, including reading from the individual steps, custom text-to-speech, or uploaded audio.

  To add a voiceover to specific steps in your demo, in the Flow Builder click **Add element** > **Voiceover**. From here, use the dropdown to select which option you want to use.

  <Frame>
    <img alt="Voiceover element" />
  </Frame>

  ## Add Guide Defaults in Workspace Settings

  Set workspace defaults for Step type, Backdrop, Navigation Buttons, and Escape View to build a consistent starting point for your team to build off of.

  To set guide defaults, visit your Workspace > **Settings** > **General** > **Flow Defaults**.
</Update>

<Update label="November 2024">
  ## Presenter Mode

  Activate **Presenter Mode** to easily control the visibility of modals and tooltips when presenting an interactive demo. When enabled, dialog boxes can be hidden or shown by the presenter using the keyboard shortcut **Ctrl + P**.

  To enable Presenter Mode, go to **Flow Settings** and toggle on **Presenter Mode**.

  ## Keyboard Navigation

  Keyboard navigation allows you to seamlessly progress through your interactive demo. When combined with Presenter Mode, it gives teams enhanced flexibility for live product demonstrations, providing presenters with greater control over the entire experience.

  To enable Keyboard Navigation, go to **Flow Settings** and toggle on **Keyboard Navigation**.

  ## Navattic JS

  Navattic JS is a JavaScript widget that can be installed on your web properties to help identify visitors and integrate with event-based analytics platforms.

  Navattic JS will allow you to quickly set up tracking for:

  * **Automatic third-party form submissions**
  * **Domain-level Visitor tracking**
  * **CRM Cookie Tracking**
  * **Track Query Parameters**

  Learn more about [Navattic JS](/navattic-js).

  ## Video Capture Advanced Options

  With Video Captures, you now have the ability to customize your video settings, including options to enable or disable autoplay, show playback controls, loop the video automatically, and toggle audio on or off.

  To access these settings, add your Video Capture to a Flow and click **Advanced.**
</Update>

<Update label="October 2024">
  ## Form builder

  The Navattic form builder allows teams to create custom lead capture forms with new field types and validation rules. Capture information like emails, names, titles, roles, etc. using new field types such as radio buttons, text input areas, and drop-down fields.

  Forms can now be re-used across Product Demos to standardize the lead capture process.

  Contact [**success@navattic.com**](mailto:success@navattic.com) if you don't have access to the New Form Builder yet and would like to try it out.

  ## **Export Demo as a Video or GIF**

  Export a preview of your Product Demo as a media file (video or GIF) to add to social channels and emails to drive engagement for a wider audience.

  To export your demo, click the three dots next to the Share button > **Export Preview** > Select **Video** or **GIF** and set the time per step > Click **Export**.

  <Frame>
    <img alt="" />
  </Frame>

  ## Launchpad

  Launchpad is a view only portal to your Navattic interactive demos. Organizations are using Launchpad to give sellers, partners, and customer success teams easy access to a defined set of interactive demos.

  From Launchpad, teams can easily create targeted share links for specific Visitors and Accounts to track demo engagement. These insights can be used to monitor interest and create targeted followups throughout the buyer journey.

  Launchpad is an add-on feature. Contact [**success@navattic.com**](mailto:success@navattic.com) to enable this in your workspace.

  <Frame>
    <img alt="Launchpad" />
  </Frame>
</Update>

<Update label="September 2024">
  ## Playbooks

  Playbooks are a combination of integration operations that are executed conditionally based on preconfigured Audiences. With Playbooks, you can now filter the Navattic Visitor and Account data that is sent to integrations by configuring different Audiences. For example, do you only want to send data for Repeat Visitors, Visitors who engage with specific demos, or Visitors from a specific industry?

  Learn more about [Playbooks]().

  <img alt="" />

  ## Audiences

  Now you can create Audiences which are filtered views of Visitors and Accounts that view your demos. These include filters for Time spent, Total sessions to detect repeat Visitors, Total steps, and more. With Playbooks, you can decide which Visitors and Accounts to send to your CRM.

  <Frame>
    <img alt="Audiences" />
  </Frame>

  ### Advanced Filters

  Advanced filters allow you to sort your Visitor and Account data using granular filters such as which share link they viewed, what city they are from, what year the company was founded and more. Pair Advanced Filters with Audiences and Playbooks to set up contact routing that matches your ICP.

  Advanced Filters are included in Navattic Growth and Enterprise plans. Contact [**success@navattic.com**](mailto:success@navattic.com) to enable this in your workspace.

  ## Share Link Email Notifications

  Toggle on Email notifications when creating a link to receive an email when a Visitor visits the share link or set up notifications for all demos under Integrations.

  Visit [Playbooks](/integrations/playbooks) to learn how to setup routing rules to email specific sales reps when Accounts matching their ICP view your demos.
</Update>

<Update label="August 2024">
  ## Build a Mobile Swipe Demo from a Flow

  Quickly create a Mobile Swipe Demo using the content from an existing flow in your demo.

  To create a Mobile Swipe Demo from a flow, visit your demo > **Mobile** > **Mobile swip demo** > **+ Copy from flow.** From here, select the steps you would like to include in the Mobile Swipe Demo and click **Create.**

  ## In-App Collaboration

  Now you can add comments directly in Navattic and tag other team members to collaborate seamlessly on the demo creation process. To add a comment, simply click on the conversation bubble above a step. If there is an unresolved comment, the conversation bubble will display a small orange dot.

  Collaboration is included in Navattic Growth and Enterprise plans. Contact [**success@navattic.com**](mailto:success@navattic.com) to enable this in your workspace.

  ## Auto Identify Visitors from Embedded Forms

  Navattic now automatically tracks submissions from embedded Hubspot and Marketo forms. These submissions can be found in [Visitors](/analyze#_MXGs). Learn how to add an [embedded third-party form](/flows#s-Gs6) directly in Navattic.
</Update>

<Update label="July 2024">
  ## New Product Demo Page Layout

  We enhanced the product demo creation process by simplifying the page layout, making it easy to understand the necessary steps for building your demo.

  ## Add Annotations to Steps while Capturing

  Speed up your demo building process by adding annotations and step settings as you take captures from the Navattic Chrome extension. We recommend using this with the [On Click feature](https://www.loom.com/share/d4cef5b1500248b19546df3f8384ae43?t=53\&sid=2d4eb252-25ca-4367-8556-cd5ab4f6ca01), which automatically anchors tooltips to selected elements, drastically speeding up the demo creation process.

  ## Enhanced Accessibility Upgrades

  Add custom ARIA (used for accessibility and screen readers) descriptions for tooltips, beacons, and trigger elements. We also added additional accessibility settings from Themes to update focus selector color and width.

  <Frame>
    <img />
  </Frame>

  ## Add Tracking params to URL actions

  We added optional tracking parameters to automatically add a UTM **Source** parameter to buttons using the "Navigate to URL" action.
</Update>

<Update label="June 2024">
  ## Mobile on Mobile

  Toggling on **Fullscreen** in the Mobile Swipe Editor allows images that are taller than they are wide to fill the entire screen. This feature now enables you to seamlessly create Mobile-on-Mobile demo experiences.

  Additionally, you can now enable Auto Progress for your Mobile Swipe Demo, which will automatically guide visitors through the demo. To turn on Auto Progess select Advanced Options > toggle on Auto Progress.

  <Frame>
    <img />
  </Frame>

  ## Pop up Embed Option

  You can now embed your demo as a lightbox pop-up directly from Navattic. To embed a pop-up, visit your demo > Embed > Pop up > Get embed code.

  ## Highest Performing Demos

  You can now identify your highest performing demos in Analytics. Simply visit Analytics and select "Compare: **Highest Performing Demos**" from the dropdown menu to view your top five demos for each section.

  <Frame>
    <img />
  </Frame>

  ## Offline Demos

  The Offline feature lets you download demos into your local Navattic app, accessible on Windows/Linux, macOS, and iPad without an internet connection. This enables easy access to your demos at conferences, trade shows, on-site customer visits, and more.

  Offline Demos is an add-on feature. Reach out to [success@navattic.com](mailto:success@navattic.com) to learn more.
</Update>

<Update label="May 2024">
  ## Mobile Swipe demos

  The Mobile swipe demo is used to engage your mobile visitors with a short and visual experience they can *swipe* through. To create a mobile swipe experience visit your demo > Build > Mobile > Mobile swipe demo > Navigate to swipe editor.

  Check out [this demo](https://training.navattic.com/o3bq0xrd) to learn more about Navattic's mobile options, including how to build a mobile swipe experience.

  <Frame>
    <img />
  </Frame>

  ## Demo Suggestions

  With more than 20,000 interactive demos built on our platform - we looked at the **top 1%** to understand what top-performing interactive demos had in common. Leveraging this research, our automated demo suggestions provide insights, allowing you to integrate best practices into your demo creation process.

  ## Set a Product Demo Theme

  <Note>
    We recommend applying a single theme across your demo to maintain consistency.
  </Note>

  You can now seamlessly apply a single theme throughout your entire demo or select a different theme for each flow. To select a single theme or choose a mix of themes visit a demo > Build > Theme.

  ## Marketo Form Embed Step

  You can now embed a Marketo form directly into your demo. To add a Marketo form select Embed as the step type > Marketo Form.
</Update>

<Update label="April 2024">
  ## Pardot Integration

  The Pardot integration is used to send real-time activity from visitors. Use this engagement data to create Pardot dashboards and automations.

  To set up your Pardot Integration, visit Integrations > Pardot > Connect. Visit [this demo](https://training.navattic.com/hf1oz0d24) to learn more about setting up the Pardot Integration.

  ## Capture from the Chrome Extension

  Streamline your capture workflow to create new Product Demos or update existing capture collections directly from the Navattic Chrome Extension.

  To capture from the Chrome Extension > Go to your app > Open the Navattic Chrome Extension > Select "New demo" or "Add to demo".

  ## Hubspot Form Embed Step

  You can now embed a [Hubspot form](/build) directly into your demo. To add a Hubspot form select Embed as the step type > Hubspot Form.
</Update>

<Update label="March 2024">
  ## Directory Sync

  Admins can now easily add and remove Navattic workspace members directly from a unified User Lifecycle Management process (a directory).

  **Set up Directory Sync to automate:**

  * Provisioning new users
  * Updating user attributes such as name and email
  * Deprovisioning users who leave your directory

  Navattic partners with WorkOS to support all major providers including [Okta SCIM](https://workos.com/docs/integrations/okta-scim), [JumpCloud SCIM](https://workos.com/docs/integrations/jumpcloud-scim), [OneLogin SCIM](https://workos.com/docs/integrations/onelogin-scim), [Rippling SCIM](https://workos.com/docs/integrations/rippling-scim), and [more](https://workos.com/docs/integrations).

  Directory Sync is included in Navattic Growth and Enterprise plans.

  <Frame>
    <img />
  </Frame>

  ## Beacons Reveal Hotkey

  Effortlessly create demos to assist sales-led presentations by combining [Click to Capture](https://www.loom.com/share/b2999aa772c442bea316e758fe2b496d?sid=8a7b897f-d175-4782-bfad-cc48599afed0) with the Beacons reveal hotkey feature. When this is enabled, Beacons will be hidden in this demo by default and may only be revealed if a demo visitor or presenter presses Ctrl + B on the keyboard.

  To turn on the Beacons reveal hotkey, visit the Flow settings > Beacons reveal hotkey. Once enabled, toggle beacons on and off using "Ctrl + B".

  <Frame>
    <img />
  </Frame>

  ## Bulk Editor

  With the Bulk Editor, you can apply edits across multiple steps at once. Bulk edits include:

  * Updating all beacons to triggers
  * Turning multiple modals into tooltips
  * Changing all beacons to have a highlight appearance instead of pulse
  * Deleting multipe beacons or triggers at the same time
  * and more!

  [View a 2-minute tutorial here](https://www.loom.com/share/eed1f37b07cf4a1e9f1082d2021cee0e?sid=3d83d4e7-56fc-43f4-af70-8c19d91ca2c3)
</Update>

<Update label="February 2024">
  ## Compare Product Demo Analytics

  To compare the Analytics of two Product Demos, visit Analytics > Compare: > Product demos > Select project 1 and Select project 2. You can also adjust the time period you would like to view using the calendar drop down. One of your projects will have a blue dot and one will have a gray dot next to the title which is the graph key.

  <Frame>
    <img alt="" />
  </Frame>

  ## Pin Demos to the Top of a Board

  To pin a demo to the top of a board, visit Product Demos > Select three dots (...) on the demo you want to pin > Pin to top. Your demo will now show up at the top of your board with a pin. To unpin a demo, select three dots (...) > Unpin.

  ## Video Captures

  Media captures now include a video option. To upload a video as a capture, visit your Product Demo > Captures > New > Media > Create > Add to Collection > Add .MP4 video files up to 40MB. See an [example](https://training.navattic.com/tp2e0vbm) of a demo that uses Video captures.
</Update>

<Update label="January 2024">
  ## Jump to a Step Action

  Add **Jump to a step** to any Beacon, Trigger, or Button in your flow to allow visitors to skip forwards or backward within your flow. Jump to a step can be paired with other click actions such as "Navigate to URL" or "Mark as Converted".

  ## Time-Based Progression

  Set a Timer Condition to any Trigger to have a step automatically progress to the next action. Adding a timer trigger can be useful in email outreach or conference use cases, where you want the demo to progress without requiring end-user interactions.

  A Timer condition can be used to perform any trigger action including "Go to next step", "Go back a step", "Navigate to url", etc.

  To add a Timer Condition, select **+ Select trigger condition** > **+** **Add condition** > **Timer**

  ## Click to Capture

  Use Click to Capture to combine the Capturing and Flow-building process into just one step ([tutorial](https://www.loom.com/share/bcd89ecea12d4bcc9fc50b1f54c70466)). When this feature is activated, you will see the note *"Shift + click an element to Capture"* present as you take Captures using the Navattic Chrome Extension.

  ## Adobe Analytics Integration

  Navattic now supports sending demo engagement data (ex. "step viewed", "flow started") to Adobe Analytics. Learn more about embed events [here](/tracking/navattic-js/subscribe-to-events).
</Update>

<Update label="December 2023">
  ## Edit Captures with Up-to-Date

  Change the date and time on your capture to be today's exact date minus a set amount. Visit your capture > Edit > Select element > Magic Editors > Up-to-date > Offset > Make up-to-date. To automatically convert all detected dates at once visit your capture > Edit > Select element > Magic Editors > Auto-detect > Offset > Convert all dates.

  ## Update Demo Version Titles and Descriptions

  Keep track of the versions of your Product Demo by editing the title and adding a description. To update the version titles and descriptions visit your Product Demo > Versions > 3 dots (...) > Edit details.

  ## Embed Step Type

  Product demos now support embedded calendar links. From the Flow Builder, set your last step to be an Embed and simply include your Calendly or Chili Piper URL. When the scheduling form is completed, visitors will advance to the next step.

  <MediaCard type="demo" title="2023 Updates" />

  ## Lazy Load Overlay

  Turn on a "lazy load overlay" for any demos that are embedded on your website to reduce page load times and speed up landing performance. This is an optional setting that may be found within your demos > Share > Website Embed > "Lazy load overlay".
</Update>

<Update label="October 2023">
  ## Product Demos

  We are excited to release a new user interface that makes building and maintaining your interactive demos easier than ever. Contact\*\* [success@navattic.com](mailto:success@navattic.com)\*\* to request early access and visit the [setup guide](/build/demo) for more information.**For existing Navattic customers, this upgraded user interface provides: \*** A quicker way to build new demos

  * Fewer workspace assets to label and organize
  * Easy access to the relevant Flows and Checklists for published demos
  * Ability to Preview and Restore previous versions of your demo
  * Search for any workspace asset with the keyboard shortcut Ctrl + K
  * New customization options in the Flow builder (resizing Beacons and Tooltips!)

  <MediaCard type="demo" title="2023 Updates" />

  ## Slack Integration

  Visit Navattic > Integrations to find the new Slack integration option! Use this to notify a designated Slack channel of new Leads or Accounts that are created in your Navattic workspace. \* Leads are created when visitors fill out a form

  * Accounts are created with Navattic's Account-Based Engagement feature

  <MediaCard type="demo" title="2023 Updates" />

  ## Add a Watermark to Themes

  Add a custom Watermark to all Tooltips and Modals within your demo. Visit Themes > **Watermark** to upload an image to be used in Modals and Tooltips, and set your watermark's position, CTA link, and opacity.

  ## Add a CTA Banner to Themes

  First, use our in-app chat or contact [success@navattic.com](mailto:success@navattic.com) to request early access to this feature. Then, visit Themes > **Banner** to create a custom CTA Banner for your demos. Customize the banner's colors, text, and linked resources. Publish & Exit to add your banner to existing projects.
</Update>

<Update label="September 2023">
  ## Upload Custom Fonts

  Themes now supports custom font uploads. Within Navattic > Themes > Font, you may now select from our existing library, add a CSS URL, or upload a font file up to 5MB.

  ## Visitors Engagement Details

  View more engagement details for your demo visitors including UTM tracking attributes. Export your data as a CSV or send leads directly to a CRM using [Navattic integrations.](/integrations)

  <MediaCard type="demo" title="2023 Updates" />
</Update>

<Update label="August 2023">
  ## HubSpot Event Timeline

  View all demo events directly in your HubSpot timeline. Track form fills, flows started, step views, and conversion events as part of the larger customer journey within HubSpot. To activate this view, simply re-authenticate your HubSpot integration from the [in-app Integrations menu](https://app.navattic.com/n/integrations) and re-connect your projects.

  <img alt={true} />
</Update>

<Update label="July 2023">
  ## Text and Image Find and Replace

  Make mass text or image updates to a single capture or across an entire collection. Visit the Navattic Capture Editor --> Magic Editors --> **Find and Replace** to apply text or image updates throughout a single Capture. Toggle on "Global" to apply these changes across all Captures in the current Collection.

  <Frame>
    <img alt={true} />
  </Frame>
</Update>

<Update label="June 2023">
  ## Analytics Dashboard

  Visit the **Analytics** tab in your Navattic workspace to view demo engagement trends over time. Filter the dashboard by Project or Timeframe to see: \* Total unique visitors, Engaged visitors (i.e., visitors who advance 1+ steps in your demo), and Converted visitors (i.e., visitors who click a CTA button in your demo)

  * Time spent per session, click-through rates, and total steps viewed
    <Frame>
      <img alt="Navatic Analytics Dashboard" />
    </Frame>
</Update>

<Update label="May 2023">
  ## Send Navattic Embed Events to any event-based platform

  Customers may now send Navattic event data to any [event-based analytics platform](https://amplitude.com/blog/event-based-analytics) like Amplitude, PostHog, and Mixpanel.

  **Background**: Navattic events include when a visitor views a step, starts a new flow, clicks a CTA, and [more](/tracking/navattic-js/subscribe-to-events).

  Event-based analytics platforms are used to analyze how users interact with your website, and may receive Navattic events similar to how they receive other website events.

  **Event-based platform may help answer questions like**:

  * How many users or sessions engage with my Navattic demo?
  * Where in my website flow do users engage with my Navattic demos?
  * Which of my Navattic projects lead to the most conversions?

  **Set this up using our**

  [**Embed Events Integration setup guide**](/tracking/navattic-js/subscribe-to-events) **.**

  ## Sync Leads to Salesforce Contacts

  Our Salesforce integration users now have the option of syncing Lead engagement data to the associated Contact if a matching email is found. Engagement data can be pushed to pre-created Salesforce fields.
</Update>

<Update label="April 2023">
  ## Google Analytics 4 Integration

  Use our new GA4 integration to combine demo engagement data with your other website event data. Read the [Google Analytics (GA4)]() integration guide to set this up.

  Use this to answer questions like:

  * How many users or sessions engage with my demo?
  * Where in my website flow do users engage with my demos?
  * Which of my projects lead to the most conversions?

  <Frame>
    <img />
  </Frame>

  ## Overlay Detection

  When editing a capture, ignore an overlay to edit content in the background of the capture.

  ## Canvas Element Freeselector

  Set a target anchor element on canvas graphics (ex. an interactive map area or graph). Freely select the desired area and size to target a specific hotspot for user attention or in-demo action.
</Update>

<Update label="March 2023">
  ## Share Link Identification and Personalization

  Track how a specific prospect interacts with your demo without needing a form fill. Apply personalization variables to a demo Share Link to identify the user accessing the product demo URL. These identification traits will get passed into  [Visitor Analytics.](/analyze#mPvnt) Learn more about [Personalization]().

  ## Expire Project Share Links

  Set an expiration date for project share links. Provide viewers access for a limited time frame to help accelerate deal timelines.

  ## Identify Visitors with Project Share Links

  Add your recipient's name, company, and/or email to a project share link to help identify their Visitor data in Navattic (no formgates needed). Use [Personalization]() to reference these variables throughout the demo as well (ex. "Hi, firstname!")

  <MediaCard type="video" title="2023 Updates" />

  ## Add Audio Clips in Flows

  Add audio files to Modals and Tooltips to help walk your prospects through your interactive demo. To activate this feature in your workspace, please reach out to your Navattic CSM.
</Update>

<Update label="February 2023">
  ## Visitor Time Tracking

  See how much time Visitors actively spend in a demo, within a Flow, or on an individual Step. Time tracking excludes idle time spent away from the demo tab. The Visitors page also includes information on device dimensions, completed Flows, and key actions like navigating to a URL during the demo.

  ## Anchor Element Traversal

  When building a Flow, use anchor element traversal to anchor Tooltips, Triggers, and Beacons with greater precision.

  ## Embed on G2 or TrustRadius

  Meet your prospects where they are and embed your Navattic demo on TrustRadius. Increase buyer engagement and showcase your solution without the friction of a demo call or trial setup.G2 embed demos will be automatically optimized for the G2 embed profile. G2 Essentials plan members and all TrustRadius members can embed a Navattic product tour on their profile. See more in our recent blog post [here](https://www.navattic.com/blog/software-review-platform-interactive-demos).
</Update>

<Update label="January 2023">
  ## Drag and Drop Images

  Drag and drop images into a Modal or Tooltip, or upload an image directly from your desktop. Resize and realign images directly within the Navattic Flow Builder.

  ## Set Guide Defaults in Themes

  Frequently changing Modals to Tooltips or adding Navigation Buttons in Flow Settings? Now you can set Guide Defaults via Themes. Determine if your Theme will automatically include:\* Modals, Tooltips, Forms, or Invisible Steps

  * Backdrops
  * Navigation buttons and Step Progress
  * Escape View

  ## Password Protect Demos

  Navattic demos can now be password protected! Open your Project Link settings to set a passcode on a project sharing link. This helps manage the audience for your demos.

  ## Reposition Modals

  Move modal steps to different positions on the screen to unblock key elements on the page. Choose from the middle of the page or various corners for optimal positioning.Remember, [Tooltips](/build#XBSdQ) can be anchored to individual on-screen elements for even more customized placement.
</Update>


# Ask Navattic
Source: https://docs.navattic.com/copilot/ask-navattic

Ask questions about your workspace data and get AI-powered answers directly in the dashboard.

Ask Navattic is an AI assistant embedded in the Navattic dashboard. Use it to query your workspace data — demo performance, visitor engagement, accounts, and referrer sources — without leaving the app. You can also ask product how-to questions, and Ask Navattic will cite the relevant documentation.

## Accessing Ask Navattic

Click the **Ask** button in the top navigation bar to open the Ask Navattic sidebar. Type your question and press **Enter** or click **Send**.

<Note>
  Ask Navattic is available on Starter plan and above. Contact your account manager if you don't see the Ask button in your workspace.
</Note>

## What you can ask

Ask Navattic can answer two types of questions:

**Workspace data questions** — questions about your demos and engagement metrics, such as:

* "How many visitors viewed my product tour last month?"
* "Which demos have the highest completion rate?"
* "Show me accounts that engaged with the onboarding demo this week."
* "What are the top referrer sources for my demos?"
* "Which visitors from Acme Corp have viewed demos in the last 30 days?"
* "What's the average session length for my pricing page demo?"

**Product how-to questions** — questions about Navattic features and capabilities, such as:

* "How do I add a CTA button to a tooltip?"
* "What's the difference between a web capture and a media capture?"
* "How do I set up a personalized demo?"
* "How do I invite someone to my workspace?"

For how-to questions, Ask Navattic searches the documentation and includes links to the relevant pages in its response.

## Using skills

Skills are pre-configured playbooks set up for your workspace. They focus Ask Navattic on a specific task — for example, summarizing a demo's performance or generating a prospect report.

To use a skill, type `/` in the composer. A menu appears listing the available skills in your workspace, each shown with its name and description. Select a skill to load it, then send your message as usual — Ask Navattic starts the conversation with that skill's context already applied.

The skills available to you depend on what has been configured for your workspace. Contact your workspace admin if you don't see any skills listed when you type `/`.

## How it works

Ask Navattic connects to your workspace using the same tools that power Navattic's external AI integrations. It reads analytics, demo browsing data, and personalization settings scoped to your workspace — it cannot access data from other workspaces.

Each conversation is maintained for the session. You can continue asking follow-up questions and Ask Navattic will reference the context from earlier in the conversation.

## What data Ask Navattic can access

Ask Navattic has read-only access to three categories of workspace data:

**Analytics**

Demo performance metrics and visitor engagement data — views, session counts, completion rates, click-through rates, and referrer sources. Ask Navattic can also surface visitor-level and account-level details, including session history, demos viewed, and firmographic data such as company, industry, and employee count. You can filter by demo, company, location, and custom properties.

**Demo library**

Your workspace's projects, flows, and share links. Ask Navattic can describe the content and structure of any demo in your workspace and tell you which share links are configured for each project.

**Personalization**

Custom properties set up for visitor personalization.

Ask Navattic cannot access billing information, team member details, or administrative settings, and it cannot make any changes to your workspace.

## Contacting support

If Ask Navattic cannot answer your question, or if you'd prefer to speak with a person, ask to connect with the support team — for example, "Can I talk to someone?" or "I need help from a human." Ask Navattic will show a support card you can use to open a request with the Navattic team.

## FAQs

<AccordionGroup>
  <Accordion title="Can Ask Navattic make changes to my workspace?">
    No. Ask Navattic has read-only access to your workspace data. It can retrieve analytics, browse demos, and read personalization settings, but it cannot create, edit, or delete anything in your workspace.
  </Accordion>

  <Accordion title="Does Ask Navattic have access to all my workspace data?">
    Ask Navattic can access analytics, demo browsing data, and personalization data for your workspace. It does not have access to billing, team member details, or administrative settings.
  </Accordion>

  <Accordion title="Is my conversation history saved?">
    Ask Navattic maintains context within the current session. Previous sessions are accessible through the chat history, but each new session starts fresh.
  </Accordion>

  <Accordion title="What plan do I need to use Ask Navattic?">
    Ask Navattic is available on Starter plan and above. Contact your account manager if you don't see it in your workspace.
  </Accordion>
</AccordionGroup>


# Generate
Source: https://docs.navattic.com/copilot/generate

Instantly spin up demos by clicking through your product.

Copilot Generate is an AI assistant that works behind the scenes as you build your demo. Just select your use case, click through your product, and Copilot automatically writes demo copy, anchors tooltips, and crafts a compelling demo story. Instead of manually writing tooltip text, modal content, and step descriptions, Copilot analyzes your captures and generates relevant, engaging content tailored to your audience.

<Frame>
  <img alt="Copilot generating demo content" />
</Frame>

## How It Works

The click areas you create during the capture process are passed to Copilot as anchors. These anchors help Copilot understand which areas of each capture are important, so it can write content that highlights the right features and guides viewers to the correct elements.

You can use Copilot Generate in two ways:

* **When creating a new Product Demo** - Enable Copilot during the demo creation process
* **From existing captures** - Create a new flow from captures you've already taken

When creating a new flow or demo, enable Copilot to write your demo content automatically:

1. **Select your captures** - Choose the captures you want to include in your flow
2. **Enable Copilot** - Toggle on "Use Copilot to write demo content"
3. **Choose a use case** - Select from your configured use cases (e.g., Product Tour, Feature Highlight, Onboarding)
4. **Add context (optional)** - Click the pencil icon to open the context field and provide additional instructions to guide the AI, such as target audience, tone, or specific messaging. Available on all plans.
5. **Generate** - Copilot will analyze your use case and captures and generate appropriate content for each step

<Frame>
  <img alt="Create demo with Copilot enabled" />
</Frame>

## Automatic URL Reading

When you generate a flow, Copilot automatically reads the URLs from your captures to understand your product in context. This means Copilot can pull in real product details -- feature names, navigation labels, and page content -- directly from your live application.

For example, if your captures include a docs page or pricing page, Copilot will reference the actual content on those pages to write more accurate, relevant demo copy. No need to manually describe your product -- Copilot reads it directly from the source.

This works automatically with any URL your captures were taken from. The more pages you capture, the more context Copilot has to work with.

## What Copilot Generates

* **Step titles and descriptions** - Clear, action-oriented text that guides viewers through your demo
* **Tooltip and modal content** - Contextual explanations that highlight key features
* **Button text** - Engaging calls-to-action that encourage progression
* **Step appearance recommendations** - Suggestions for whether each step should be a tooltip, modal, or capture only

## Use Cases

Use cases are predefined contexts that guide how Copilot generates demo content. When you select a use case, it shapes the writing style, tone, step content, and call-to-action suggestions to match your intended audience.

<Frame>
  <img alt="Use case selection in Copilot" />
</Frame>

### Default Use Cases

Navattic includes four default use cases:

| Use Case             | Audience                    | Focus                                                                                               |
| -------------------- | --------------------------- | --------------------------------------------------------------------------------------------------- |
| **Marketing**        | Website visitors, prospects | Concise, compelling steps that communicate product value, emphasize benefits, and drive conversions |
| **Sales**            | Potential buyers            | Conversational tone showcasing value moments, ROI, and real-world applications                      |
| **Customer Success** | Existing customers          | Simple, instructional steps that help users quickly understand how to resolve common issues         |
| **Product**          | Technical evaluators        | Highlights core functionality, user workflows, and technical capabilities                           |

### Custom Use Cases

<Info>Custom use cases are available on Base, Growth, and Enterprise plans. Please reach out to your account manager or [support@navattic.com](mailto:support@navattic.com) to learn more.</Info>

While four defaults are available, you can create custom use cases for your workspace. This allows your team to define specific personas, content guidelines, and brand requirements that Copilot will follow when generating content.

## Brand and Tone

Copilot Generate uses your workspace's Brand and Tone settings to match your voice across all generated content. Navigate to **Settings > Copilot** to configure three key fields:

* **Brand and Tone** - Define your writing style, formality level, and vocabulary preferences. Use the suggestion chips (e.g., Conversational, Professional, Action-oriented) to quickly build your voice profile, or type your own guidelines.
* **Product Context** - Describe what your product does, key features, value proposition, and specific terminology your team uses.
* **Go-to-Market Context** - Provide details about your sales motion, CTA language, pricing model, and target audience.

Each field has a maximum of 10,000 characters. A counter below each field turns amber as you approach the limit and red when you reach it.

<Info>Brand and Tone settings are available on Base, Growth, and Enterprise plans.</Info>

Once configured, these settings apply across all Copilot features -- Generate, Review, and Prompt -- so every AI-assisted action stays on-brand.

### Uploading context

Instead of filling in the fields manually, you can have Copilot extract context for you from a website or a document. Click **Upload context** at the top of the Settings > Copilot page to open the upload modal.

<Steps>
  <Step title="Choose your source">
    Select **Website** to paste a URL (for example, your pricing or product page), or select **File** to upload a document such as a PDF, Word document, or text file. Copilot reads the content and extracts relevant brand voice, product context, and go-to-market context.
  </Step>

  <Step title="Generate">
    Click **Generate**. Copilot scans the source and extracts structured content into the three context fields. This usually takes a few seconds.
  </Step>

  <Step title="Review and edit">
    Before anything is saved, Copilot shows you the extracted content so you can review and edit it. Make any adjustments, then continue.
  </Step>

  <Step title="Apply">
    If your workspace already has context saved, choose whether to **Replace** the existing content or **Merge** the new content with what's already there. Click **Apply context** to save.
  </Step>
</Steps>

<Tip>
  For the best results, point Copilot at a page that describes your product clearly — a homepage, pricing page, or product overview works well. For file uploads, use documents that contain product descriptions, messaging guides, or sales playbooks.
</Tip>

## Automatic demo titles

When you publish a demo without a name, Copilot automatically generates a title based on the content of your steps. The title appears in the demo breadcrumb right after publishing — no page reload required.

To give your demo a custom name before publishing, click the demo title in the breadcrumb at the top of the builder and type a name.

<Note>
  Automatic demo titles require Copilot to be enabled on your workspace. Contact your account manager to learn more.
</Note>

## Best Practices

* **Provide context** - The more context you give Copilot about your audience and goals, the better the generated content will be
* **Review and refine** - Always review generated content and make adjustments to match your brand voice
* **Configure Brand and Tone** - Set up your brand voice, product context, and GTM strategy in **Settings > Copilot** so Copilot generates on-brand content from the start
* **Capture key pages** - Since Copilot reads your capture URLs, capturing product pages with rich content (docs, feature pages, pricing) gives it more to work with
* **Use appropriate use cases** - Setting up use cases with brand guidelines helps Copilot generate more consistent content


# Prompt
Source: https://docs.navattic.com/copilot/prompt

Make bulk changes to step names, content, CTAs, and more using natural language.

<Info>Copilot Prompt is available on Base, Growth, and Enterprise plans. Please reach out to your account manager or [support@navattic.com](mailto:support@navattic.com) to learn more.</Info>

Copilot Prompt is a conversational AI assistant that lets you update, polish, and repurpose your demos using natural language. Make bulk changes to step names, content, CTAs, and more to cut down on time spent manual editing. Instead of clicking through menus and options, simply describe what you want to change and Copilot will suggest specific edits you can apply with one click.

<Frame>
  <img alt="Copilot Prompt suggestions" />
</Frame>

## How to Use Copilot Prompt

1. Open a flow in the builder
2. Click the **More actions** menu (three dots) > **Copilot Prompt** or use the keyboard shortcut **Cmd/Ctrl + ;** to open the prompt interface
3. Type your request in natural language (e.g., "Make the button text more engaging" or "Add a welcome step at the beginning")
4. Optionally, select specific steps to target your changes
5. Press **Enter** to submit your prompt
6. Review the suggested changes and apply or discard each one

<Frame>
  <img alt="Creating a prompt in Copilot" />
</Frame>

## Targeting Specific Steps

You can scope your prompts to specific steps:

1. Click **Select steps** in the prompt bar or type **@** to mention a step
2. Click on the steps you want to target in the flow preview
3. Selected steps appear as chips in the prompt bar
4. Your prompt will only affect the selected steps

This is useful when you want to:

* Update content on just a few steps
* Rename specific steps
* Modify buttons on particular steps

## Adding Files for Context

You can upload documents to give Copilot additional context when making changes. This is useful when you want to align demo content with existing materials like product briefs, messaging guides, or feature documentation.

To add a file:

1. Click the **menu** in the prompt bar
2. Select **Add file for context**
3. Choose a file from your computer

Supported formats: **PDF**, **TXT**, **Markdown**, and **DOCX** (up to 512 MB). Once uploaded, the file appears as a chip in the prompt bar. Copilot will reference the file's content when generating suggestions, so your demo copy can pull directly from your source material.

## What Copilot Prompt can do

<Tip>We are always adding new capabilities. Check back for updates or reach out to [support@navattic.com](mailto:support@navattic.com).</Tip>

### Step content

* Rewrite or update the text in a modal or tooltip
* Rename steps
* Change tone (professional, casual, technical, etc.)
* Translate content to another language
* Shorten or expand descriptions
* Add or update presenter notes

### Steps

* Add a new step at any position in the flow
* Remove a step
* Reorder steps
* Change a step's type (modal, tooltip, video, capture only)
* Move a modal to a different screen position (center, corner, etc.)
* Move a tooltip to a different position relative to its anchor

### Buttons

* Add or remove buttons on a step
* Update button text
* Change a button's action (go to a specific step, open a URL, close the flow, complete the flow)
* Change button style (primary or secondary)
* Reorder buttons
* Show or hide the **Next** and **Back** navigation buttons per step, or enable/disable them for the entire flow

### Backdrop

* Add or remove a backdrop on a tooltip step
* Set backdrop intensity (light, medium, or heavy)

### Beacons and triggers

* Add or remove beacons (pulsing hotspot indicators)
* Add or remove click, hover, or timer triggers

### Voiceover

* Add voiceover narration to a step from text
* Update or remove voiceover from a step

### Video

* Add a video to a step from a URL (YouTube, Vimeo, Loom, Wistia, or Vidyard)
* Remove a video from a step

### Flow-level settings

* Update the escape view message and buttons
* Add or update the complete button text
* Enable or disable presenter mode for the flow

## Reviewing Suggested Changes

After submitting a prompt, Copilot presents its suggestions in a panel:

* **Summary** - A brief explanation of what Copilot understood and planned
* **Changes list** - Each proposed change as an expandable item showing:
  * The type of change (content update, new step, rename, etc.)
  * Which step is affected
  * A preview of the before/after content
  * Apply and Discard buttons

## Applying Changes

For each suggestion:

* **Apply** - Implements the change immediately in your flow
* **Discard** - Ignores the suggestion

Bulk actions:

* **Apply all** - Accepts all pending changes at once
* **Discard all** - Dismisses all pending changes

## Multi-Turn Conversations

Copilot Prompt supports follow-up messages, so you can:

* Refine suggestions ("Make it shorter")
* Request additional changes ("Now do the same for the next step")
* Ask for alternatives ("Try a different approach")

Your conversation history is preserved, and Copilot remembers which changes you've already applied or discarded.

## Example prompts

* "Rewrite all the step content to be more concise"
* "Add a welcome modal at the beginning that introduces the product"
* "Make the button text more action-oriented"
* "Change the tone to be more professional"
* "Rename steps 2-4 to better describe what they show"
* "Remove the last step"
* "Update the CTA on step 3 to say 'Get Started'"
* "Generate copy for a new use case targeting enterprise buyers"
* "Add a beacon to step 4"
* "Add voiceover to step 2 explaining this feature"
* "Turn step 3 into a tooltip"
* "Hide the back button on the first step"
* "Enable navigation buttons for the whole flow"
* "Add a medium backdrop to step 5"


# Review
Source: https://docs.navattic.com/copilot/review

Get an AI demo score based on highest-performing benchmarks and one-click apply suggestions.

<Info>Copilot Review is available on Base, Growth, and Enterprise plans. Please reach out to your account manager or [support@navattic.com](mailto:support@navattic.com) to learn more.</Info>

Copilot Review analyzes your demo for structure, clarity, and engagement—then lets you one-click apply suggestions. It scores your demo against our highest-performing benchmarks and provides actionable feedback to help you create more engaging, polished experiences before sharing with your audience.

<Frame>
  <img alt="Copilot review results with quality score" />
</Frame>

## How to Run a Review

You can run reviews at two levels:

* **Product Demo level** - Review all flows in your demo at once from the demo overview
* **Flow level** - Review a single flow from within the flow builder

To start a review:

1. Open your demo or flow in the builder
2. Click the **Review** button in the header
3. Click **Start review** to begin the analysis
4. Copilot will analyze your content and generate a quality score along with specific suggestions

<Frame>
  <img alt="Starting a Copilot review" />
</Frame>

## Understanding Your Review

### Quality Score

Your demo receives an overall quality score based on our highest-performing benchmarks, reflecting structure, clarity, and engagement potential. Scores are categorized as:

* **Excellent**
* **Good**
* **Needs Improvement**

### Summary

A brief overview of your demo's strengths and areas for improvement.

### Suggestions by Flow

Suggestions are organized by flow, showing how many are pending, accepted, or rejected for each. Click into any flow to see and act on specific suggestions.

## Types of Suggestions

Copilot Review identifies opportunities across several categories:

### Content Improvements

* **Improve Writing** - Suggestions to make text more concise and action-oriented
* **Fix Grammar** - Corrections for grammatical errors
* **Fix Tone** - Adjustments to match your desired professional or casual tone
* **Improve CTA** - Better call-to-action text for buttons

### Data & Personalization

* **Personalize Content** - Opportunities to add personalization variables (like company name or user name)
* **Refresh Dates** - Outdated dates that should show relative or current times

### Visual & Technical

* **Remove Overlay** - Distracting elements (like cookie banners) that should be hidden
* **Animate Text** - Elements that would benefit from typewriter-style animations
* **Edit Table/Chart** - Data visualizations that could be improved

## Acting on Suggestions

<Frame>
  <img alt="Reviewing suggestions in a flow" />
</Frame>

For each suggestion, you can:

* **Accept** - Apply the recommended change to your demo
* **Dismiss** - Ignore the suggestion if it doesn't apply
* **Apply All** - Accept all pending suggestions at once
* **Dismiss All** - Clear all pending suggestions

## Review History

Copilot saves your review history, so you can:

* Compare quality scores over time
* See which suggestions you've acted on
* Run new reviews after making changes to track improvement


# Interest demos
Source: https://docs.navattic.com/demos/interest

Unlock a powerful insight - what features your visitors are interested in.

<Frame>
  <img alt="Interest areas" />
</Frame>

## Interest Area demos

We recommend leveraging <Icon icon="square-check-big" /> **Interest Areas demos** on your marketing site to better understand what features visitors are exploring. These insights can help you optimize messaging, prioritize campaigns, and personalize follow-up based on real user behavior.

Interest area demos improve the experience for both website visitors and marketers:

<Tabs>
  <Tab title="For visitors">
    **Relevant experiences**

    <div>
      Website visitors get to explore the features that matter most to them—at their own
      pace—resulting in a more personalized and engaging first impression of your product.
    </div>
  </Tab>

  <Tab title="For marketers">
    **Actionable insights**

    <div>
      See which features generate the most engagement and use that data to inform content strategy,
      refine ad targeting, or pass along intent signals to your sales team for smarter outreach.
    </div>
  </Tab>
</Tabs>

## Building an Interest Area Demo

Follow these steps to create an Interest Area demo that your sales team can share for discovery:

<Steps>
  <Step title="Create an Interest Demo">
    On the Product Demo page, select `+ Create new`. For `Start by` select
    `Generating interest demo`. We recommend using `Interest areas` forms for
    sales use cases to collect **the area of interest** a prospect has in
    different features.

    <img alt="Create interest areas demo" />
  </Step>

  <Step title="Select Interests">
    Select the Interests that you would like to include in your demo.
    `Interests` are product or feature areas that a prospect might be interested
    in. (ex. Payments, Credit Cards, Corporate Spending, Payroll, etc).

    You will be generating a flow (5-15 steps recommended) for each Interest.

    <img alt="Select interests" />
  </Step>

  <Step title="Edit your generated flows">
    After clicking `Create demo` an Interest Area form will be added to the first flow, a flow will be created for each interest, and a checklist task will be created for each flow.

    Now you can open and edit each flow to complete the demo.

    <img alt="Generated interest flows" />
  </Step>
</Steps>

<Icon icon="party-popper" /> **Congratulations** -- you've finished building your first
<Icon icon="chart-no-axes-column" /> **Interest areas demo** and it's ready to share!

Interest areas demos are a powerful tool for marketing teams to uncover what resonates most with site visitors—before they ever fill out a form.

They’re especially useful for capturing product interest on your website, helping you refine messaging and pass along valuable signals to your sales team.


# Multilingual demos
Source: https://docs.navattic.com/demos/multilingual

Learn how to translate your Navattic demos into multiple languages.

<Info>Enabled in workspaces on the Growth plan.</Info>

<Icon icon="languages" /> **Multilingual demos** are a powerful feature that allows you to translate
your demos into multiple languages. Use multilingual demos to reach a global audience and create a
more inclusive, localized experience for every viewer.

To translate a demo, open it in the **Build** tab > click the settings icon (gear) in the top-right toolbar > **Languages** > **Add language** > select a language from the dropdown > **Add**.

When you add a language, Navattic uses AI to automatically generate translations. These translations write into draft edit versions so they can be edited in the builder. If you make manual changes to your default language, you can click "Sync translations" to retranslate the selected languages.

### What updates on publish

When you publish a demo, all language versions that have a completed translation go live at the same time. Share links immediately serve whichever language matches a viewer's browser preference. Languages that were never translated, or whose translation is still in progress, do not appear as options until the translation is complete and the demo is published again.

### Syncing translations

**Sync translations overwrites your manual edits.** When you click "Sync translations," Navattic re-translates the selected languages from your default language content from scratch. Any manual changes you made to those translations are replaced. Languages you do not select in the sync dialog are left untouched.

### Captures vs. text

Text (tooltip copy, step titles, and button labels) and captures (the screenshots or videos of your product) are translated independently.

By default, all language versions share the same captures — every viewer sees the same screenshots regardless of their language. Per-language capture translation is an additional opt-in feature. When enabled, publishing the demo triggers background jobs to produce translated capture sets for each non-default language. Syncing translations only affects text; captures are re-translated on publish, not on a manual sync.

### Automatic language detection

Navattic automatically serves your demo in the viewer's preferred language. When a viewer opens a demo, Navattic checks their browser's language settings and — if a matching completed translation exists — displays the demo in that language without any action required from the viewer or you.

Language priority:

1. **`?lang=` URL parameter** — If the share link includes a language parameter, that language is always used.
2. **Browser language preference** — If no `?lang=` parameter is set, Navattic reads the viewer's browser language and serves the closest matching translation.
3. **Demo default language** — If the viewer's browser language does not match any available translation, the demo's default language is shown.

No configuration is needed. Automatic detection works for any demo that has at least one completed translation.

### In-demo Language Selector

Allow visitors to switch between available languages directly within the demo. Enable the **Language selector** toggle in the Languages menu to show a flag icon in the demo player.

### Translation Glossary

Ensure consistent translation of brand names and specific terms across all your demos. Workspace Admins can manage the **Translation Glossary** in **Settings** > **Translation**.

Automatic demo translations to these languages are supported today:

<CardGroup>
  <Card
    title="Afrikaans (af)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/za.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Arabic (ar)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/sa.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Bulgarian (bg)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/bg.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Cantonese (yue)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/hk.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Chinese - Simplified (zh-CN)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/cn.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Chinese - Traditional (zh-TW)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/tw.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Czech (cs)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/cz.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Danish (da)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/dk.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Dutch (nl)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/nl.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Filipino (tl)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/ph.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Finnish (fi)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/fi.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="French (fr)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/fr.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="German (de)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/de.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Greek (el)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/gr.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Hebrew (he)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/il.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Hindi (hi)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/in.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Hungarian (hu)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/hu.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Indonesian (id)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/id.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Italian (it)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/it.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Japanese (ja)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/jp.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Korean (ko)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/kr.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Lithuanian (lt)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/lt.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Malay (ms)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/my.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Norwegian (no)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/no.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Polish (pl)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/pl.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Portuguese (pt)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/pt.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Romanian (ro)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/ro.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Russian (ru)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/ru.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Slovak (sk)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/sk.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Spanish (es)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/es.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Swedish (sv)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/se.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Thai (th)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/th.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Turkish (tr)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/tr.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Ukrainian (uk)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/ua.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Vietnamese (vi)"
    icon={
  <img src="https://hatscripts.github.io/circle-flags/flags/vn.svg" className="my-0 h-6 w-6" />
}
  />
</CardGroup>


# Narrated demos
Source: https://docs.navattic.com/demos/narrated

Create demos with synchronized audio narration using Copilot.

<Info>
  Available on the **Growth plan and above**. Requires Copilot to be enabled in your workspace.
</Info>

Narrated demos let you record your screen alongside a live voice narration, then use Copilot to generate a demo where the audio and screen captures are synchronized. The result is a polished, self-paced experience visitors can watch on their own.

## Creating a narrated demo

<Steps>
  <Step title="Open the Create demo modal">
    From your Navattic workspace, click **Create demo**.
  </Step>

  <Step title="Select Narrated demo">
    Under **What type of demo are you creating?**, choose **Narrated demo** from the dropdown.

    <Note>
      This option only appears when Narrated Demos and Copilot are both enabled for your workspace. Contact your account team if you don't see it.
    </Note>
  </Step>

  <Step title="Enter your app URL and name your demo">
    Provide the URL of the application you want to capture, then give your demo a name. Click **Create**.
  </Step>

  <Step title="Open the Navattic Chrome Extension">
    After creating the demo, open the Navattic Chrome Extension on your application. You'll be prompted to select a microphone for recording.

    Choose your preferred microphone from the **Microphone** dropdown, or select **None** to skip audio. Click through to begin your capture session.
  </Step>

  <Step title="Record your narration and captures">
    Navigate through your application as you normally would when capturing a demo. As you capture each screen, speak your narration aloud — Navattic records the audio and links each capture to its point in the narration timeline.

    When you're done, end the capture session in the extension.
  </Step>

  <Step title="Generate the narrated demo">
    Return to Navattic and click **Generate** to let Copilot build the demo from your recordings. Copilot uses the audio and capture timestamps to create a synchronized experience.

    Generation time depends on the length of your recording.
  </Step>
</Steps>

## Syncing narration from step text

After a narrated demo is generated, you can update the narration for individual steps using the text already in your Modals and Tooltips — no re-recording needed.

To sync narration from step text, open the step in the Flow Builder and click **Sync from step text** in the voiceover settings. Navattic uses the step's text content to generate new narration audio for that step.

This is useful when you've edited the text of a step and want the narration to match the updated copy.

## Closed captions

<Note>
  Closed captions must be enabled for your workspace. Contact your account team if you don't see this option.
</Note>

Narrated demos support closed captions that display synchronized text alongside the audio narration. When enabled, visitors see a caption overlay that follows along as the narration plays.

To enable closed captions, open the narrated demo in the builder, go to **Settings**, and toggle on **Closed captions**.

## Tips for narrated demos

* **Speak naturally** — Narrate as if you're walking a colleague through the product. Copilot handles the synchronization; you focus on the message.
* **Pause between screens** — Give yourself a moment after speaking before clicking to the next screen. This keeps the audio clearly tied to the relevant capture.
* **Test your microphone first** — Confirm your microphone is working before starting a session to avoid having to re-record.
* **Keep recordings concise** — Shorter, focused narrations produce the clearest results. Aim for demos that cover one goal or workflow per recording.


# Offline demos
Source: https://docs.navattic.com/demos/offline

Present Navattic demos offline from your own device.

<Info>Enabled in workspaces on the Enterprise plan.</Info>

Use <img /> **Offline demos** to confidently present your demo at a conference, trade show, or on-site with your client.

<Steps>
  <Step title="Download demos for offline use">
    Under <Icon icon="layout-grid" /> **Product demos**, find the demo to download for offline use
    and select `Download` under the more actions menu.

    <img alt="Download demos for offline use" />
  </Step>

  <Step title="Open the Offline Player">
    The Offline Player is the home for presenting your demos offline on your device. The Offline
    Player can be used without being connected to wifi when installed as a PWA. Navigate to
    `Settings` > `Offline` and click on the `Go to offline player` button.

    <img alt="Offline demos go to player" />
  </Step>

  <Step title="Install Offline Desktop App">
    You can download the offline player as a progressive web app to make it easier to access your
    demos from your dock. Follow the appropriate instructions to install the PWA on your device.

    <img alt="Offline demos install PWA" />
  </Step>

  <Step title="View your offline demos">
    In the Offline Player, you'll see a list of demos that you've downloaded. Click `Present` to
    view the demo.

    <Frame>
      <img alt="Offline demos player" />
    </Frame>
  </Step>
</Steps>

**Use Cases**

* Bring your demo to trade shows or any event where the internet connection may be unstable
* Save your demos to designated event devices to help the attending team avoid logging in
* Use Tooltips and Modals to let audience members explore your product asynchronously (ex. as they wait in line), or use Triggers and Beacons if you're supporting a presenter-led use case.

<MediaCard type="demo" title="Offline Demos" />


# Personalized demos
Source: https://docs.navattic.com/demos/personalized

Make demos personalized by adding user and account properties.

<Icon icon="user-pen" /> **Personalization** lets you customize demo content based on user information, such as their name, role, or company logo. Use variables to create a more relevant experience for each viewer.

<a href="https://www.salesforce.com/in/resources/articles/customer-expectations/#:~:text=73%25%20of%20customers%20expect%20better,as%20its%20products%20and%20services.">
  <Tip>
    <b>73% of Buyers</b>
    expect better personalization with technology improvements.
  </Tip>
</a>

<Steps>
  <Step title="Select elements to personalize">
    Determine which elements you want to personalize. For example, you might want to personalize the `Name`, `Role`, and `Company Logo` of the visitor.
  </Step>

  <Step title="Personalize your captures">
    Open the `Capture Editor` and select the element(s) you want to personalize. Open <Icon icon="user-pen" /> **Personalization** in the Magic Editors.
    Click `+ Add Personalization` and select a property.

    You can add a fallback for the text using the format: `{{ property || fallback }}`.

    <Frame>
      <img alt="Personalize Capture Editor" />
    </Frame>
  </Step>

  <Step title="Personalize company logo">
    Select the logo that you would like to personalize in your capture, Click `Add Personalization` and select `Company Logo` for the property.

    The `Company Logo` will be personalized with the Navattic Logo API anytime the `Company Domain` or the `Visitor email` is populated.

    <img alt="Personalize Company logo Capture Editor" />
  </Step>

  <Step title="Personalize flows">
    Any text in your flows can also be personalized. In the `Flow Builder`, click `Personalization` in the More Action menu of the rich text editor for a step.

    <img alt="Personalize Richtext" />
  </Step>

  <Step title="Sharing personalized links">
    Once you've personalized your demo, you can share personalized share links with prospects. By specifying the recipient of a share link, the company logo will automatically be personalized. Within <Icon icon="link" /> **Share link settings** you can override this logo or add any other personalized property.

    <img alt="Personalize Share Link" />
  </Step>
</Steps>

<Icon icon="party-popper" /> **Congratulations** -- you've created a
<Icon icon="user-pen" /> **personalized demo** that you can use to share with visitors. Personalized
demos are great to create a personalized buyer experience.

<Note>
  Already have a list of prospects or accounts in mind? Use CONCATENATE within [Google
  Sheets](https://www.causal.app/formulae/concat-google-sheets#:~:text=To%20use%20CONCAT%20in%20Google,that%20you%20want%20to%20concatenate.)
  or
  [Excel](https://support.microsoft.com/en-us/office/combine-text-from-two-or-more-cells-into-one-cell-81ba0946-ce78-42ed-b3c3-21340eb164a6)
  to create personalized project share links in bulk.
</Note>


# Sandbox demos
Source: https://docs.navattic.com/demos/sandbox

Create a lightweight sandbox that your sales team can use live on calls.

<Info>
  Sandbox demos are available on Growth and Enterprise plans.
</Info>

<Frame>
  <img alt="Sandbox builder" />
</Frame>

Sandboxes allow you to click elements to navigate different parts of your application, making them perfect for live presentations. No engineering support needed.

## Step 1: Generate a Sandbox Demo

The quickest way to get started is by generating your sandbox demo from the Chrome extension or in-app.

<Tabs>
  <Tab title="Chrome Extension">
    <Steps>
      <Step title="Open the Chrome Extension">
        Open the Navattic Chrome Extension over your application.
      </Step>

      <Step title="Create a new demo">
        Select **New demo** and name your project.
      </Step>

      <Step title="Configure capture settings">
        Under **Capture Type**, select **Web capture**. Check the box for **Click to capture** and check the box for **Generate Sandbox from captures**.
      </Step>

      <Step title="Capture your screens">
        Click **Start capturing** and click naturally through your app to save your screens. Your clicks will be used as anchors to generate links for the sandbox.
      </Step>
    </Steps>
  </Tab>

  <Tab title="In-App Generator">
    <Steps>
      <Step title="Create a new demo">
        From the Navattic **Product Demos** page, click **Create demo**.
      </Step>

      <Step title="Select Sandbox demo">
        Select **Sandbox demo** under "What type of demo are you creating?"
      </Step>

      <Step title="Start capturing">
        Enter your **App URL** and click **Start capturing**. Click naturally through your app to save your screens.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Step 2: Edit the NavLinks

By clicking around your app using click to capture, sandbox links are automatically created. Open your sandbox demo in the Demo builder to edit them — the sandbox editing interface is built into the Build tab.

To view and manage all links at once, click the **Sandbox links** icon in the toolbar. A panel opens where you can switch between **This screen** (links on the current step) and **All links** (every link in the demo).

<AccordionGroup>
  <Accordion title="Creating Links">
    Select any onscreen element on your capture to create a link.
  </Accordion>

  <Accordion title="Flow Links">
    To move to another screen within the same section, set your link to navigate to a step within the same Flow. Use **Flow scoped links** (GoToStep) when navigating within the same section.
  </Accordion>

  <Accordion title="Demo Links">
    To jump to a completely different section of your app, set your link to start a new Flow. Use **Demo scoped links** (StartFlow) for top-level navigation between distinct sections.
  </Accordion>

  <Accordion title="Edit & Sync">
    You can edit existing matches, sync links across multiple screens, or delete steps directly from the sandbox builder without losing context.
  </Accordion>

  <Accordion title="Bulk remove or delete links">
    Select multiple links using the checkboxes in the Sandbox links panel, then click the trash icon to remove or delete them in one action.

    The behavior depends on which view you are in:

    * **This screen** — removes selected links from the current screen. The links still exist in other steps where they are used.
    * **All links** — permanently deletes selected links from the entire project, removing all associated beacons and triggers across every flow.

    A confirmation dialog shows which links will be affected before you proceed.
  </Accordion>

  <Accordion title="Duplicating flows, moving flows, and copying steps">
    When you duplicate a flow, move a flow to another demo, or copy steps to another flow, Navattic automatically handles any NavLinks in those flows or steps:

    * **Duplicate a flow** — Links that navigate to steps within the duplicated flow are automatically remapped to point to the corresponding steps in the new copy. Links that point outside the duplicated flow are preserved as-is.
    * **Move to another demo** — Links that reference steps in the original demo are remapped where possible. Links that cannot be remapped (because the target step doesn't exist in the destination demo) are dropped.
    * **Copy a step** — Flow-scoped links (GoToStep) that navigate to steps within the same flow are preserved in the copied step.

    After any of these operations, open the **Sandbox links** panel to confirm your links point to the right destinations.
  </Accordion>
</AccordionGroup>

<Tip>
  Stay organized by making every top-level navigation of your app (e.g., Home, Assignments, Evaluations) a separate Flow. You can then use Demo-scoped links to connect these separate flows together.
</Tip>

## Step 3: Configure Settings and Present

Prepare your demo for the perfect live call.

<CardGroup>
  <Card title="Reveal link hints" icon="eye">
    Turn this on in the settings menu to highlight clickable areas so presenters always know where to click.
  </Card>

  <Card title="Keyboard navigation" icon="keyboard">
    Enable keyboard navigation for smoother transitions during live calls.
  </Card>

  <Card title="Presenter notes" icon="sticky-note">
    Add presenter notes to your steps to help your team stay on script.
  </Card>

  <Card title="Presenter mode" icon="presentation">
    Enable presenter mode to show an optimized view for live delivery.
  </Card>

  <Card title="Show link suggestions" icon="sparkles">
    Display the original capture anchors to help you quickly identify and click elements to create new links.
  </Card>

  <Card title="Reset scroll" icon="arrow-up-to-line">
    Automatically scroll back to the top of the screen when navigating to a new step.
  </Card>
</CardGroup>

## FAQs

<AccordionGroup>
  <Accordion title="What is the difference between a Sandbox demo and a guided Flow?">
    Flows are step-by-step demos that a user progresses through at their own pace, best used for sharing. Sandbox demos allow the presenter to click around elements freely to navigate many different parts of the application live on a call.
  </Accordion>

  <Accordion title="Can I use Media captures in a Sandbox?">
    Yes. Media captures (uploaded images and videos) can be used as steps in a Sandbox demo. You can add NavLinks to media capture steps just like web captures, making them part of your clickable navigation. To generate the initial Sandbox from a live recording session, you still need Web captures — but once your Sandbox is created, you can add media capture steps through the builder and wire them into your navigation.
  </Accordion>

  <Accordion title="How do I delete a step in the Sandbox Builder?">
    You can delete steps directly from the Sandbox builder toolbar to save time and reduce context switching.
  </Accordion>

  <Accordion title="What if I have conflicting links?">
    If multiple actions are assigned to the same element, the Sandbox Builder will flag it as a collision. Click the collision badge to open the conflict resolve popover, where you can select your primary navigation action.

    To remove or delete multiple conflicting links at once, select them using the checkboxes in the conflict resolve popover and click the trash icon. A confirmation dialog lets you choose:

    * **Remove from screen** — removes the selected links from the current step only. Their anchors in other steps remain intact.
    * **Delete everywhere** — permanently removes the selected links and all their anchors from every flow in the project.
  </Accordion>

  <Accordion title="How do I link completely different sections of my app together?">
    Stay organized by making every top-level navigation of your app (e.g., Home, Assignments, Evaluations) a separate Flow. Use Demo-scoped links to connect these separate flows together.
  </Accordion>

  <Accordion title="When should I use Flow vs. Demo scoped links?">
    Use **Flow scoped links** (GoToStep) to navigate to a step within the same flow -- best for moving around the same section. Use **Demo scoped links** (StartFlow) to jump to the start of a flow in the same project -- ideal for top-level navigation between distinct sections.
  </Accordion>

  <Accordion title="When should I use 'Sync link' or 'Apply to all steps'?">
    Use this when you have a persistent navigation element (like a top navbar or side menu) that appears across many screens. Syncing the link applies it to all relevant screens automatically, saving you from adding it manually to each step.
  </Accordion>

  <Accordion title="When should I use 'Show link suggestions'?">
    Use this feature when building your sandbox. It shows the original anchors from your capture, allowing you to easily identify and click elements to create new sandbox links faster.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup>
  <Card title="Present demos" icon="presentation" href="/launchpad/share/present">
    Share and present Navattic demos during live calls.
  </Card>

  <Card title="Demo builder" icon="hammer" href="/build/demo-builder">
    Learn more about the Demo builder interface.
  </Card>
</CardGroup>


# Navattic Basics
Source: https://docs.navattic.com/help/basics

Interactive demos and video walkthroughs of Navattic basics.

Looking for a quick, engaging overview of Navattic basics? Learn the basics of the Navattic platform through a series of <Icon icon="circle-play" /> **videos** and <Icon icon="square-mouse-pointer" /> **interactive demos**.

## Creating and sharing demos

<CardGroup>
  <Card icon="circle-play" title="Build a demo using Copilot" href="https://www.loom.com/share/f488cf7ad0a144f984c3a7cf12afcd3d" />

  <Card icon="square-mouse-pointer" title="Navattic basics demo" href="https://navattic-website.navattic.com/1q8v0y4w" />

  <Card icon="circle-play" title="Building a flow" href="https://www.loom.com/share/8bc441b4963a431e89a94eb845fa5c29?sid=15eee611-903a-4f27-9b66-1781f65dea65" />

  <Card icon="circle-play" title="Mobile options" href="https://www.loom.com/share/c3e6f1c647c74434847c3e1e07689192?sid=03e7961f-8b6f-4e9a-b27b-c9445a850dca" />

  <Card icon="square-mouse-pointer" title="Share your Demo" href="https://navattic-website.navattic.com/bo3u40133" />

  <Card icon="circle-play" title="Create a checklist" href="https://www.loom.com/share/c370d6ec6c024b4888dad0d2b3f8c6e4?sid=d0e50567-acf7-4389-b077-41e1750b0a5d" />
</CardGroup>

## Taking and editing Captures

<CardGroup>
  <Card icon="circle-play" title="Take Captures" href="https://www.loom.com/share/dac1ae7fb3784bdeadb56f8943250227" />
</CardGroup>

## Customize your demo

<CardGroup>
  <Card icon="circle-play" title="Create a theme" href="https://www.loom.com/share/4567c5556b0541d0b2fbc2d04ae19e53?sid=7991caaf-9679-4e6e-91dd-7559c72d887c" />

  <Card icon="square-mouse-pointer" title="Add an Escape View" href="https://navattic-website.navattic.com/ojbv0zpp" />

  <Card icon="square-mouse-pointer" title="Buttons, Beacons, and Triggers" href="https://navattic-website.navattic.com/7y6s90e53" />
</CardGroup>

## Analytics

<CardGroup>
  <Card icon="circle-play" title="Understanding demo analytics" href="https://www.loom.com/share/16f7e9aa026c48fba8e13ae7d01af7bc?sid=536f8981-7d63-4031-9e49-edf2557baf1f" />

  <Card icon="square-mouse-pointer" title="Demo activity" href="https://navattic-website.navattic.com/rs4nv0ala" />

  <Card icon="square-mouse-pointer" title="Demo visitors" href="https://navattic-website.navattic.com/ub1ci072w" />

  <Card icon="square-mouse-pointer" title="Account based engagement" href="https://navattic-website.navattic.com/5y1l06cj" />
</CardGroup>

## Workspace

<CardGroup>
  <Card icon="circle-play" title="Invite members" href="https://navattic-website.navattic.com/b1tw0dbr" />
</CardGroup>


# Best practices
Source: https://docs.navattic.com/help/best-practices

Tips for creating interactive demos that convert visitors into customers.

Build demos that engage visitors and drive conversions. See examples in the [Customer Showcase](https://www.navattic.com/showcase) and the [2026 State of the Interactive Product Demo Report](https://www.navattic.com/report/state-of-the-interactive-product-demo-2026).

## Lead with your product

1. Prioritize vibrant, visual, and value-adding product areas when taking captures. 86% of captures in top-performing demos are HTML web captures. Use the [capture editor](/build/captures/web) to refine text or images as needed.
2. Use tooltips, beacons, and backdrops to highlight the most important elements on each step. See demos by [Mixpanel](https://mixpanel.navattic.com/h87c05n5), [Edge Delta](https://edge-delta.navattic.com/5g1703yt), and [DailyPay](https://get.dailypay.com/) for inspiration.

## Craft an engaging narrative

1. Top performing demos start with a hook, address customers directly, and contain **5-13 steps** per flow. Keep dialog boxes to **25-30 words**, with opening steps even shorter at 10-20 words. See [copywriting tips](https://www.navattic.com/blog/interactive-demo-copywriting-tips) for more guidance.
2. Use **multiple flows** when demoing different features or use cases. Multi-flow demos achieve 48% higher completion rates than single-flow demos.
3. [Add CTAs](/build/flows) after major product moments, on your final step, or throughout your demo with [escape view](/build/flows). Escape view is recommended for demos with 10+ steps.

## Apply finishing touches

1. Create a [theme](/build/themes) that includes your brand colors and fonts. 63% of top-performing demos use custom themes. See demos by [Guru](https://www.getguru.com/tour) and [Drift](https://www.drift.com/tour/conversational-marketing/) for design inspiration.
2. Set [responsive strategies](/build/responsive) to control how demos appear at different resolutions. 52% of top demos implement mobile-specific strategies—important since mobile visitors spend less time (1.2 min vs 2.7 min on desktop).

## Promote your demo

Where you place your demo on your website affects performance.

* **80% of top CTAs appear above the fold**—navbar and above-the-fold placements achieve 68% click-through rates
* Product pages (62%) and homepages (48%) are the most common locations for demos
* "Take a tour" remains the most popular CTA language

## Add conversion points

Your demo should encourage visitors to take the next step—whether that's booking a sales call, starting a free trial, or upgrading a feature. Top 10% of demos achieve 32% click-through rates, with the top 1% reaching 71%.

<Steps>
  <Step title="Add CTAs to your final step">
    Add 1-2 buttons to the last step of your demo directing visitors to the next step (e.g., "Start a free trial", "Book a demo").
  </Step>

  <Step title="Include a mid-demo conversion step">
    Add a dedicated conversion step right after a major reveal or "wow moment" in your demo, as shown in this [demo by Guru](https://www.getguru.com/tour).
  </Step>

  <Step title="Enable escape view">
    High-intent or returning visitors may be ready to convert before reaching your final step. [Enable escape view](/build/flows) to give visitors access to your CTA at any point.
  </Step>
</Steps>

## Form gating

Ungated demos show **6% higher engagement** and **7% higher completion** than gated demos. If you do use a form:

* Keep it short—75% of forms use a single field
* Position the form at the end of the demo rather than the beginning

<Tip>
  When linking to other pages from your demo, add `utm_source=navattic` to identify traffic from your demos. Learn more about [UTM tracking](https://blog.hubspot.com/marketing/what-are-utm-tracking-codes-ht).
</Tip>

## Learn more

<CardGroup>
  <Card title="Best practices blog" icon="newspaper" href="https://www.navattic.com/blog/category/best-practices">
    Read more tips and strategies for building demos.
  </Card>

  <Card title="2026 benchmark report" icon="chart-line" href="https://www.navattic.com/report/state-of-the-interactive-product-demo-2026">
    See data on what makes demos perform.
  </Card>
</CardGroup>


# FAQs
Source: https://docs.navattic.com/help/faqs

Find answers to frequently asked questions about web captures, media captures, and common issues.

### Web Captures

<AccordionGroup>
  <Accordion title="How do I capture a dropdown or popup menu?">
    If you are having trouble capturing an onscreen element, try using the keyboard command Ctrl+C (or Command+C for Mac) to take the capture.
  </Accordion>

  <Accordion title="How do I edit a Capture after adding it to a Flow?">
    From the Flow Builder, locate the Capture you would like to edit > click the arrows icon to expand the Capture > click "Edit". Save & Exit when complete. Keep in mind that your edits will be applied to every step that references this Capture (to avoid applying edits to every step with this Capture, first duplicate the Capture you are editing).
  </Accordion>

  <Accordion title="How do I edit the background when a popup or modal is present?">
    In the capture editor, use the up and down arrows to select the background element, open `Magic
                                                                                Editors` and `Overlay` and select `Ignore Overlay`. You may have to remove the Overlay on a few different layers before being able to access the element you are hoping to edit.
  </Accordion>

  <Accordion title="How do I edit text in my Captures?">
    First, **don't capture sensitive data**. While the Capture Editor can be used to quickly replace simple strings of text or to alter the appearance of distracting elements, we ask our customers to avoid capturing sensitive data altogether.

    To edit non-sensitive text, open the Capture Editor > select your text field > and type something new in the Text / HTML box. Most text fields are easily accessible in the Editor; [this tutorial](https://www.loom.com/share/33f5904569434c319480e683e8108bee) shows you a workaround if you are having trouble selecting a given "text" field.
  </Accordion>

  <Accordion title="I am unable to load the Chrome Extension.">
    If you're having trouble loading the Navattic Chrome Extension, it's possible that the extension does not have the correct permissions. If you want to use the application on any domain the chrome extension needs to have the permission "On all sites". If you just want it to work on specific applications, it should have the permissions for "navattic.com" and any other domains you want.

    **To update permissions:**

    1. Click on the Navattic icon in the Chrome extension bar. If it's not visible click the puzzle icon and select it from the dropdown menu (click the pin to add it to the extension bar).
    2. Open the tab "This Can Read and Change Site Data"
    3. Select the appropriate sites
    4. Refresh app.navattic.com and any pages that you have open where you want to run the extension.

       <img alt="" />
  </Accordion>

  <Accordion title="How can I take a Web Capture of a Figma file?">
    Follow the instructions in [this video](https://www.loom.com/share/9b159cef99ac40afb111e8aad4a734f5?sid=5f58608c-a856-485e-813d-35577cf9aecc) to learn how to convert your Figma files into an editable Web Capture.
  </Accordion>
</AccordionGroup>

### Media Captures

<AccordionGroup>
  <Accordion title="Can I add device borders to a screenshot?">
    Navattic includes mobile, tablet, and desktop borders for Apple and non-Apple devices. Adding a device border helps end users best visualize your desktop or mobile application. Learn more about' ' [adding a device border](/build/captures/media)' ' to a media capture.
  </Accordion>

  <Accordion title="How can I get my screenshot to better fit the device borders?">
    Using [device mode](https://developer.chrome.com/docs/devtools/device-mode) in Google Chrome paired with a [tool like
    this](https://chromewebstore.google.com/detail/gofullpage-full-page-scre/fdpohaocaechififmbbbbbknoalclacl) , you are able to take screenshots that better fit with the device borders.
  </Accordion>

  <Accordion title="Can I edit a media capture using the Capture Editor?">
    No. Navattic does not currently support image editing. We recommend using a tool like Figma or Adobe to make modifications prior to uploading.
  </Accordion>

  <Accordion title="What is the recommended resolution for screenshots in Navattic?">
    We recommend using images that are greater than 1200px in width as smaller images will appear blurry in Navattic.
  </Accordion>

  <Accordion title="How do I avoid the need to scroll when using a device border?">
    To avoid the need to scroll, find the ratio of the device border and ensure your image has the same ratio before uploading it to Navattic.

    ```text theme={null}
    The ratio for the Desktop border within Navattic is 3:2.
    ```

    An easy way to get the correct ratio is to set up a Google Slides deck with this same ratio as the device border you want to use. Then, fill the slides with your images before downloading each individual Slide.
  </Accordion>
</AccordionGroup>

### Flows

<AccordionGroup>
  <Accordion title="How do I add additional media files to a Flow?">
    You can add images, videos, and audio clips in Modals and Tooltips. From the Flow Builder, navigate to your desired step > click the dialog box > click "+" in the dialog header that appears > select and upload your media.

    Images and audio recordings will be uploaded directly from your device. Videos will require a link to a public video on Youtube, Vimeo, Loom, Wistia or Vidyard. We recommend keeping media attachments short to encourage users to explore your product on their own.
  </Accordion>

  <Accordion title="How should I end my Flow?">
    We recommend adding dual CTAs to the last step of your Flow. You may click `+` to add a Button to the Modal or Tooltip, or [hide Navigation
    Buttons](https://www.loom.com/share/dde828c52d4e4e4e820ddf64b2db5550) on the last step if needed. This will make it clear to your end user that they have completed the demo and encourage them to convert.
  </Accordion>

  <Accordion title="How do I use Navigation Buttons and CTA Buttons together?">
    To hide Navigation Buttons, click your step heading (ex. "Modal" or "Tooltip") > toggle on **Hide navigation** in the right-hand menu. Now that the navigation buttons aren't visible on this step, click the + button in the step and select **Button**. If you want to add more than one button, repeat this step.

    <img alt={true} />
  </Accordion>

  <Accordion title="How can I highlight multiple elements in a single step?">
    While each step can only include one Tooltip or Modal, **Beacons** can be used to highlight multiple elements at once ( [example](https://app.navattic.com/preview/flow/cls25ldm4006f0fjwfa1x9ky0?s=10) ). To do this, find your Step in the Flow Builder and simply [add Beacons](/build/flows) . We recommend including a Tooltip on this Step to communicate the intended workflow with users.
  </Accordion>

  <Accordion title="How do I fix a Tooltip that appears to run offscreen?">
    Tooltips may run off screen if the selected anchor element is too large and does not leave enough room to display the Tooltip fully. You can [change the tooltip position](/flows#2WZL5), [edit the tooltip height](/flows#AASb1) and/or [edit the tooltip width](/flows#_T4ZM) to try and get the Tooltip to fit.

    If these edits do not solve the problem, please select a smaller anchor element for this step.

    <img alt="" />

    <img alt="" />
  </Accordion>

  <Accordion title="How do I replace Captures within a Flow?">
    From the Flow Builder, locate the step where you want to switch the Capture and click on **Replace Capture**. This will open a dropdown menu where you can select a Capture from the current Collection, Add to the Collection, or select Captures from a different Collection in your workspace. If the new Capture has similar elements to the old Capture, the anchor element will automatically be updated.

    <img />
  </Accordion>

  <Accordion title="How will the Escape View appear in a Flow?">
    Escape View will match the Escape step that can be found at the end of your flow builder. To turn on [Escape view](https://demo-staging.navattic.com/7429hwxgx), click settings > toggle on Escape view.

    <img />
  </Accordion>

  <Accordion title="When should I include a Form in my demo?">
    Forms are used to gather user information such as name, email, company, and more. If the goal of your demo is to directly generate leads, a Form may be helpful for gathering information. Typically, about 20% of demo Visitors will fill out a Form on the first step.

    If using a Form, we recommend introducing this early in your demo and keeping it brief (**1-2 fields if possible**). Remember, your demo likely also includes other CTAs and conversion points that help high-intent viewers make their interest known.
  </Accordion>

  <Accordion title="I am unable to select elements within the Flow builder.">
    The [Navattic Chrome
    Extension](https://chrome.google.com/webstore/detail/navattic/lbecioncobbndebbfdopnpinnibemoon) is required in order to select elements within the Flow builder. Be sure to install this extension first. If it is already installed, please remove and re-add it to update it.
  </Accordion>

  <Accordion title="How do I enable a text input trigger?">
    [Text input has value condition](/build/flows) can be used to have viewers engage with the capture by adding a text string to a text input field or contenteditable element. If a text input condition is used in conjunction with a tooltip on the same step, you will also want to toggle off the **Progress on click** option on the step (found by clicking on the Anchor > Advnaced) so that the demo does not move to the next step when the element is clicked.
  </Accordion>

  <Accordion title="Can I highlight elements without using Tooltips?">
    While most Navattic demos benefit from dialog boxes that tell a story about your product,' ' [Beacons](/build/flows) can be used to highlight standalone elements in your Captures. From your Flow > add a Beacon. By default, a Beacon is a blinking dot next to an element.
  </Accordion>

  <Accordion title="Can I make edits across multiple steps at once?">
    With the Bulk Editor, you can apply edits across multiple steps at once. Bulk edits include:

    * Updating all beacons to triggers
    * Turning multiple modals into tooltips
    * Changing all beacons to have a highlight appearance instead of pulse
    * Deleting multiple beacons or triggers at the same time
    * Copying or Moving Steps to other Flows within your demo or to other Demos
    * Deleting multiple steps at the same time
    * and more!

    [View a 2-minute tutorial here](https://www.loom.com/share/b844f27c6f444054afa5790c65adfa7c?sid=b4e95e64-3e59-47cd-9d2b-3083d04ef645)
  </Accordion>

  <Accordion title="Can I copy or move steps into another Flow?">
    With the Bulk Editor, you can copy or move steps into another Flow within the same demo or to another Demo in your Workspace.

    To do this, check off the steps you want to move or copy and then select the **Copy to...** or \*\*Move to.. \*\*icon at the bottom of your screen. From here, you'll be prompted to select whether you want to copy the steps into a Flow within this demo or in another demo. Once you select the Flow you want to move it to, click **Copy # step.**

    [View a 2-minute tutorial here](https://www.loom.com/share/b844f27c6f444054afa5790c65adfa7c?sid=b4e95e64-3e59-47cd-9d2b-3083d04ef645)

    <img alt={true} />
  </Accordion>

  <Accordion title="How do I copy or move a flow to another Demo?">
    With Product Demos, you can copy over Flows from existing Product Demos. To do this, visit **Flows** > **+ Create Flow** > **Copy**. Select the target Product Demo and desired Flow to copy into your new Product Demo.

    You can also copy or move multiple Flows at once by selecting the Flows you want to Copy and then selecting the **Copy to...** or **Move to...** icon at the bottom of the screen. From here, you'll be prompted to select which Demo you want to add the Flows to.

    [View a 2-minute tutorial here](https://www.loom.com/share/b844f27c6f444054afa5790c65adfa7c?sid=b4e95e64-3e59-47cd-9d2b-3083d04ef645) .

    <img />

    ### Can I add navigation buttons to my demo without using a Modal or Tooltip?

    Yes, you can add navigation buttons without using a modal or tooltip by creating a Theme with a transparent dialog box and border.

    To create a Theme, visit **Themes** > **+ Create theme**. From here, select **Dialog** > **Dialog Background Color** > use the opacity slider under the color picker to make the dialog box transparent. Repeat this step with the **Dialog border color**.

    Learn more about [Themes](/build/themes).
  </Accordion>

  <Accordion title="Can I add navigation buttons to my demo without using a Modal or Tooltip?">
    Yes, you can add navigation buttons without using a modal or tooltip by creating a Theme with a transparent dialog box and border.

    To create a Theme, visit **Themes** > **+ Create theme**. From here, select **Dialog** > **Dialog Background Color** > use the opacity slider under the color picker to make the dialog box transparent. Repeat this step with the **Dialog border color**.

    Learn more about [Themes](/build/themes).
  </Accordion>
</AccordionGroup>

### Checklists

<AccordionGroup>
  <Accordion title="How do I make a Checklist appear for the viewer?">
    While viewers can manually expand at any point, you can also add an action to any Beacon, Trigger, or Button in your flow to prompt a Checklist to open automatically at a certain point, including after the last step. **Expand Checklist** can be paired with any condition, including **Timer**.

    <img alt={true} />
  </Accordion>

  <Accordion title="How do I adjust the appearance of my Checklist?">
    Visit [Themes](/build/themes) to adjust the appearance of your Checklist. Common adjustments may be:

    * Adjust the shape and size of your Checklist Launcher
    * Change the color of the checkmark
  </Accordion>

  <Accordion title="How do I view the Checklist created?">
    To view your Checklist, visit a Product Demo > **Checklist**. You can also preview the checklist when previewing the flow.
  </Accordion>

  <Accordion title="How do I move my Checklist to the left or right of the screen?">
    To move the Checklist position, you can drag and drop the checklist in the builder. Alternatively, visit the **Checklist** tab in your demo > **Edit** > **Position** > Select **Left** or **Right.**
  </Accordion>

  <Accordion title="How do I reset my progress in a Checklist?">
    When testing a Product Demo that contains a Checklist, you may notice that the Checklist tasks are already completed or include a strikethrough. This is due to your browser caching each previously completed step of the demo.

    To restart your Checklist each time, visit your Checklist Settings > **Always reset completed tasks**.

    <img />
  </Accordion>

  <Accordion title="How do I hide my Checklist until after a Form is submitted?">
    To prevent Visitors from skipping the Form by using the Checklist, visit your Checklist > Settings > Toggle on **Start hidden**.

    Once this is toggled on, visit the Flow with the Form > locate the Form Step > add the **Show checklist** action to **When form is submitted**.

    <img alt="Checklist Demos 10 Pn" title="Checklist Demos 10 Pn" />
  </Accordion>
</AccordionGroup>

### Share

<AccordionGroup>
  <Accordion title="How do I customize Product Demo links for sharing?">
    You may customize the path of your Product Demo URL under Share > Share links. ([https://workspace.navattic.com/CustomizablePortion](https://workspace.navattic.com/CustomizablePortion))

    Visit your Product Demo > **Share** > **Share links** > **+ Create link** > Enter a Name for your link > type into the customizable portion of the Share link at the bottom > **Create**.
  </Accordion>

  <Accordion title="How do I remove responsiveness from my Product Demos?">
    While your application's native responsiveness settings will work well in most cases, **Scale width** will be helpful for smaller iframe embeds or viewports. Instead of rearranging onscreen elements per your app's default responsiveness behavior, Scale width will **shrink** the entire Capture proportionally to fill your viewport. This ensures that end users will see the same elements onscreen as you did while taking the Capture.

    You can turn this on within Product Demos > Responsive > Scale width.
  </Accordion>

  <Accordion title="How do I create a .GIF or Video (.MP4) of my Product Demos?">
    Select the three dots next to the Share button and click **Export Preview** > Select **GIF** or **Video**  > Select the **Flow** > Choose the number of steps to include and the Time per step > click **Export**.
  </Accordion>

  <Accordion title="How do I optimize a demo of a Mobile App for viewing on Mobile Devices?">
    The goal of this section is to fine-tune a demo of a **Mobile App on a Mobile Device** (ex. demo the Slack mobile app on an iPhone). Please visit [this section of mobile viewing](/mobile) for information on presenting a demo of a *Web App on a Mobile Device*, which is a different scenario.

    To try the example below, visit this [demo of the Famly Mobile App](https://famly.navattic.com/for-docs?hideMobileAlert=true\&scale=1) on a mobile device. If you do not have a mobile device handy, installing a [mobile simulator like this](https://chrome.google.com/webstore/detail/mobile-simulator-responsi/ckejmhbmlajgoklhgbapkiccekfoccmk) may help quickly preview demos from a desktop.

    <img />

    **Step 1: Create a new Capture Collection** and upload screenshots of your mobile app interface ([Upload Images tutorial](https://www.loom.com/share/019783401a3d440ea2f7659b34892913?sid=4becb222-576e-451f-a65e-ea8a6ff4171a)). Do not add device borders to your screenshots. They should appear full-screen when previewed.

    * If you are creating a demo of a *Mobile Website* rather than a *Mobile App*, here is a [tutorial](https://www.loom.com/share/31e542e0b8df45df84872ec6377b1a69?sid=decf4ea1-da04-42a7-98cb-eb2edd8a8265) for taking scrollable screenshots of a Mobile Website. [GoFullPage](https://chrome.google.com/webstore/detail/gofullpage-full-page-scre/fdpohaocaechififmbbbbbknoalclacl) is a helpful browser extension for this.

    **Step 2: Create a Flow** using these Captures as you usually do ([Create a Flow](/flows)). When building, use these tips to further fine-tune your Flow for a mobile audience:

    * Use Tooltips rather than Modals to create an engaging experience
    * Add a heavy backdrop to steps that include a Tooltip. This helps highlight important elements, even on a smaller mobile screen
    * Add Beacons when necessary to show users where to click
    * Include Navigation buttons to help users easily progress thorugh the demo

    **Step 3: Select 'Show desktop demo'** under the Mobile tab to ensure your demo appears as expected on mobile devices.

    <img alt="Desktop On Mobile Faq Pn" title="Desktop On Mobile Faq Pn" />

    **Step 4:** From your website builder, link to the adjusted copy of your demo when a device under 800-px wide is detected. Most builders provide the option to create a [responsive layout](https://university.webflow.com/lesson/intro-to-responsive-design) for your page that will present slightly different elements when viewed on Mobile vs. Desktop.
  </Accordion>

  <Accordion title="How can I set up my demo so visitors can select the desktop or mobile app based on their device?">
    <Info>
      **Example**: View this demo on desktop vs. mobile to see the setup in action: [https://avizva.navattic.com/veh0awg](https://avizva.navattic.com/veh0awg).
    </Info>

    Follow the  instructions below to build out a demo that allows your visitor to select whether they would like to view the desktop or mobile app based on their device:

    1. **Build out two  Flows in the same demo:**

       * **Desktop App Demo**: Follow [these instructions](/build/flows) to build a Flow of your desktop demo.
       * **Mobile App Demo:**

         Check out the FAQ above to learn how to build a demo of a Mobile App for viewing on Mobile Devices.

       <img alt="Faqs 37 Pn" title="Faqs 37 Pn" />
    2. **Add a checklist to your demo:** After building out the desktop Flow and mobile Flow in the same demo,  add a [checklist](/build/checklist) to your demo that will serve as the device selector.
    3. **Set the checklist to "Floating"**:

       This ensures that it takes up a small portion of the screen.
    4. **Add the two checklist tasks** and update the descriptions to something like:
       * \*\*"I'm on a desktop" \*\*— Directs users to the desktop version of your demo.
       * **"I'm on a mobile device"** — Sends mobile users to your mobile-optimized demo.

         <img alt="Faqs 38 Pn" title="Faqs 38 Pn" />
    5. **Turn on "Start launched"**: Within the Checklist Settings, toggle on Start launched, which ensures the checklist automatically opens when the demo loads, prompting the visitor to choose their experience right away.
    6. **(Optional but recommended) Enable  "Backdrop"  in the Checklist Settings:**

       This subtly dims the rest of the screen so the device selector stands out, reducing the chance a visitor misses it.

       <img alt="Faqs 39 Pn" title="Faqs 39 Pn" />
    7. **Preview and publish:**

       Test both paths to confirm the desktop and mobile flows open as expected. Once everything looks good, **publish** your demo.
  </Accordion>

  <Accordion title="How do I embed my demo in my Zendesk help center?">
    Check out [this demo](https://training.navattic.com/3p2x0xuv) to learn how to embed a demo in your Zendesk help center.
  </Accordion>

  <Accordion title="How do I change the text in the banner of a Pop Up Embed Demo?">
    If you're using the HTML [Pop up embed code](/share/embed) , you can easily update the `data-navattic-title` attribute within the button element. By default, this attribute is set to the demo's title, but you can change it to any title you prefer.

    Alternatively, you can edit the name of your demo, publish the changes, and then re-embed the demo using the updated embed code.

    <img alt="" />
  </Accordion>

  <Accordion title="Can the embedded demo automatically show the visitor's preferred language based on location or browser settings?">
    Yes, as long as you are using the [Languages](/demos/multilingual) feature, you can manually configure the embedded demo to reflect the correct language by passing a query string to the iframe embed or demo share link [following these steps](https://stackoverflow.com/questions/10435512/capture-incoming-url-parameters-then-pass-to-iframe-src-with-javascript).

    For example, many websites allow visitors to select their preferred language, then append a query parameter like ?lang=en to the URL of subsequent pages to maintain that language preference. To ensure the demo reflects the correct language, you should pass the same query parameter to the demo embed or share link—and ensure it matches the language codes supported by Navattic.
  </Accordion>

  <Accordion title="How do I link to a specific flow within a multi-flow demo?">
    To link to a specific flow, use the following format: [capture.navattic.com/projectID/?g=flowID\&s=stepNumber.](http://capture.navattic.com/projectID/?g=flowID\&s=stepNumber)

    You can find the projectID and Flow ID in the URL of the flow builder. In the example below, the projectID is highlighted in red and the Flow ID is highlighted in green.

    <img alt="" />

    The share link for this specific flow would look like this: [****capture.navattic.com/clxy49afk000009jn3ss2d3rt/?g=clxz2h9b8000109lcf9sa07dk\&s=0****](https://capture.navattic.com/clxy49afk000009jn3ss2d3rt/?g=clxz2h9b8000109lcf9sa07dk\&s=0).

    If you wanted to link to step 2 of this flow, then you would switch **s=0** to be **s=1**. If you wanted to link to step 3, then you would change it to **s=2** and so on.
  </Accordion>

  <Accordion title="Can I add a full screen option to my embedded demo?">
    Yes. You can allow viewers to toggle your demo into full-screen mode.

    To enable this, visit your demo's **Build** page > Click the **three dots** next to the **Share** button > Select **Settings** > Enable **Full screen toggle** > Click **Save**.
  </Accordion>
</AccordionGroup>

### Tracking

<AccordionGroup>
  <Accordion title="How do I pass UTMs from a landing page URL into an embedded demo?">
    You may notice that your embedded Navattic demo does not automatically receive UTMs from the landing page it is embedded on. Take these steps to pass UTMs from the landing page URL into an embedded demo.

    1. Use [this resource by WickedReports](https://stackoverflow.com/questions/20366731/how-can-i-pass-utm-parameters-from-url-to-an-iframe) to pass UTMs into the demo iframe.
    2. Locate your iframe source ("iframe src") in your demo embed code. It will look like this. Add your UTM\_source to the end of this iframe src, as highlighted below.

       <img alt="" />
    3. You will now see Visitor UTMs appear in your CSV export and your Visitors tab > expand a Visitor > "Tracking" section.
  </Accordion>

  <Accordion title="What are the app.navattic.com cookies used for?">
    The following filtered cookies:

    ```text theme={null}
    __Secure-xxxxxxx
    ```

    ```text theme={null}
    __Host-next-auth-.csrf-token'
    ```

    are used for Navattic app auth and are not used for Visitor tracking. These cookies would never be sent from a Visitor page.
  </Accordion>

  <Accordion title="Does Navattic collect cookies for demo visitors?">
    If Customers decide to enable visitor cookies (this is an optional setting within the platform), visitor cookies will be tracked. If a Navattic form is used, these cookies will allow previously identified visitors to automatically skip subsequent Navattic form fills, providing a streamlined experience for both the visitor and the vendor (Customer).
  </Accordion>

  <Accordion title="How can I add tracking parameters to CTA buttons?">
    <img alt={true} />

    You can add flexible tracking parameters to URLs that visitors click throughout your Navattic demo. If you have tracking parameters like UTMs, Campaign IDs, etc., present in your demo share link, you can now add these to the CTA links that visitors click during your demo.

    This provides a fuller picture of a user's journey from your demo referrer page to your demo, to your CTA page, and beyond.

    To set this up, locate a **Navigate to URL** click action within your demo. Then:

    1. Check the box for **Add tracking params**.
    2. Add tracking params in a similar format as you have on other pages. For example, `?utm_source={{utm_source}}&utm_medium={{utm_medium}}` would insert the present value for utm\_source into this field.

    **If your demo is embedded**, check out the [Navattic JS docs](https://docs.navattic.com/tracking/identify/visitors#tracking-utm-parameters) to automatically tack UTM parameters.
  </Accordion>
</AccordionGroup>

### Visitor Analytics

<AccordionGroup>
  <Accordion title="How do I track converted Visitors in Navattic?">
    First, add a' ' ["Mark as Converted"](/build#A_TJC)' ' click action to the primary CTA button in your demo. Next, visit your Navattic Workspace > **Visitors** > **Filters** > Events: **Converted**. If you only want to see converted Visitors for a specific demo, you can also add a Product Demo Filter.
  </Accordion>

  <Accordion title="How do I see the total number of Visitors for a Demo?">
    From your Visitors tab, Filter by your Product Demo name to see only the Visitors who have engaged with this Demo.
  </Accordion>

  <Accordion title="How do I separate Product Demo Analytics for different embeds or links?">
    There are several ways to separate engagement data if you are using the same demo in multiple places. If you are sharing your demo via [Share Links](/share/links), **our recommendation** is to create [different share links](/product-updates#k7xAg) for your product demo and to view the /path in your CSV export.

    If you are [embedding your demo](/share/embed), **our recommendation** is to create multiple copies of your demo, so that each demo has a unique embed code. To copy a demo, visit the Product Demos page > locate the demo > click the three dots > Make copy.

    <img />
  </Accordion>

  <Accordion title="Do demos with or without Forms see more user engagement?">
    Form-gated demos may see a higher % of conversion events, as viewers who complete a Form are oftentimes higher-intent. However, we have found ungated demos had about on average 12% higher completion and 5% higher engagement rates.
  </Accordion>

  <Accordion title="Why are there a lot of Step 1 views?">
    If your demo is embedded as an iFrame on a high-traffic landing page **and** does not include a third-party form, each website visitor is "loading" the first step of your demo. In this case, Step 1 views represent each time your webpage has been loaded and may include users who do not click into your demo; for ungated embedded demos, Step 2 views would provide a better representation for how many users have interacted with each Demo.
  </Accordion>

  <Accordion title="Why are there more Views for later steps?">
    Within the Product Demo page, each step view represents a time that page has been loaded. If a user refreshes a particular step of your demo, this will count this as two views. If present, this discrepancy is usually small.
  </Accordion>

  <Accordion title="How do I add UTMs to an embedded demo?">
    To track UTMs for Visitors to an embedded demo, add your UTMs to the **end of the src link** in your Navattic Website Embed code (the highlighted section below). Note that Navattic does not pull UTMs from the top frame of the page for embedded demos.
  </Accordion>

  <Accordion title="How can I configure my Navattic form to accept only business/work emails?">
    To ensure visitors enter their work email in a Navattic form, navigate to the Form > Select **Email**> form field to open the settings > toggle on **Require work email**.
  </Accordion>

  <Accordion title="How can I block unwanted email domains from accessing my demos?">
    You can restrict access by adding a [Form](/tracking/forms/index) with an email field and enabling the **Blacklisted Domains** setting. To set this up, go to your Form Builder, select the email field, toggle on **Blacklisted Domains**, and enter the domains you want to block.

    This feature is available for Growth and Enterprise workspaces.

    <frame name="frame" />

    <img alt="2025 Product Updates 7 Pn" />
  </Accordion>
</AccordionGroup>

### Themes

<AccordionGroup>
  <Accordion title="How can I autogenerate a Theme using my company colors?">
    To autogenerate a Theme, go to Themes > Quick Builder. From here, you can choose a primary color and a secondary color > Click "Generate theme". If you want one of the colors to be the default background color, toggle on "background".

    These colors will automatically apply to all of the elements in Themes including buttons, beacons, tooltips, etc.

    <img alt="" />
  </Accordion>

  <Accordion title="How can I change the font?">
    To edit the font used in your demo, go to Themes > Font. You can edit the font color, size, line height, link color, and link hover color. You can also select a custom font.

    <img alt="" />
  </Accordion>

  <Accordion title="How do I edit the Button color and size?">
    To customize the Button, go to Themes > Select "Buttons" in the menu on the right. From here you can edit the Button border, text color, background color, font weight, and padding.

    <img />
  </Accordion>

  <Accordion title="How do I edit the Beacon color and size?">
    To edit the color and size of the Beacon, go to Themes > Select "Beacons" in the menu on the right.

    <img alt="" />
  </Accordion>

  <Accordion title="How can I customize the width of my Tooltips?">
    To edit the Tooltip width, go to Themes > Tooltip. Use the arrows to change the Tooltip widths for Small, Medium, and Large. Check out [Customize Tooltip
    Width](/flows#_T4ZM) for more details.
  </Accordion>

  <Accordion title="How do I edit the Checklist background color, border, and font?">
    To edit your Checklist background color and border, go to Themes > Use the drop down to select Checklist > Select Dialog.

    You can also edit the Font in your Checklist directly above Dialog. Make sure to Publish & Exit after making changes to your Checklist.

    <img alt="" />
  </Accordion>

  <Accordion title="How do I edit the Checklist checkmark color and task completion decoration?">
    To edit the Checklist checkmark color visit Themes > Select Checklist in the righthand menu.

    <img alt="" />
  </Accordion>

  <Accordion title="How do I edit the Checklist Launcher?">
    To edit the Checklist Launcher visit Themes > Select Checklist Launcher in the righthand menu.

    You can edit the placement, the horizontal and vertical padding, the border radius, the background color, the text color, and the font weight.

    <img />
  </Accordion>

  <Accordion title="How do I edit the Progress Bar?">
    To edit the Progress Bar (for your Modals, Tooltips and Checklist), visit Themes > Select Progress Bar in the righthand menu. Select "Show checklist progress bar" to turn on the Progress Bar for Checklists or "Show dialog progress bar" to turn on the Progress Bar for Modals and Tooltips.

    <Note>
      To preview what the Progress Bar will look like for Modals, Tooltips, or the Checklist you can use the dropdown menu in the top lefthand corner.
    </Note>

    <img alt="" />
  </Accordion>

  <Accordion title="How can I add a CTA banner to my demo?">
    Visit Themes > Banner to create a custom CTA Banner for your demos. Customize the banner's colors, text, and linked resources. Publish & Exit to add your banner to existing projects.

    <img alt="" />
  </Accordion>

  <Accordion title="How can I add a custom watermark to Tooltips and Modals?">
    Visit Themes > Watermark to upload an image to be used in Modals and Tooltips, and set your watermark's position, CTA link, and opacity.

    <img alt="" />
  </Accordion>

  <Accordion title="How can I change the Tooltip Border Color when paired with a Backdrop?">
    Visit Themes > Tooltip > Anchor backdrop highlight color to change the backdrop border color. Check out how to' ' [add a backdrop to your Tooltip](/flows#OX0vQ)
  </Accordion>
</AccordionGroup>

### Versions

<AccordionGroup>
  <Accordion title="What are Versions?">
    Every time you publish a demo, a new version is created, capturing a snapshot of your demo at that moment. This creates a complete history of your published changes, allowing you to see how your demo has evolved over time. Your current unpublished work is always available as "Drafted changes."
  </Accordion>

  <Accordion title="What can I do with a previous version?">
    From the version history, you can:

    * **Restore**: Revert your current draft to a previous version.
    * **Preview**: View a specific version to see how it looked and functioned.
    * **Edit Details**: Update the title and description of a version to keep your history organized.
  </Accordion>

  <Accordion title="How do I restore a previous version of my demo?">
    You can restore a previous version from the demo's "Versions" panel.

    1. From the demo header, open the menu and select **Versions**.
    2. A timeline of all your demo's versions will appear.
    3. Find the version you want to restore and select the **Restore** option.
  </Accordion>

  <Accordion title="What happens when I restore a version?">
    When you restore a previous version, its content will replace your current draft. A confirmation message will appear to let you know that all changes made to your draft since that version was created will be overwritten.
  </Accordion>

  <Accordion title="Does restoring a version automatically publish it?">
    No, restoring a version only updates your current draft. It does not automatically publish the changes. You will need to publish the demo to make the restored version live for your viewers.
  </Accordion>
</AccordionGroup>

### Launchpad tracking

<AccordionGroup>
  <Accordion title="What is the difference between a 1:1 and a 1:many share link?">
    A **1:1 link** is created for a specific company or prospect. You specify the company domain when creating the link, which allows Navattic to personalize the demo and track engagement to that account. A **1:many link** is designed for outbound campaigns where you're sharing with multiple prospects or companies at once. Navattic recommends 1:1 links for most deals, as they provide better personalization and more accurate engagement tracking.
  </Accordion>

  <Accordion title="Can I identify individual viewers from a 1:many share link?">
    Not by default. 1:many links are not tied to specific recipients, so viewers are tracked anonymously. To identify individual viewers, enable the **Recipient form gate** when creating the share link — this prompts each viewer to enter their name or email before accessing the demo.
  </Accordion>

  <Accordion title="What happens if a prospect forwards a 1:1 link to someone else?">
    Each person who opens the link creates a separate session in Navattic. If no recipient gate is enabled, those additional sessions will be unidentified. Enabling the **Recipient name or email gate** prompts new viewers to identify themselves, which helps you discover additional stakeholders in the buying process.
  </Accordion>

  <Accordion title="How do Launchpad demo sessions track to Salesforce opportunities?">
    There are two ways sessions are associated with Salesforce records. If the rep selects a Salesforce Opportunity when creating the share link, sessions from that link are logged directly to that opportunity. If no opportunity is selected, the Salesforce integration playbook automatically matches sessions to Leads, Contacts, and Accounts using the visitor's email address and company domain.
  </Accordion>
</AccordionGroup>

### Workspace FAQs

<AccordionGroup>
  <Accordion title="How can I preview my demo?">
    You can preview an entire demo by visiting the **Build** tab of your demo and clicking the **Play** button in the top navigation bar. This will open an interactive preview of your draft directly within the builder.

    <img />
  </Accordion>

  <Accordion title="How can I add a beacon or trigger?">
    You can still add a beacon or trigger to steps in your flow. To do this, scroll down and select **Add element**. A dropdown will apear and you can select either **Beacon, Input trigger**, **Timer trigger**, or **Element trigger**.

    <img />
  </Accordion>

  <Accordion title="Where can I find Tracking Scripts?">
    Tracking Scripts can still be found at the individual demo level. Select the three dots next to the black Share button > **Tracking Scripts**.
  </Accordion>

  <Accordion title="Where can I find Languages (Share links to translated demos)?">
    You can translate your demo or view Share links for different language versions of your demo by select the three dots next to the black Share button > **Languages**. Click **+ Add Language** to translate your demo.

    <img />
  </Accordion>

  <Accordion title="Where can I find the Flow Activity and step breakdown?">
    To see a step breakdown of your flows, visit a demo > **Analyze** **>** **Step breakdown**. You can analyze by a specific Version or by a share link. Use the dropdown **Flow** to select which flow you want to see the step breakdown for.

    <img alt="" />
  </Accordion>

  <Accordion title="How can I send a Test run in Playbooks?">
    To send a Test run in Playbooks to ensure your Integrations are working as expected, click the [Playbooks](/integrations/playbooks) tab > select a Playbook > Under **Configuration**, select the three dots (...) next to **Save** > **Test run.**

    <img />
  </Accordion>

  <Accordion title="How do I copy a demo?">
    To copy or duplicate an entire Product Demo, click **+ Create demo** and select the **Make Copy** option. This will duplicate all associated Capture collections, Flows, and the Checklist.
  </Accordion>

  <Accordion title="How do I copy a capture collection?">
    With Product Demos, you can make copies of Capture Collections from existing Product Demos. To do this, visit **Captures** > **+ Create Collection** > **Make Copy**. Select the target Product Demo and desired Capture Collection to copy this asset into your new Product Demo.

    <img />
  </Accordion>

  <Accordion title="How do I archive a product demo?">
    To archive your Product Demo, visit your demo > **click the three dots** next to the Share button > **Settings** >  **Danger zone** > toggle on **Archive**.

    You can also archive a demo on the **Product Demos** page by clicking the three dots next to the demo's title > **Archive.**
  </Accordion>

  <Accordion title="How do I find archived product demos?">
    To search for Archived Product Demos, visit Product Demos > Filters > Status: **Archived**.

    You can then unarchive the Product Demo by selecting the demo click the three dots next to the Share button > **Settings** > **Danger zone** > toggle off **Archive**.
  </Accordion>

  <Accordion title="How do I archive a flow?">
    To archive a single flow, open your demo and go to the **Flows** tab. Click the three dots next to the flow you want to archive and select **Archive**.

    To archive multiple flows at once, select them using the checkboxes and click the archive icon in the bulk action bar at the bottom of the screen. Navattic will show you any steps or checklist tasks that depend on the flow before confirming.
  </Accordion>

  <Accordion title="How do I unarchive a flow?">
    Archived flows are stored in your workspace archive. To find and restore them, go to **Workspace** > **Archive** in the left sidebar. Filter by **Flow** to narrow the list, then select the flow and click **Unarchive**.
  </Accordion>

  <Accordion title="How can I update my Workspace Name, Slug, and Logo?">
    You can update your Workspace Name, Slug and Logo under **Settings** > **General**.

    The logo is pulled directly from your website favicon based off the Website Domain added under **General**. Once your website favicon updates, the logo should automatically update as well.

    <img alt={true} />
  </Accordion>

  <Accordion title="How can I prevent Builders in my workspace from editing a published demo?">
    You can enable the **Require approval to publish demos** setting for your workspace. To find this, click **Settings** > **Workspace** > **General.**

    <img alt="Clean Shot 2026 01 23 At 14 12 49@2x" title="Clean Shot 2026 01 23 At 14 12 49@2x" />

    When this setting is turned on, **only the Project Owner or a Workspace Admin** can publish changes to a demo that has already been published. Other builders will still be able to view the demo, but they **won't be able to publish updates to the live version**.

    If a non-authorized builder attempts to publish changes, they'll see a message indicating that the demo is locked and that they should contact the project owner or a workspace admin.
  </Accordion>

  <Accordion title="Are Navattic demos accessible and WCAG compliant?">
    Navattic demos are WCAG compliant, so end viewers can navigate and interact with your demos using assistive technology. Specific accessibility features include:

    **Keyboard navigation**

    * Full keyboard support for navigating demos: **Tab** to move between interactive elements, **Enter** or **Space** to activate buttons, beacons, triggers, and checklist tasks, and **Escape** to dismiss dialogs
    * **Skip to content** and **Skip to capture** links for jumping past navigation
    * Automatic focus on the first interactive element when a step loads (form fields, buttons, checklist tasks, etc.)

    **Screen reader support**

    * ARIA roles applied to dialogs (`role="dialog"`, `aria-modal="true"`), buttons, links, and presentational elements
    * `aria-live` regions on dialog content so screen readers announce step changes
    * Beacons, triggers, and anchors include dynamic `aria-label` values describing the available action (for example, "Continue" or "Jump to step")
    * Builders can author custom ARIA descriptions for tooltips, beacons, and triggers to provide additional context
    * Dialog header controls (Back, Close) include explicit `aria-label` attributes

    **Focus indicators**

    * Visible focus styles on all interactive elements via `:focus-visible`
    * Focus ring color and width are customizable under **Themes**, so the focus indicator can meet your contrast requirements

    **Images and media**

    * Builders can set alt text on media captures, swipe step images, and inline images in modals and tooltips
    * The image editor includes a field for alternative text descriptions

    **Theme controls**

    * Color, contrast, and typography are fully customizable under **Themes**, so demos can be configured to meet the contrast ratios required for your audience

    For additional questions about accessibility and compliance, contact [support@navattic.com](mailto:support@navattic.com).
  </Accordion>
</AccordionGroup>


# Welcome to Navattic
Source: https://docs.navattic.com/index

Build interactive demos for marketing, growth, and sales.

<Frame>
  <img alt="Launchpad" />
</Frame>

## Welcome to Navattic

**Navattic** makes it easy to build and share interactive product demos across your team. With Navattic, teams can organize, access, and distribute demos in a consistent, scalable way.

This documentation will guide you through setting up your workspace—from creating demos to tracking engagement—so you can start using interactive demos throughout your workflows.

## Building demos

Creating clear, engaging demos is key to making the most of Navattic. In this section, you’ll learn how to build demos tailored to a variety of use cases—whether you're personalizing for an individual, showcasing a key feature, or creating something entirely custom.

We’ll also walk through how to build your first gold-standard demo that matches your company’s brand and style.

<CardGroup>
  <Card title="Build your first demo" icon="layout-grid" href="/build/demo">
    Create a demo for your first use case in minutes.
  </Card>

  <Card title="Creating flows" icon="route" href="/build/flows">
    Break down your demo into smaller stories.
  </Card>

  <Card title="Checklist demos" icon="list-checks" href="/build/checklist">
    Allow visitors to choose their own adventure with a checklist.
  </Card>

  <Card title="Customize your theme" icon="swatch-book" href="/build/themes">
    Build a theme that reflects your brand and style.
  </Card>

  <Card title="Supporting screen sizes" icon="monitor-smartphone" href="/build/responsive">
    Learn how to make your demos look great on every screen size.
  </Card>
</CardGroup>

## Advanced demos

Take your demos a step further with advanced features that add flexibility and depth. In this section, you'll learn how to personalize content, support multiple languages, showcase mobile apps, and even use demos offline or to track feature interest.

<CardGroup>
  <Card title="Personalized demos" icon="user-pen" href="/demos/personalized">
    Make demos personalized by adding user and account properties.
  </Card>

  <Card title="Multilingual demos" icon="languages" href="/demos/multilingual">
    Support multiple languages in your demos.
  </Card>

  <Card title="Interest demos" icon="square-check-big" href="/demos/interest">
    Unlock a powerful insight - what features prospects are interested in seeing.
  </Card>

  <Card title="Offline demos" icon={<img src="https://mintcdn.com/navattic-app/F-ocMwTZ1ZRknPbL/images/icons/offline.svg?fit=max&auto=format&n=F-ocMwTZ1ZRknPbL&q=85&s=0a33f3be65cc6e3844dd2163a9c86400" />} href="/demos/offline">
    Use your demos offline at tradeshows and conferences.
  </Card>

  <Card title="Sandbox demos" icon={<img src="https://mintcdn.com/navattic-app/F-ocMwTZ1ZRknPbL/images/icons/sandbox.svg?fit=max&auto=format&n=F-ocMwTZ1ZRknPbL&q=85&s=4160abd437d29288d56a6ec31ed9ab69" />} href="/demos/sandbox">
    Learn how to quickly build a lightweight sandbox demo.
  </Card>
</CardGroup>

## Sharing demos

Once your demo is ready, it’s time to get it in front of your audience. This section covers best practices for sharing—whether you’re embedding it on your website or sending it out via trackable share links.

<CardGroup>
  <Card title="Embed your demo" icon="panels-top-left" href="/share/embed">
    Embed your demo on your marketing website or product.
  </Card>
</CardGroup>

## Tracking

Tracking helps you understand how demos are being used and who’s engaging with them. In this section, you’ll learn how to install tracking scripts, identify visitors, and connect demo activity to your other analytics tools.

<CardGroup>
  <Card title="Navattic JS" icon="square-code" href="/tracking/navattic-js/index">
    Install and configure the Navattic JS tracking script.
  </Card>

  <Card title="Identifying visitors" icon="user-round-search" href="/tracking/identify/visitors">
    Identify who is visiting your demos.
  </Card>

  <Card title="Tracking scripts" icon="activity" href="/tracking/tracking-scripts/index">
    Add third-party tracking scripts to your demos.
  </Card>
</CardGroup>

## Integrations

Connect Navattic with your existing tools to streamline demo sharing and surface insights. This section covers how to embed demos in outbound campaigns, sync engagement data with your CRM, and use integrations to understand visitor behavior.

<CardGroup>
  <Card title="Playbooks" icon="zap" href="/integrations/playbooks">
    Send demos in outbound email campaigns to book more meetings.
  </Card>

  <Card title="Integrations" icon="sliders-vertical" href="/integrations">
    Learn about what the prospect is interested in before the first call.
  </Card>
</CardGroup>

## Workspace

Your shared workspace is for building, organizing, and managing demos as a team. Here, you'll learn how to invite members, set shared defaults, structure your workspace, and collaborate efficiently.

<CardGroup>
  <Card title="Inviting members" icon="globe" href="/workspace/inviting-members">
    Invite members to your workspace and manage their access.
  </Card>

  <Card title="Demo defaults" icon="wrench" href="/workspace/demo-defaults">
    Standardize defaults for demos across your workspace.
  </Card>

  <Card title="Workspace organization" icon="grid-3x3" href="/workspace/workspace-organization">
    Organize your workspace to scale to meet your needs.
  </Card>

  <Card title="Collaboration" icon="message-circle" href="/workspace/collaboration">
    Leave comments on demos for your team to review.
  </Card>
</CardGroup>

## Security Features

Keep your workspace secure and compliant with enterprise-grade controls. This section covers how to manage access with SSO and directory sync, host demos on custom domains, and monitor activity with audit logs.

<CardGroup>
  <Card href="/workspace/sso" icon="shield" title="SSO">
    Require all workspace members to authenticate using your organization's identity provider, such
    as Okta.
  </Card>

  <Card href="/workspace/directory-sync" icon="database" title="Directory Sync">
    Automatically provision users and configure their roles using your organization's identity
    provider, such as Okta.
  </Card>

  <Card href="/workspace/custom-domains" icon="globe" title="Custom Domains">
    Custom domains allow you to host demos on your own domain such as `demo.acme.com`.
  </Card>

  <Card href="/workspace/custom-domains" icon="list" title="Audit Logs">
    View an event stream of notable actions that members take in your workspace.
  </Card>
</CardGroup>


# Field mappings
Source: https://docs.navattic.com/integrations/field-mappings

Configure how Navattic syncs data to your CRM integrations.

<Frame>
  <img alt="Field mappings" />
</Frame>

<Icon icon="arrow-right-left" /> **Field mappings** control how visitor and company data from
Navattic demos flows into your CRM system. This guide covers setup, available fields, and best
practices for [HubSpot](/integrations/hubspot), [Salesforce](/integrations/salesforce),
[Marketo](/integrations/marketo), and [Pardot](/integrations/pardot).

## How to Configure Field Mappings

Field mappings are configured directly within each integration's settings:

1. Navigate to **Settings** → **Integrations** in your Navattic workspace
2. Select your connected CRM integration
3. Click the **Configuration** tab
4. Select **Field Mapping** from the dropdown menu

## Default Field Mappings

Navattic provides standard fields that can be mapped to your CRM. These are organized into Visitor fields (individual contacts) and Company fields (accounts).

<Expandable title="Visitor fields">
  | Name                     | Description                                                                                                                | Type   |
  | ------------------------ | -------------------------------------------------------------------------------------------------------------------------- | ------ |
  | Visitor Source           | Indicates record came from Navattic                                                                                        | Text   |
  | Email                    | Visitor's email address                                                                                                    | Text   |
  | Visitor First Name       | First name of the visitor                                                                                                  | Text   |
  | Visitor Last Name        | Last name of the visitor                                                                                                   | Text   |
  | Last Viewed Flow ID      | Navattic's internal ID for the last flow viewed                                                                            | Text   |
  | Last Viewed Flow Name    | Human-readable name of the last flow viewed                                                                                | Text   |
  | Last Viewed Project ID   | Navattic's internal ID for the last demo viewed                                                                            | Text   |
  | Last Viewed Project Name | Human-readable name of the last demo viewed                                                                                | Text   |
  | Last Viewed Step ID      | Navattic's internal ID for the last step viewed                                                                            | Text   |
  | Last Viewed Step Name    | Human-readable name of the last step viewed                                                                                | Text   |
  | Last Viewed Step Index   | Numerical position of the last step viewed (e.g., "3" for third step)                                                      | Text   |
  | Session ID               | Unique identifier for the demo session                                                                                     | Text   |
  | Checklist Name           | Name of the checklist being followed (if applicable)                                                                       | Text   |
  | UTM Content              | Campaign content parameter from the demo URL                                                                               | Text   |
  | UTM Source               | Traffic source parameter from the demo URL (e.g., "email", "social")                                                       | Text   |
  | UTM Medium               | Marketing medium parameter from the demo URL (e.g., "cpc", "organic")                                                      | Text   |
  | UTM Campaign             | Campaign name parameter from the demo URL                                                                                  | Text   |
  | UTM Term                 | Paid search keyword parameter from the demo URL                                                                            | Text   |
  | UTM Referrer             | Referring URL that brought the visitor to the demo                                                                         | Text   |
  | Browser                  | Visitor's web browser (e.g., Chrome, Safari, Firefox)                                                                      | Text   |
  | Current URL              | Full URL where the demo was viewed                                                                                         | Text   |
  | Path                     | URL path where the demo was viewed (excludes domain)                                                                       | Text   |
  | Screen Width             | Visitor's screen width in pixels                                                                                           | Number |
  | Screen Height            | Visitor's screen height in pixels                                                                                          | Number |
  | Device                   | Device type (Desktop, Mobile, Tablet)                                                                                      | Text   |
  | Operating System         | Visitor's operating system (e.g., Windows, macOS, iOS)                                                                     | Text   |
  | Navattic Agent CTAs      | Comma-separated list of CTA button labels clicked during a Navattic Agent session. Only populated for identified visitors. | Text   |
</Expandable>

<Expandable title="Company fields">
  | Name                     | Description                                                               | Type |
  | ------------------------ | ------------------------------------------------------------------------- | ---- |
  | Company Source           | Indicates record came from Navattic                                       | Text |
  | Name                     | Company name (enriched via Clearbit or form submission)                   | Text |
  | Last Viewed Flow ID      | Navattic's internal ID for the last flow viewed by anyone at this company | Text |
  | Last Viewed Flow Name    | Human-readable name of the last flow viewed by anyone at this company     | Text |
  | Last Viewed Project ID   | Navattic's internal ID for the last demo viewed by anyone at this company | Text |
  | Last Viewed Project Name | Human-readable name of the last demo viewed by anyone at this company     | Text |
  | Last Viewed Step ID      | Navattic's internal ID for the last step viewed by anyone at this company | Text |
  | Last Viewed Step Name    | Human-readable name of the last step viewed by anyone at this company     | Text |
  | Last Viewed Step Index   | Numerical position of the last step viewed by anyone at this company      | Text |
  | Domain                   | Company's primary web domain                                              | Text |
  | Description              | Company description (from Clearbit enrichment)                            | Text |
  | LinkedIn URL             | Company's LinkedIn page URL                                               | Text |
  | Employee Count           | Number of employees (from Clearbit enrichment)                            | Text |
  | City                     | Company headquarters city                                                 | Text |
  | State                    | Company headquarters state/region                                         | Text |
  | Country                  | Company headquarters country                                              | Text |
  | Postal Code              | Company headquarters postal code                                          | Text |
  | Technologies             | Comma-separated list of technologies used by the company (from Clearbit)  | Text |
</Expandable>

## Custom Form Field Mappings

In addition to default fields, you can map any custom form fields from your Navattic demos:

1. Create a form in your Navattic demo with custom fields
2. In field mappings, these custom fields appear automatically
3. Map each form field to corresponding CRM fields
4. Form submissions will populate your mapped CRM fields

### Best Practices for Form Fields

* Keep field names consistent between Navattic and your CRM
* Test form mappings with sample submissions
* Consider required vs. optional fields in both systems

## Next Steps

For integration-specific setup details, see:

<CardGroup>
  <Card
    title="Hubspot"
    href="/integrations/hubspot"
    icon={
  <img
    src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/integrations/hubspot.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=82b201671090d1c88fc8ebea2e90edb0"
    className="my-0 h-6 w-6"
  />
}
  >
    Sync engagement data with Hubspot Contacts, and Companies.
  </Card>

  <Card
    title="Salesforce"
    href="/integrations/salesforce"
    icon={
  <img
    src="https://mintcdn.com/navattic-app/2TSaKTXFRjfdIO0O/images/integrations/salesforce.svg?fit=max&auto=format&n=2TSaKTXFRjfdIO0O&q=85&s=1b9fd5585c937afe2287a19484df3328"
    className="my-0 h-6 w-6"
  />
}
  >
    Sync engagement data to Salesforce Leads, Contact, and Accounts.
  </Card>

  <Card
    title="Marketo"
    href="/integrations/marketo"
    icon={
  <img
    src="https://www.navattic.com/img/integrations/logos/marketo.png"
    className="my-0 h-6 w-6"
  />
}
  >
    Sync engagement data with Marketo programs.
  </Card>

  <Card title="Pardot" href="/integrations/pardot" icon={<img src="https://logo.navattic.com/pardot.com" className="my-0 h-6 w-6" />}>
    Sync engagement data with Pardot leads, accounts, dashboards, and workflows.
  </Card>
</CardGroup>


# HubSpot
Source: https://docs.navattic.com/integrations/hubspot

Connect your demos with HubSpot to create records from Visitors.

<Frame>
  <img alt="Hubspot integration" />
</Frame>

<Info>
  Check that you are [Identifying visitors](/tracking/identify/visitors) before setting up the Hubspot integration.
</Info>

The HubSpot integration is used to:

1. Create or update HubSpot Contacts with Navattic Visitor and Engagement data
2. Create and update HubSpot Companies with Navattic Account and Engagement data.

Once the data is available in HubSpot, HubSpot dashboards and reports can be created to answer questions like:

* Which demos generate the most leads?
* What % of leads originating from Navattic later convert to MQLs, and onwards?
* Which steps in my demo are most visitors dropping off at?

<MediaCard type="demo" title="Hubspot" />

<br />

## Setting up the HubSpot Integration

Follow these steps or the demo below to set up the Hubspot integration with Navattic:

<MediaCard type="demo" title="Hubspot Setup" />

<br />

<Steps>
  <Step title="Connect with HubSpot">
    Navigate to `Integrations` in Settings and select Hubspot. Click on Connect and follow the instructions to authorize your Hubspot account.
  </Step>

  <Step title="Set Up Field Mapping">
    [Field mappings](/navattic-field-mappings) allow you to control which pieces of Navattic's data go where. To set up field mapping, go to the **Settings** tab of your HubSpot integration. Open the **Field Mapping** dropdown, and start mapping fields. If you have [Account-Based Engagement](https://docs.navattic.com/tracking/identify/accounts#identifying-accounts), you will also see the option to set up Company field mapping. Fields on the left are Navattic data, and fields on the right are destinations within your HubSpot instance. Navattic uses HubSpot Contact Properties as data destinations.

    <Note>
      If you are setting up field mappings for Contacts, Email is a required field.
    </Note>
  </Step>

  <Step title="Create a Playbook">
    Once your HubSpot integration is fully set up, visit [Playbooks](/integrations/playbooks) in your Workspace to start pushing data into HubSpot. You can use a Template or create your own Playbook.

    There are four separate HubSpot Actions that you can set up: Sync contact, Send timeline events at the contact level, Sync account, and Send timeline events at the company or deal level.

    <Note>
      A Playbook consists of [Audiences](/integrations/playbooks) and Actions. You can use one of the default Audiences or you can create your own. If you create your own, remember to add new demos to the Audience if you are choosing to filter by specific demos.
    </Note>
  </Step>

  <Step title="Run a Test">
    Once the Playbook is set up, run a quick test to ensure this test data populates in HubSpot. To run a test, click the three dots next to the **Save** button > **Test run.**
  </Step>

  <Step title="Create HubSpot Dashboards to see ROI">
    [Try a demo](https://navattic-website.navattic.com/k8puwxfx) to see how Navattic-created Contacts appear in HubSpot.

    * Once connected, Navattic will send **email** (required) and all of the selected mapped fields to your HubSpot CRM.
    * These Contacts will be identifiable by the property **Original source 2** is Navattic.
    * The Original Source will reflect "Offline sources", per [HubSpot's default conditions](https://knowledge.hubspot.com/contacts/understand-source-properties#:~:text=A%20contact%E2%80%99s%20Original%20source%20or%20Latest%20source%20value%20will%20be%20one%20of%20the%20following%3A). Now you can use HubSpot dashboards to visualize your demo engagment data! We recommend creating [this HubSpot dashboard](https://navattic-website.navattic.com/k8puwxfx) to see demo views, step views, conversions, and the number of Contacts created by each demo.

    <MediaCard type="demo" title="Hubspot Dashboard" />

    <br />

    <MediaCard type="video" title="HubSpot Dashboard" />
  </Step>
</Steps>

<Tip>
  Tip: You can also create [HubSpot sequences](https://knowledge.hubspot.com/sequences/create-and-edit-sequences) based on visitor engagement with demos. The [HubSpot Knowledge Base](https://knowledge.hubspot.com/) contains more information on creating dashboards, reports, and sequences.
</Tip>

## Timeline events contact sync mode

When configuring a **Send timeline events at the contact level** playbook action, you can control whether Navattic creates new HubSpot contacts or only associates timeline events with contacts that already exist.

This option appears as **Contact sync mode** when **Associate with contact** is enabled on the timeline events action:

* **All visitors (create contacts)** — Default. Timeline events are associated with the visitor's contact record in HubSpot, creating the contact if one doesn't already exist.
* **Only existing contacts** — Timeline events are only sent for visitors who already have a matching contact in HubSpot. No new contacts are created.

<Tip>
  Use **Only existing contacts** when your Sync contact step is set to **Only update existing** — this keeps both actions consistent and prevents timeline events from being attached to contacts that were intentionally excluded from sync.
</Tip>

## Pipeline impact

Navattic can pull deal data from HubSpot to attribute pipeline to your demos. This feature is available to all workspaces with HubSpot connected and requires enabling the **Deals sync** setting in your HubSpot integration settings.

<Frame>
  <img alt="Integrations Hubspot Pipeline" />
</Frame>

### How it works

By default, the HubSpot integration pulls accounts and visitor data based on demo views and sessions. When **Deals sync** is enabled, Navattic uses HubSpot Deals as the data entrypoint — the same approach used for Salesforce — and maps deals to sessions, companies, and visitors in Navattic.

This lets you see which demos influenced open and closed deals, giving you a direct view of demo-attributed pipeline.

### Enabling Deals sync

<Steps>
  <Step title="Go to your HubSpot integration settings">
    Navigate to **Settings** > **Integrations** and select **HubSpot**.
  </Step>

  <Step title="Enable Deals sync">
    In the **Settings** tab, toggle on **Deals sync**. Once enabled, Navattic will begin pulling deal data from HubSpot.
  </Step>
</Steps>

<Note>
  Deals sync requires that your HubSpot integration is already connected and that you have deal data in HubSpot. If you do not see pipeline data after enabling this setting, confirm that your HubSpot Deals are associated with the Contacts that Navattic has identified.
</Note>


# Marketo
Source: https://docs.navattic.com/integrations/marketo

Sync demo engagement data and form submissions for automated lead nurturing.

<Frame>
  <img alt="Marketo integration" />
</Frame>

<Info>
  Check that you are [Identifying visitors](/tracking/identify/visitors) before setting up the Marketo integration.
</Info>

This integration is used to send Navattic visitor and engagement data to create or update Marketo Leads. Teams use this data to track the Leads that interact with demos, and to make informed routing and campaign decisions based on Navattic demo engagement data.

**Use this to answer questions like**:

* How many Leads interacted with the Navattic demo?
* How many Leads were created directly from a Navattic form fill?
* Which product demos do most Leads interact with?

<MediaCard type="demo" title="Marketo" />

## Setting up the Marketo Integration

Follow these steps or the demo below to set up the Marketo integration with Navattic:

<MediaCard type="demo" title="Marketo Setup" />

<Steps>
  <Step title="Set up your Marketo instance">
    Navattic requires a Client ID, Client Secret, Endpoint URL, and Identity URL from your Marketo instance. If you have not set up similar integrations before, the below step-by-step guide will help you create a custom service that Navattic can harness.

    1. [Create an API-only user role](https://experienceleague.adobe.com/docs/marketo/using/product-docs/administration/users-and-roles/create-an-api-only-user-role.html)
    2. [Create an API-only user](https://experienceleague.adobe.com/docs/marketo/using/product-docs/administration/users-and-roles/create-an-api-only-user.html?lang=en)
    3. [Create a custom service](https://experienceleague.adobe.com/docs/marketo/using/product-docs/administration/additional-integrations/create-a-custom-service-for-use-with-rest-api.html)
    4. [Grab your Client ID and Client Secret](https://experienceleague.adobe.com/docs/marketo/using/product-docs/administration/additional-integrations/create-a-custom-service-for-use-with-rest-api.html#credentials-for-api-access)
    5. [Grab your Endpoint URL and Identity URL](https://developers.marketo.com/rest-api/base-url/)

    Once you've obtained your Client ID, Client Secret, Endpoint URL, and Identity URL, go to [app.navattic.com](https://app.navattic/com) > **Playbooks** > **Integrations** > **Marketo** > **Manage** > **Connect**. Paste the fields into the respective tabs and click **Connect**.
  </Step>

  <Step title="Set Up Field Mapping under Configuration">
    Under **Configuration**, set up [Field mapping](/navattic-field-mappings) which allows you to control which pieces of Navattic's data go where. Fields on the left are Navattic data, and fields on the right are destinations within your Marketo instance.
  </Step>

  <Step title="Create a Playbook">
    Once your Marketo integration is fully set up, visit [Playbooks](/integrations/playbooks) in your Workspace to start pushing data into Marketo. You can use a Template or create your own Playbook. There is one Action that you can set up: Sync visitor. Additionally, make sure to select the Marketo Program you want to send data to.

    <Note>
      A Playbook consists of [Audiences](/integrations/playbooks) and Actions. You can use one of the default Audiences or you can create your own. If you create your own, remember to add new demos to the Audience if you are choosing to filter by specific demos.
    </Note>

    ### **Troubleshooting**

    If the integration is failing to populate fields in your Marketo instance, a common problem might be insufficient permissions for the API role created in Step 1. For leads not populating standard fields such as e-mail, name, or company, edit the role permissions ensure that the **Read-Write Schema Standard Field** permission is enabled under **Access API**. For leads not populating custom Navattic fields such as Last Viewed Project Title, ensure that the **Read-Write Schema Custom Field** permission is enabled.
  </Step>

  <Step title="Create Marketo Dashboards to see ROI">
    Now you can use Marketo reports to visualize your demo engagment data and attribute it to pipeline generation and closed-won revenue. We recommend creating a set of reports similar to the one below to track lead generation, pipeline influence, MQL conversion rates and more.

    <MediaCard type="video" title="Marketo" />
  </Step>
</Steps>


# Integrations overview
Source: https://docs.navattic.com/integrations/overview

Connect Navattic with your CRM, marketing automation, and analytics tools.

Navattic supports the following <Icon icon="sliders-vertical" /> **Integrations** that help you automatically sync engagement data across your go-to-market stack.

Whether you're alerting sales in Slack or enriching CRM records, these integrations ensure your team has the right context to operationalize on demo engagement.

<CardGroup>
  <Card
    title="Hubspot"
    href="/integrations/hubspot"
    icon={
  <img
    src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/integrations/hubspot.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=82b201671090d1c88fc8ebea2e90edb0"
    className="my-0 h-6 w-6"
  />
}
  >
    Sync engagement data with Hubspot Contacts, and Companies.
  </Card>

  <Card
    title="Salesforce"
    href="/integrations/salesforce"
    icon={
  <img
    src="https://mintcdn.com/navattic-app/2TSaKTXFRjfdIO0O/images/integrations/salesforce.svg?fit=max&auto=format&n=2TSaKTXFRjfdIO0O&q=85&s=1b9fd5585c937afe2287a19484df3328"
    className="my-0 h-6 w-6"
  />
}
  >
    Sync engagement data to Salesforce Leads, Contact, and Accounts.
  </Card>

  <Card
    title="Marketo"
    href="/integrations/marketo"
    icon={
  <img
    src="https://www.navattic.com/img/integrations/logos/marketo.png"
    className="my-0 h-6 w-6"
  />
}
  >
    Sync engagement data with Marketo programs.
  </Card>

  <Card title="Pardot" href="/integrations/pardot" icon={<img src="https://logo.navattic.com/pardot.com" className="my-0 h-6 w-6" />}>
    Sync engagement data with Pardot leads, accounts, dashboards, and workflows.
  </Card>

  <Card
    title="Slack"
    href="/integrations/slack"
    icon={
  <img
    src="https://mintcdn.com/navattic-app/2TSaKTXFRjfdIO0O/images/integrations/slack.svg?fit=max&auto=format&n=2TSaKTXFRjfdIO0O&q=85&s=e42ea16764d8a23306cfa74534b5ba2a"
    className="my-0 h-6 w-6"
  />
}
  >
    Receive engagement alert notifications in your Slack channel.
  </Card>

  <Card
    title="Segment"
    href="/integrations/segment"
    icon={
  <img
    src="https://www.navattic.com/img/integrations/logos/segment.png"
    className="my-0 h-6 w-6"
  />
}
  >
    Send engagement data to Segment to build custom workflows.
  </Card>

  <Card title="Webhook" href="/integrations/webhook" icon="webhook">
    Use webhooks to integrate any tool in your stack, including data warehouses and CDPs.
  </Card>

  <Card title="ZoomInfo" href="/integrations/zoominfo" icon={<img src="https://logo.navattic.com/zoominfo.com" className="my-0 h-6 w-6" />}>
    Enrich visitor and account data with ZoomInfo profiles.
  </Card>

  <Card title="Email" icon="mail">
    Receive engagement alert notifications in your inbox.
  </Card>
</CardGroup>

### Tracking scripts

<Icon icon="activity" /> **Tracking Scripts** can be enabled on individual Navattic demos to track
things like session recordings, demo engagement, as well allow chat or calendar widgets to be
included within the demo.

These scripts run on directly on your demo and send data directly to a third-party platform.

<CardGroup>
  <Card icon={<img src="https://logo.navattic.com/6sense.com" className="my-0 h-6 w-6" />} title="6sense" href="/tracking/tracking-scripts/6sense">
    Track visitor engagement as page views and clicks.
  </Card>

  <Card icon={<img src="https://logo.navattic.com/drift.com" className="my-0 h-6 w-6" />} title="Drift" href="/tracking/tracking-scripts/drift">
    Add chat widget for real-time customer conversations.
  </Card>

  <Card
    icon={
  <img
    src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/integrations/hubspot.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=82b201671090d1c88fc8ebea2e90edb0"
    className="my-0 h-6 w-6"
  />
}
    title="HubSpot JS"
    href="/tracking/tracking-scripts/hubspot"
  >
    Integrate demo engagement with HubSpot CRM.
  </Card>

  <Card
    icon={
  <img
    src="https://www.navattic.com/img/integrations/logos/marketo.png"
    className="my-0 h-6 w-6"
  />
}
    title="Marketo"
    href="/tracking/tracking-scripts/marketo"
  >
    Track demo interactions in Marketo campaigns.
  </Card>

  <Card icon={<img src="https://logo.navattic.com/posthog.com" className="my-0 h-6 w-6" />} title="PostHog" href="/tracking/tracking-scripts/posthog">
    Analyze demo usage with product analytics.
  </Card>

  <Card icon={<img src="https://logo.navattic.com/qualified.com" className="my-0 h-6 w-6" />} title="Qualified" href="/tracking/tracking-scripts/qualified">
    Deploy chatbots for automated demo engagement.
  </Card>
</CardGroup>

### Embedded forms

<Icon icon="code" /> **Embedded forms** allow you to integrate third-party forms and scheduling
tools directly into your demo steps. While Navattic forms are recommended for the best user
experience, embedded forms let you maintain existing workflows and integrations.

<CardGroup>
  <Card
    href="/tracking/forms/embedded"
    title="HubSpot"
    icon={
  <img
    src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/integrations/hubspot.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=82b201671090d1c88fc8ebea2e90edb0"
    className="my-0 h-6 w-6"
  />
}
  >
    Embed HubSpot forms with full CRM integration and tracking
  </Card>

  <Card
    href="/tracking/forms/embedded"
    title="Marketo"
    icon={
  <img
    src="https://www.navattic.com/img/integrations/logos/marketo.png"
    className="my-0 h-6 w-6"
  />
}
  >
    Capture leads directly into Marketo campaigns and programs
  </Card>

  <Card
    href="/tracking/forms/embedded"
    title="Calendly"
    icon={
  <img
    src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/integrations/calendly.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=2e56e3f9c79146ac86161ec8e771f7bc"
    className="my-0 h-6 w-6"
  />
}
  >
    Schedule meetings without leaving the demo experience
  </Card>

  <Card
    href="/tracking/forms/embedded"
    title="Chili Piper"
    icon={
  <img
    src="https://mintcdn.com/navattic-app/sbomoyxYqCTZHNO1/images/integrations/chilipiper.jpg?fit=max&auto=format&n=sbomoyxYqCTZHNO1&q=85&s=bf88bd73b76c0d55695319f66c2a2d4e"
    className="my-0 h-6 w-6"
  />
}
  >
    Instant routing and scheduling for qualified leads
  </Card>

  <Card
    href="/tracking/forms/embedded"
    title="RevenueHero"
    icon={
  <img src="https://logo.navattic.com/https://www.revenuehero.io" className="my-0 h-6 w-6" />
}
  >
    Qualify and route leads to the right sales rep instantly
  </Card>

  <Card
    href="/tracking/forms/embedded"
    title="HubSpot Meeting"
    icon={
  <img
    src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/integrations/hubspot.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=82b201671090d1c88fc8ebea2e90edb0"
    className="my-0 h-6 w-6"
  />
}
  >
    Book meetings directly with HubSpot scheduling pages
  </Card>

  <Card href="/tracking/forms/embedded" title="Default.com" icon={<img src="https://logo.navattic.com/default.com" className="my-0 h-6 w-6" />}>
    Smart scheduling and routing for demos
  </Card>
</CardGroup>


# Pardot
Source: https://docs.navattic.com/integrations/pardot

Track prospect engagement and automate follow-up.

<Frame>
  <img alt="Pardot integration" />
</Frame>

<Info>
  Check that you are [Identifying visitors](/tracking/identify/visitors) before setting up the Pardot integration.
</Info>

The Pardot integration sends real-time activity from visitors. You can use this engagement data to create Pardot leads, accounts, dashboards, and workflows.

## Setting up the Pardot Integration

Use this interactive demo or the written steps below to set up your integration.

<MediaCard type="demo" title="Pardot" />

<Steps>
  <Step title="Connect with Pardot">
    Navattic uses OAuth to connect with Pardot. Visit **Playbooks** > **Integrations** > **Pardot** > **Manage.** Select **Production** or **Sandbox** and add your 18-character Business Unit ID, which can be found in your Salesforce Settings > Platform Tools > Account Engagement > Business Unit Setup. This Pardot Business Unit ID begins with "0Uv" and is 18 characters long. Click **Connect**.

    You will be redirected to log in to your Salesforce account. Once you log in, it will bring you back to Navattic.
  </Step>

  <Step title="Set Up Field Mapping under Configuration">
    Under **Configuration**, set up [Field mapping](/navattic-field-mappings) which allows you to control which pieces of Navattic's data go where. Fields on the left are Navattic data, and fields on the right are destinations within your Pardot instance.

    Email will map automatically, so you do not need to add an email field.
  </Step>

  <Step title="Create a Playbook">
    Once your Pardot integration is fully set up, visit [Playbooks](/integrations/playbooks) in your Workspace to start pushing data into Pardot. You can use a Template or create your own Playbook.

    There are two Actions that you can set up: Sync prospect and Sync account (if you have Accounts set up).

    <Note>
      A Playbook consists of [Audiences](/integrations/playbooks) and Actions. You can use one of the default Audiences or you can create your own. If you create your own, remember to add new demos to the Audience if you are choosing to filter by specific demos.
    </Note>
  </Step>
</Steps>

## Embedding Pardot forms in demos

You can embed a Pardot form directly into a demo step using the **Pardot Form** embed type in the demo builder.

<Steps>
  <Step title="Add an embed step">
    In the Flow Builder, add a new step and select **Embed** as the step type. Then choose **Pardot Form** from the dropdown.
  </Step>

  <Step title="Enter your form details">
    * **Form ID or embed URL** — Paste the full form URL from your Pardot embed code (recommended, and required for custom tracker domains), or enter a numeric Form ID. To find the numeric ID, go to Marketing > Forms in your Pardot account; the ID appears in the form's URL.
    * **Business Unit ID** (optional) — Only needed when using a numeric Form ID. Leave this blank if you pasted a full form URL. To find it, go to Salesforce Setup > Pardot Account Setup. It begins with "0Uv" and is 18 characters long.
  </Step>
</Steps>

<Note>
  If your Pardot account uses a custom tracker domain (for example, `https://learn.yourcompany.com/l/...`), paste the full form URL in the Form ID field. Numeric Form IDs only work with the standard `go.pardot.com` domain.
</Note>

<Note>
  The Pardot form renders in an iframe within the demo. Form submissions are detected automatically. See [Embedded forms](/tracking/forms/embedded) for details on all supported embed types.
</Note>


# Playbooks
Source: https://docs.navattic.com/integrations/playbooks

Automate workflows and trigger actions based on demo engagement.

<Frame>
  <img alt="Playbooks" />
</Frame>

You have the option to create Playbooks manually, selecting from default or custom audiences and actions, or you can generate Playbooks automatically by using **Templates**.

<MediaCard type="video" title="Playbooks" />

## Audiences

Audiences are filtered views of Visitors and Accounts that view your demos. These include filters for Time spent, Total sessions to detect repeat visitors, Total steps, and more. **Create an Audience** by adding Filters to your Visitors or Accounts tab and selecting **Save.**

<img alt="" />

The below **Audiences** are created by default with Playbooks. You can always create a new audience as well.

### Default Visitors audiences

| Audience            | Description                                      |
| ------------------- | ------------------------------------------------ |
| Identified visitors | Visitors that have an email associated with them |
| Engaged visitors    | Visitors who advance 1+ steps in your demo       |
| Repeat visitors     | Visitors with at least 2 unique sessions         |

### Default Accounts audiences

| Audience                        | Description                               |
| ------------------------------- | ----------------------------------------- |
| Engaged accounts                | Companies with at least 1 engaged visitor |
| Accounts with multiple visitors | Companies with >1 unique visitor          |

### Create a custom audience

To create an Audience, visit the **Visitors** tab to create contact-based audiences or the **Accounts** tab to create account-based audiences. Use Filters to select the Audience you'd like to create. Once you have added the necessary Filters click \*\*Save \*\*> Name your audience > Save. Now, when you create a Playbook, you will see this Audience appear in the dropdown under **When visitor: Matches audience**.

<Note>
  If you have created Audiences in the past, these Audience will already be available to use with
  Playbooks.
</Note>

## Actions

We currently support 13 playbook actions outlined below. These actions are used to send visitor or account level data to the listed third-party tools. Playbook actions are run for individual visitor sessions when the session ends (i.e. when a visitor closes the page containing the demo or after 30 minutes of inactivity).

### Visitor-based actions

| Integrations | Playbook Action(s)                             |
| ------------ | ---------------------------------------------- |
| Hubspot      | Sync contact, Timeline events                  |
| Salesforce   | Sync contact, Sync lead, Submit session object |
| Pardot       | Sync lead                                      |
| Marketo      | Sync visitor                                   |
| Slack        | Send visitor message                           |
| Segment      | Segment event                                  |
| Webhook      | Webhook event                                  |
| Email        | Send visitor message                           |

### Account-based actions

Account-based actions are available if you have Account Based Engagement enabled. Contact [success@navattic.com](mailto:success@navattic.com) if you would like to learn more about Account Based Engagement.

| Integrations | Playbook Action(s)                                   |
| ------------ | ---------------------------------------------------- |
| Hubspot      | Sync company, Timeline events                        |
| Salesforce   | Sync account, Send notification to Opportunity Owner |
| Pardot       | Sync account                                         |
| Slack        | Send account message                                 |
| Segment      | Segment event                                        |
| Webhook      | Webhook event                                        |
| Email        | Send account message                                 |

<Note>
  Adding Marketo to a Playbook will allow you to choose which Marketo Program Visitors will sync to.
  Similarly, adding Slack to a Playbook will allow you to select the Slack channel to send visitors
  and/or account messages to.
</Note>

## Sync mode

<img />

### **Update and create**

**Update and create** includes full sync functionality and will create new Visitor and/or Account records. It will also update existing ones if they exist for each matching session that triggers the Playbook.

### Only update existing

**Only update existing** will not create any net new Visitor and/or Account records, but will update existing ones for each matching session that triggers the Playbook.

### Only first session

When enabled, this action will only be triggered for the first session for that Visitor or Account.

### Timeline events contact sync mode

The HubSpot **Timeline events** action has an additional **Contact sync mode** option, separate from the sync modes above. When associating timeline events with contacts, you can control whether Navattic creates new HubSpot contacts:

* **All visitors (create contacts)** — Default. Timeline events are attached to the visitor's contact record, creating the contact if one doesn't already exist.
* **Only existing contacts** — Timeline events are only sent for visitors who already have a matching contact in HubSpot. No new contacts are created.

See [Timeline events contact sync mode](/integrations/hubspot#timeline-events-contact-sync-mode) in the HubSpot integration docs for details.

### FAQs

<AccordionGroup>
  <Accordion title="How do Playbooks differ from existing Navattic integrations?">
    Playbooks allow you to filter the Navattic Visitor and Account data that is sent to HubSpot, Salesforce, Marketo, and Slack by configuring different Audiences. For example, do you only want to send data for Repeat Visitors, Visitors who engage with specific demos, or Visitors from a specific industry?

    Playbooks also include **detailed error logs** to support thorough debugging of any failed Runs, which are sent whenever a Visitor or Account is detected viewing your demo. For example:

    <img alt="" />
  </Accordion>

  <Accordion title="What happens to my workspace's existing integrations?">
    All existing field mappings to HubSpot, Salesforce, Marketo, and Slack will continue as-is (here are [all available field mappings](/navattic-field-mappings) as a refresher). You may configure field mappings in your Navattic workspace > Settings > Integrations tab (no changes).

    All existing integrations will now have a corresponding "Playbook" visible in your [Playbooks tab](https://app.navattic.com/w/playbooks), which gives you visibility to the status of each integration. For example, if you were already sending identified Visitors and Accounts to HubSpot, you will see two corresponding Playbooks like this:

    <img alt="" />
  </Accordion>

  <Accordion title="Why does my new Playbook show 0 Runs?">
    Playbook runs are not documented retroactively and will show "0 Runs" if your Playbook was created
    recently (i.e., around the time of this message). However, your integrations have been
    continuously syncing, and your new Playbooks will show more Runs soon as new Visitor or Account
    sessions are detected in your demos.
  </Accordion>

  <Accordion title="Can I retroactively run a Playbook?">
    Yes, you can replay a Playbook to send past Visitor and/or Account data to your integrations. To
    retroactively run a Playbook, visit your Playbook in your Workspace > click the three dots next to
    the save button > **Replay**. Set the **delay between sessions** and the **start** and **end
    dates** for which you want to replay the playbook. See how to [Replay a
    Playbook](https://training.navattic.com/7i801h9).
  </Accordion>

  <Accordion title="How do I create new Playbooks?">
    [Use these steps](https://www.loom.com/share/fc949ad0a7a8461b8297cc57ef008055) to create new Playbooks and visit our [Template Playbooks](https://app.navattic.com/n/playbooks/templates) for inspiration!

    <img alt="" />
  </Accordion>

  <Accordion title="Where do I go to connect new Integrations?">
    You may continue connecting integrations in your Navattic workspace > Settings > Integrations tab. You can also navigate here by clicking the "Integrations" button in the Playbooks tab (shown below).

    <img alt="" />
  </Accordion>

  <Accordion title="How do I setup routing rules to email specific sales reps?">
    You can create a Playbook to setup routing rules to email specific sales reps by connecting the Email integration to your workspace. To setup the Email Integration, visit **Playbooks** > **Integrations** > **Email** > **Connect**. Once the Email Integration is connected, create a Playbook, select the Audience you would like to receive notifications for and choose **Send visitor message to Email** as the Action. You can then select the email you would like notifications to be sent to.

    <Note>
      *Tip: Create a custom audience using the advanced filters so that sales reps receive notifications for companies that match their ICP.*
    </Note>

    <img alt={true} />
  </Accordion>

  <Accordion title="How can I prevent duplicate messages in Slack?">
    To avoid duplicate messages in Slack, toggle on **Only first session** after selecting **Send
    visitor message to Slack** as the Action.
  </Accordion>

  <Accordion title="When does a session end?">
    A session ends and is marked as closed when a user navigates away from the demo or closes the
    page. Once a session is closed, the Navattic fields will be sent to the Integrations that are set
    up with the Playbook. In some instances, Navattic is not able to perfectly capture when a user
    leaves a demo, so there is a secondary condition based on user activity. Every 15 minutes Navattic
    checks all ongoing sessions, and if any of them have not had activity within the last 30 minutes
    (defined by having any activity events), they are marked as closed with the closing time equaling
    the time of the session's most recent activity event.
  </Accordion>

  <Accordion title="I'm not seeing my Slack Channel populate when creating a Slack Playbook?">
    If you're unable to select the Slack channel while creating a Playbook, please ensure that the
    Navattic bot has been added to the channel. You can do this by sending the message @navattic in
    the Slack channel. Additionally, verify that you are a Slack Admin and that the channel is set to
    public. If needed, try searching for the channel using the "Use ID" toggle to locate it more
    easily.
  </Accordion>

  <Accordion title="How can I use Webhooks to send data to Zapier?">
    Use the [Webhook](/integrations/webhook) integration to integrate with a Zapier
    workflow by using a Zap URL. Learn more about triggering [Zaps from
    webhooks](https://help.zapier.com/hc/en-us/articles/8496288690317-Trigger-Zaps-from-webhooks).
  </Accordion>

  <Accordion title="Why isn't internal traffic generating a Playbook run?">
    If you are testing out your Playbook on a live demo and do not see a Playbook run come through,
    you likely have **Hidden Accounts** set up to exclude your domain. Instead, we recommend sending a
    test run by clicking the three dots in the top right corner next to Save > Test run. To confirm if
    Hidden Accounts is set up, visit your Workspace **Settings** > **Hidden Accounts** > Add **Domains
    to exclude.**

    When a session does come from a hidden domain and a Playbook run is recorded, the run shows a **Hidden account** badge instead of the usual Completed status. This lets you distinguish skipped runs from genuine completions at a glance.
  </Accordion>
</AccordionGroup>


# Salesforce
Source: https://docs.navattic.com/integrations/salesforce

Sync demo engagement data to Leads and Contacts for better sales insights.

<Frame>
  <img alt="Salesforce integration" />
</Frame>

<Info>
  Check that you are [Identifying visitors](/tracking/identify/visitors) before setting up the Salesforce integration.
</Info>

The **Salesforce integration** allows you to send engagement data from demos to your Salesforce Opportunity, Leads, Contact, and Accounts.

<Note>
  If your Salesforce org restricts external app authorizations (common in enterprise environments), use the [Salesforce Managed Package](/integrations/salesforce-managed-package) instead.
</Note>

<MediaCard type="demo" title="Salesforce" />

## Setting up the Salesforce Integration

Follow these steps or the demo below to set up the Salesforce integration with Navattic:

<MediaCard type="demo" title="Salesforce Setup" />

<Steps>
  <Step title="Connect Salesforce">
    Navigate to `Integrations` in Settings and select `Salesforce`. Click on `Connect` and follow the instructions to authorize your Salesforce account.

    <img alt="Salesforce Integration" />

    Once you've connected your Salesforce account, a `Playbook` will be automatically created to send engagement data from demos to your Salesforce Opportunity, Leads, Contact, and Accounts.

    You can click view to manage the `Playbook` or refine the `Audience` filters.

    <img alt="Salesforce Integration Connected" />
  </Step>

  <Step title="Set Up Field Mapping">
    [Field mappings](/navattic-field-mappings) allow you to control which pieces of Navattic's data go where. To set up field mapping, go to the **Settings** tab of your Salesforce integration. Open the **Field Mapping** dropdown, and start mapping fields. Fields on the left are Navattic data, and fields on the right are destinations within your Salesfoce instance.

    Navattic provides 20+ Visitor and Account level fields to map. To map fields, you need to first create the recipient field on the Salesforce objects you're mapping to. We recommend starting with these 3 text fields for Contact, Leads, and Account objects.

    <Note>
      Salesforce **reference (lookup) fields** — including `Owner ID` — are supported as mapping targets. If your Salesforce org requires a non-blank Owner ID on Contact inserts, map a Navattic property containing a valid Salesforce User ID to `OwnerId` in field mappings.
    </Note>

    <Note>
      Salesforce **checkbox (boolean) fields** are supported as mapping targets. Map any Navattic property that evaluates to true or false to a Checkbox field on your Salesforce object.
    </Note>

    | **Name**                 | **Description**                                                       | **Type** |
    | ------------------------ | --------------------------------------------------------------------- | -------- |
    | Last Viewed Flow Name    | Human-readable name of the last flow viewed                           | Text     |
    | Last Viewed Project Name | Human-readable name of the last demo viewed                           | Text     |
    | Last Viewed Step Index   | Numerical position of the last step viewed (e.g., "3" for third step) | Text     |
  </Step>

  <Step title="Create a Playbook">
    Once your Salesforce integration is fully set up, visit [Playbooks](/integrations/playbooks) in your Workspace to start pushing data into Salesforce. You can use a Template or create your own Playbook.

    There are six separate Salesforce Actions that you can set up: Sync lead, Sunc contact, Submit session object, and Send notification to opportunity owner (at the Visitor and/or Account level), and Sync account.

    <Note>
      A Playbook consists of [Audiences](/integrations/playbooks) and Actions. You can use one of the default Audiences or you can create your own. If you create your own, remember to add new demos to the Audience if you are choosing to filter by specific demos.
    </Note>
  </Step>

  <Step title="Run a Test">
    Once the Playbook is set up, run a quick test to ensure this test data populates in Salesforce. To run a test, click the three dots next to the **Save** button > **Test run.**
  </Step>

  <Step title="Edit your Salesforce Object page">
    <MediaCard type="demo" title="Salesforce Object" />

    Navigate to your Salesforce object page that you'd like to edit (Opportunity, Lead, Contact, or Account). Select `Edit Page` under the `Setup Menu`.

    <Frame>
      <img alt="Salesforce Opportunity page" />
    </Frame>

    Search for `Dynamic Related List - Single` in the `Components` search field.

    <Frame>
      <img alt="Salesforce component list" />
    </Frame>

    Search for `Navattic Session` in the Related List field. Make sure that the Parent Record is set to the default `Use This Opportunity` (or the relevant Salesforce object).

    <Frame>
      <img alt="Salesforce Navattic Session" />
    </Frame>

    Update the `Related List Fields` to show the following fields:

    * Email
    * Demos
    * Duration (minutes)
    * Full Name
    * Flows
    * Steps Viewed
    * Very Interested Areas
    * Somewhat Interested Areas
    * Not Interested Areas
    * Session ID

    <Frame>
      <img alt="Salesforce Navattic Fields" />
    </Frame>

    Save the Page Builder and exit to the page layout.

    Once a visitor views the interactive demo share link and completes their session, this will be logged in Salesforce.

    <Frame>
      <img alt="Salesforce Opportunity Navattic Data" />
    </Frame>

    <br />

    <Frame>
      <img alt="Salesforce Opportunity Navattic Session Data" />
    </Frame>
  </Step>

  <Step title="[Optional] Set up a Salesforce Reporting Dashboard">
    Once your data is flowing into Salesforce, you can create a dashboard to track how your demos are performing. Check out the video below for a step-by-step walkthrough on setting this up.

    <MediaCard title="Salesforce dashboard" type="video" />

    <Icon icon="party-popper" /> Congratulations -- You've finished setting up Salesforce with Navattic.
  </Step>
</Steps>

## Pipeline impact

Once your Salesforce integration is connected, Navattic automatically pulls opportunity data to power the [Pipeline Impact](/analyze) dashboard. This gives you visibility into how your demos influence pipeline and revenue — showing sourced and influenced pipeline, new accounts, and deal value across your CRM data.

No additional setup is required. The Pipeline Impact dashboard in **Analytics** will reflect your Salesforce opportunities once the integration is active.

<Note>
  The Pipeline Impact dashboard uses Salesforce Opportunity data. Metrics marked with an asterisk (\*) on the dashboard require the Salesforce integration to be connected.
</Note>


# Segment
Source: https://docs.navattic.com/integrations/segment

Send demo events to Segment for advanced analytics and data routing.

<Frame>
  <img alt="Segment integration" />
</Frame>

Integrating with **Segment** allows you to process the raw event data from Navattic in any way you want. Navattic strives to minimize the changes to the Segment integration, and if necessary will provide ample notice for any breaking changes.

Events will be sent to your Segment setup whenever a Visitor session in your demo is marked as closed. The timestamp in each respective event will be an ISO-8601 formatted date-time string that signifies the closing time of the session. The event will also contain information about the session, including a list of the recorded events associated with the session, as well as the corresponding end-user the session relates to, and the company account, if any (company account can be null).

<MediaCard type="video" title="Segment and Webhook" />

### Event Types

Segment supports two different types of events: track and identify. **Track** events contain information about how a visitor interacted with your demo (e.g. viewed a flow step) while **Identify** events contain identification information for the associated visitor and company account.

<Expandable title="Segment Example Track Event">
  ```json theme={null}
  {
    event: 'Session Closed',
    userId: 'abc123',
    properties: {
      timestamp: '2024-07-24T21:21:21.389Z',
      session: {
        closed_at: '2024-07-24T21:21:21.389Z',
        closed_by: 'PAGE_LEAVE',
        recorded_events: [
          {
            id: 'clz0czwjs000008m54x5mbzbp',
            created_at: '2024-07-24T21:21:21.389Z',
            updated_at: '2024-07-24T21:21:21.389Z',
            type: 'VIEW_STEP',
            recorded_step_id: 'clz0d3sq7000608m52n529l9k',
            recorded_step_index: 5,
            recorded_step_common_id: 'clz0d3x7y000708m5bzlwfll2',
            recorded_step_name: 'step name',
            recorded_flow_id: 'clz0d40v5000808m58evb8g7j',
            recorded_flow_name: 'flow name',
            recorded_project_id: 'clz0d45gc000908m5207lhziy',
            recorded_project_name: 'project name',
            recorded_checklist_id: 'clz0d49n2000a08m56936629p',
            recorded_checklist_name: 'checklist name',
            recorded_task_id: 'clz0d4cuu000b08m50rf86gqz',
            recorded_task_name: 'task name',
            url_navigated: '/',
            workspace_id: 'clz0d53sj000c08m5gjn2259r',
            project_id: 'clz0d5acx000d08m5hz4gbxqr',
            project_share_link_id: 'clz0d5m14000e08m599mb3qtl',
            flow_id: 'clz0d5xv5000f08m58grzam4a',
            checklist_id: 'clz0d64g3000g08m5fxdzd6v7',
            project_version_id: 'clz0d6i2i000h08m5hajn057b',
            project_language: 'EN',
            guide_id: 'clz0d7qsh000i08m58mpp9vka',
            session_id: 'clz0d7ufl000j08m583hzej1n',
            end_user_id: 'clz0d7xye000k08m55wos3qra',
            mobile_id: 'clz0d817k000l08m511at4wdx',
            mobile_version_id: 'clz0d84ik000m08m5cr8x1juy'
          },
          ...
        ]
      },
      company_account: {
        total_sessions: 5,
        total_steps: 50,
        total_time: 600,
        total_visitors: 3
      },
      end_user: {
        total_sessions: 2,
        total_steps: 20,
        total_time: 300,
        custom_attributes: [
          {
            id: 'clz0dbz6k000o08m59ouc2ss1',
            created_at: '2024-07-24T21:21:21.389Z',
            updated_at: '2024-07-24T21:21:21.389Z',
            end_user_id: 'clz0dc7ea000q08m54tz14g3u',
            created_by_event_id: 'clz0dcb0f000r08m5awp54t65',
            name: 'attribute name',
            attribute_source: 'OTHER',
            data_type: 'STRING',
            value_string: 'value',
            value_bool: null,
            value_number: null,
            value_json: null,
            value_date_time: null
          },
          ...
        ]
      }
    }
  }
  ```
</Expandable>

<Expandable title="Segment Example Visitor Identify Event">
  ```json theme={null}
  {
    "event": "Visitor Identified",
    "userId": "clzkcqncr000b58dedjgu4bug"
    "properties": {
      "email": "john.doe@acme.com",
      "full_name": "John Doe"
      "company": {
        "account_type": "ACCOUNT",
        "amount_raised": "5000000",
        "city": "San Francisco",
        "clearbit_confidence": "HIGH",
        "country": "United States",
        "created_at": "2024-08-07T21:19:10.011Z",
        "custom_property_values": [],
        "description": "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam vehicula, nisi a commodo efficitur, eros turpis volutpat massa, vitae fermentum felis justo vel purus. Sed sit amet risus id elit bibendum hendrerit in id lacus.",
        "employee_count": 500,
        "engaged": true,
        "estimated_annual_revenue": "75000000",
        "founded_year": 1990,
        "hubspot_account_id": "",
        "id": "clzkcqncr000c58de22xichxv",
        "industry": "Internet Software & Services",
        "industry_group": "Software & Services",
        "linkedin_url": "linkedin.com/company/acme-corporation",
        "name": "acme.com",
        "postal_code": "",
        "salesforce_account_id": "",
        "sector": "Information Technology",
        "state": "California",
        "sub_industry": "Cloud Services",
        "technologies": "",
        "total_sessions": 1,
        "total_steps": 10,
        "total_time": 300,
        "total_visitors": 1,
        "traffic_rank": "very_high",
        "updated_at": "2024-08-07T21:19:10.011Z",
        "website_domain": "acme.com",
        "workspace_id": "clzd3d50a0000d8de3cc32ubs"
      }
  }
  ```
</Expandable>

<Expandable title="Segment Example Company Account Identify Event">
  ```json theme={null}
  {
    "event": "Account Identified",
    "userId": "clzkd1c5i002v58dea2dzc6zo",
    "properties": {
      "account_type": "ACCOUNT",
      "amount_raised": "5000000",
      "city": "San Francisco",
      "clearbit_confidence": "HIGH",
      "country": "United States",
      "created_at": "2024-08-07T21:27:28.711Z",
      "custom_property_values": [],
      "description": "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam vehicula, nisi a commodo efficitur, eros turpis volutpat massa, vitae fermentum felis justo vel purus. Sed sit amet risus id elit bibendum hendrerit in id lacus.",
      "employee_count": 500,
      "engaged": true,
      "estimated_annual_revenue": "75000000",
      "founded_year": 1990,
      "hubspot_account_id": "",
      "id": "clzkd1c5i002w58de8qshfub0",
      "industry": "Internet Software & Services",
      "industry_group": "Software & Services",
      "linkedin_url": "linkedin.com/company/acme-corporation",
      "name": "acme.com",
      "postal_code": "",
      "salesforce_account_id": "",
      "sector": "Information Technology",
      "state": "California",
      "sub_industry": "Cloud Services",
      "technologies": "",
      "total_sessions": 1,
      "total_steps": 10,
      "total_time": 300,
      "total_visitors": 1,
      "traffic_rank": "very_high",
      "updated_at": "2024-08-07T21:27:28.711Z",
      "website_domain": "acme.com",
      "workspace_id": "clzd3d50a0000d8de3cc32ubs"
    }
  }
  ```
</Expandable>


# Slack
Source: https://docs.navattic.com/integrations/slack

Get real-time notifications in Slack when prospects engage with your demos.

<Frame>
  <img alt="Slack integration" />
</Frame>

<Info>
  Check that you are [Identifying visitors](/tracking/identify/visitors) before setting up the Slack integration.
</Info>

Send identified visitor and/or account information directly to Slack. Once a visitor or account has been [identified](/tracking/identify/visitors), send that information to a Slack channel.

## Setting up the Slack Integration

Use this interactive demo or the written steps below to set up your integration.

<MediaCard type="demo" title="Slack Setup" />

<Steps>
  <Step title="Connect to Slack">
    Visit [app.navattic.com](https://app.navattic.com) > Playbooks > Integrations > Slack > Manage > Connect > Log into your Slack account if prompted > Authorize certain permissions within your Slack workspace.

    <Note>
      You can customize the Slack message under **Configuration**. Click **+ Add property** to select which properties to include in the message.
    </Note>
  </Step>

  <Step title="Add the Navattic app to your channel">
    Once you have connected your Slack workspace, navigate to your channel and connect the Navattic app by sending **@navattic** in a message. You must follow this step before adding the channel to your Playbook (see the next step).
  </Step>

  <Step title="Create a Playbook">
    Once your integration for Slack is fully set up, visit [Playbooks](/integrations/playbooks) in your Workspace to start pushing data into Slack. You can use a Template or create your own Playbook.

    There are two Action that you can set up: Send visitor message and Send account message (if you have Accounts set up). Additionally, make sure to select the Slack Channel you want to send data to. You can toggle on **Use ID** if the channels aren't populating in the dropdown.

    <Note>
      A Playbook consists of [Audiences](/integrations/playbooks) and Actions. You can use one of the default Audiences or you can create your own. If you create your own, remember to add new demos to the Audience if you are choosing to filter by specific demos.
    </Note>
  </Step>

  <Step title="See identified Visitors and Accounts in Slack">
    Your connected Slack channel will now receive notifications in real time.

    <img alt="" />
  </Step>
</Steps>


# Webhook
Source: https://docs.navattic.com/integrations/webhook

Send demo events to custom webhooks for flexible integration with any system.

<Frame>
  <img alt="Webhook integration" />
</Frame>

Integrating with Webhook allows you to process the raw event data from Navattic in any way you want. Navattic strives to minimize the changes to the Webhook integration, and if necessary will provide ample notice for any breaking changes.

Events will be sent to your Webhook setup whenever a Visitor session in your demo is marked as closed. The timestamp in each respective event will be an ISO-8601 formatted date-time string that signifies the closing time of the session. The event will also contain information about the session, including a list of the recorded events associated with the session, as well as the corresponding end-user the session relates to, and the company account, if any (company account can be null).

## Example payloads

The following examples show the structure of the `session_closed` payloads for visitor and account events.

```json Visitor event payload expandable theme={null}
{
  "eventType": "session_closed",
  "timestamp": "2026-07-14T18:32:05.000Z",
  "data": {
    "session": {
      "type": "INTERACTIVE_DEMO",
      "recordedGuideSessionId": "clx8f2k1a0003abcd12345678",
      "createdAt": "2026-07-14T18:20:11.000Z",
      "closedAt": "2026-07-14T18:32:05.000Z",
      "mostRecentDemoName": "Acme Product Tour",
      "mostRecentProjectId": "clx8f0aaa0001abcd12345678",
      "mostRecentShareLinkId": "clx8f0bbb0002abcd12345678",
      "recordedEvents": [
        {
          "id": "clx8f3xyz0004abcd12345678",
          "createdAt": "2026-07-14T18:20:12.000Z",
          "updatedAt": "2026-07-14T18:20:12.000Z",
          "type": "VIEW_STEP",
          "recordedStepId": "clx8f0ccc0005abcd12345678",
          "recordedStepIndex": 0,
          "recordedStepCommonId": "clx8f0ddd0006abcd12345678",
          "recordedStepName": "Welcome",
          "recordedFlowId": "clx8f0eee0007abcd12345678",
          "recordedFlowName": "Getting Started",
          "recordedProjectId": "clx8f0aaa0001abcd12345678",
          "recordedProjectName": "Acme Product Tour",
          "recordedChecklistId": "",
          "recordedChecklistName": "",
          "recordedTaskId": "",
          "recordedTaskName": "",
          "recordedInterestId": "",
          "recordedInterestName": "",
          "urlNavigated": "",
          "workspaceId": "clx8ezzzz0000abcd12345678",
          "projectId": "clx8f0aaa0001abcd12345678",
          "projectShareLinkId": "clx8f0bbb0002abcd12345678",
          "flowId": "clx8f0eee0007abcd12345678",
          "checklistId": null,
          "projectVersionId": "clx8f0fff0008abcd12345678",
          "projectLanguage": "EN",
          "guideId": "clx8f0ggg0009abcd12345678",
          "sessionId": "clx8f2k1a0003abcd12345678",
          "endUserId": "clx8f1hhh0010abcd12345678",
          "mobileId": null,
          "mobileVersionId": null
        }
      ]
    },
    "endUser": {
      "id": "clx8f1hhh0010abcd12345678",
      "createdAt": "2026-06-01T09:14:00.000Z",
      "updatedAt": "2026-07-14T18:32:05.000Z",
      "mostRecentEmail": "jane.doe@example.com",
      "mostRecentName": "Jane Doe",
      "mostRecentCompany": "Example Corp",
      "mostRecentCountry": "United States",
      "mostRecentCountryRegion": "California",
      "mostRecentCity": "San Francisco",
      "converted": true,
      "navigated": true,
      "engaged": true,
      "workspaceId": "clx8ezzzz0000abcd12345678",
      "sharedId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "companyAccountId": "clx8f4iii0011abcd12345678",
      "customPropertyValues": [
        {
          "propertyId": "clx8f6kkk0013abcd12345678",
          "value": "jane.doe@example.com",
          "createdAt": "2026-07-14T18:21:00.000Z",
          "source": "FORM",
          "property": {
            "id": "clx8f6kkk0013abcd12345678",
            "name": "Email",
            "object": "VISITOR"
          }
        }
      ],
      "recordedEvents": []
    },
    "companyAccount": {
      "id": "clx8f4iii0011abcd12345678",
      "createdAt": "2026-06-01T09:14:00.000Z",
      "updatedAt": "2026-07-14T18:32:05.000Z",
      "workspaceId": "clx8ezzzz0000abcd12345678",
      "name": "Example Corp",
      "websiteDomain": "example.com",
      "engaged": true,
      "description": "Example Corp builds widgets.",
      "linkedinUrl": "https://linkedin.com/company/example",
      "sector": "Information Technology",
      "industryGroup": "Software & Services",
      "industry": "Software",
      "subIndustry": "Application Software",
      "employeeCount": 250,
      "estimatedAnnualRevenue": "50000000",
      "amountRaised": "12000000",
      "trafficRank": "high",
      "foundedYear": 2015,
      "city": "San Francisco",
      "state": "CA",
      "country": "US",
      "postalCode": "94105",
      "technologies": "react,aws",
      "clearbitConfidence": null,
      "customPropertyValues": []
    }
  }
}
```

```json Account event payload expandable theme={null}
{
  "eventType": "session_closed",
  "timestamp": "2026-07-14T18:32:05.000Z",
  "data": {
    "id": "clx8f4iii0011abcd12345678",
    "createdAt": "2026-06-01T09:14:00.000Z",
    "updatedAt": "2026-07-14T18:32:05.000Z",
    "workspaceId": "clx8ezzzz0000abcd12345678",
    "name": "Example Corp",
    "websiteDomain": "example.com",
    "engaged": true,
    "description": "Example Corp builds widgets.",
    "linkedinUrl": "https://linkedin.com/company/example",
    "sector": "Information Technology",
    "industryGroup": "Software & Services",
    "industry": "Software",
    "subIndustry": "Application Software",
    "employeeCount": 250,
    "estimatedAnnualRevenue": "50000000",
    "amountRaised": "12000000",
    "trafficRank": "high",
    "foundedYear": 2015,
    "city": "San Francisco",
    "state": "CA",
    "country": "US",
    "postalCode": "94105",
    "technologies": "react,aws",
    "clearbitConfidence": null,
    "customPropertyValues": [
      {
        "propertyId": "clx8f7lll0014abcd12345678",
        "value": "Enterprise",
        "createdAt": "2026-07-14T18:21:00.000Z",
        "source": "ENRICHMENT",
        "property": {
          "id": "clx8f7lll0014abcd12345678",
          "name": "Plan Tier",
          "object": "ACCOUNT"
        }
      }
    ]
  }
}
```

## Payload reference

There are two webhook action types, which share the same envelope but differ in what `data` contains:

* **Visitor event** — the full session, visitor, and account details
* **Account event** — the company account details only

All timestamps are ISO 8601 strings. Large numeric values (e.g. `estimatedAnnualRevenue`) are sent as strings.

### Top-level envelope

| Field       | Type   | Description                                                                                                                      |
| ----------- | ------ | -------------------------------------------------------------------------------------------------------------------------------- |
| `eventType` | string | The type of event. Currently always `session_closed`.                                                                            |
| `timestamp` | string | When the session closed.                                                                                                         |
| `data`      | object | The event body. For visitor events: `{ session, endUser, companyAccount }`. For account events: the company account object only. |

### `data.session` — the demo session

Fields common to all sessions:

| Field                | Type   | Description                                                                                 |
| -------------------- | ------ | ------------------------------------------------------------------------------------------- |
| `type`               | string | `INTERACTIVE_DEMO` or `AGENT_DEMO`.                                                         |
| `createdAt`          | string | When the session started.                                                                   |
| `closedAt`           | string | When the session ended.                                                                     |
| `mostRecentDemoName` | string | Name of the demo the visitor viewed.                                                        |
| `recordedEvents`     | array  | The activity events recorded during this session (see [Recorded events](#recorded-events)). |

Additional fields for interactive demo sessions (`type: INTERACTIVE_DEMO`):

| Field                    | Type   | Description                                                                                                                     |
| ------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------------- |
| `recordedGuideSessionId` | string | Unique ID of the session.                                                                                                       |
| `mostRecentProjectId`    | string | ID of the demo (project) the visitor viewed most recently.                                                                      |
| `mostRecentShareLinkId`  | string | ID of the share link used to open the demo, if any.                                                                             |
| `shareLink`              | object | Present when the session came from a share link: `{ id, createdBy: { id, email } }` — the link and the teammate who created it. |

Additional fields for AI agent demo sessions (`type: AGENT_DEMO`):

| Field                | Type   | Description                          |
| -------------------- | ------ | ------------------------------------ |
| `agentDemoSessionId` | string | Unique ID of the agent demo session. |
| `agentDemoId`        | string | ID of the agent demo.                |

### `data.endUser` — the visitor

| Field                     | Type           | Description                                                                                            |
| ------------------------- | -------------- | ------------------------------------------------------------------------------------------------------ |
| `id`                      | string         | Unique visitor ID.                                                                                     |
| `createdAt`               | string         | When the visitor was first seen.                                                                       |
| `updatedAt`               | string         | When the visitor record was last updated.                                                              |
| `sharedId`                | string         | Stable visitor identifier used across sessions.                                                        |
| `workspaceId`             | string         | ID of the Navattic workspace the visitor belongs to.                                                   |
| `companyAccountId`        | string \| null | ID of the company account the visitor is matched to, if any.                                           |
| `mostRecentEmail`         | string         | Visitor's most recently captured email address.                                                        |
| `mostRecentName`          | string         | Visitor's most recently captured name.                                                                 |
| `mostRecentCompany`       | string         | Visitor's most recently captured company name.                                                         |
| `mostRecentCountry`       | string         | Country from the visitor's most recent session.                                                        |
| `mostRecentCountryRegion` | string         | State/region from the visitor's most recent session.                                                   |
| `mostRecentCity`          | string         | City from the visitor's most recent session.                                                           |
| `converted`               | boolean        | Whether the visitor has ever converted (e.g. clicked a CTA).                                           |
| `navigated`               | boolean        | Whether the visitor has ever navigated through a demo.                                                 |
| `engaged`                 | boolean        | Whether the visitor has ever engaged with a demo.                                                      |
| `customPropertyValues`    | array          | Custom property values set on the visitor (see [Custom property values](#custom-property-values)).     |
| `recordedEvents`          | array          | The session's activity events, mirrored here for convenience (same shape as `session.recordedEvents`). |

### `data.companyAccount` — the account

`null` on visitor events when no account could be matched (or account info is unavailable for the visitor). This object is the entire `data` payload for account events.

| Field                    | Type           | Description                                                                                        |
| ------------------------ | -------------- | -------------------------------------------------------------------------------------------------- |
| `id`                     | string         | Unique account ID.                                                                                 |
| `createdAt`              | string         | When the account was first seen.                                                                   |
| `updatedAt`              | string         | When the account record was last updated.                                                          |
| `workspaceId`            | string         | ID of the Navattic workspace the account belongs to.                                               |
| `websiteDomain`          | string         | The account's website domain (e.g. `acme.com`).                                                    |
| `name`                   | string \| null | Company name.                                                                                      |
| `engaged`                | boolean        | Whether anyone from the account has engaged with a demo.                                           |
| `description`            | string \| null | Company description (from enrichment).                                                             |
| `linkedinUrl`            | string \| null | Company LinkedIn URL.                                                                              |
| `sector`                 | string \| null | Company sector.                                                                                    |
| `industryGroup`          | string \| null | Industry group.                                                                                    |
| `industry`               | string \| null | Industry.                                                                                          |
| `subIndustry`            | string \| null | Sub-industry.                                                                                      |
| `employeeCount`          | number \| null | Estimated employee count.                                                                          |
| `estimatedAnnualRevenue` | string \| null | Estimated annual revenue.                                                                          |
| `amountRaised`           | string \| null | Total funding raised.                                                                              |
| `trafficRank`            | string \| null | Website traffic rank.                                                                              |
| `foundedYear`            | number \| null | Year the company was founded.                                                                      |
| `city`                   | string \| null | Company HQ city.                                                                                   |
| `state`                  | string \| null | Company HQ state.                                                                                  |
| `country`                | string \| null | Company HQ country.                                                                                |
| `postalCode`             | string \| null | Company HQ postal code.                                                                            |
| `technologies`           | string \| null | Technologies detected on the company's website.                                                    |
| `clearbitConfidence`     | string \| null | Confidence level of the enrichment match.                                                          |
| `customPropertyValues`   | array          | Custom property values set on the account (see [Custom property values](#custom-property-values)). |

### Custom property values

Each entry in `endUser.customPropertyValues` and `companyAccount.customPropertyValues`:

| Field        | Type   | Description                                                                                                                                       |
| ------------ | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `propertyId` | string | ID of the custom property.                                                                                                                        |
| `value`      | string | The property value.                                                                                                                               |
| `createdAt`  | string | When the value was set.                                                                                                                           |
| `source`     | string | How the value was captured: `FORM`, `IDENTIFY`, `QUERY_PARAMS`, `REDUCER`, `SHARE_LINK`, `PRESENTATION`, `ENRICHMENT`, `INTEGRATION`, or `OTHER`. |
| `property`   | object | The property definition: `{ id, name, object }`, where `object` is `END_USER` or `COMPANY_ACCOUNT`.                                               |

### Recorded events

Each entry in `session.recordedEvents` (and mirrored in `endUser.recordedEvents`) is one activity event from the session:

| Field                                           | Type           | Description                                                                                                                                                                                               |
| ----------------------------------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `id`                                            | string         | Unique event ID.                                                                                                                                                                                          |
| `createdAt` / `updatedAt`                       | string         | When the event occurred / was last updated.                                                                                                                                                               |
| `type`                                          | string         | Event type: `VIEW_STEP`, `START_FLOW`, `COMPLETE_FLOW`, `START_CHECKLIST`, `OPEN_CHECKLIST`, `CLOSE_CHECKLIST`, `IDENTIFY_USER`, `ENGAGE`, `CONVERTED`, `NAVIGATE`, `COMPLETE_TASK`, or `SESSION_CLOSED`. |
| `recordedStepId`                                | string         | ID of the demo step the event occurred on.                                                                                                                                                                |
| `recordedStepIndex`                             | number         | Position of the step within its flow.                                                                                                                                                                     |
| `recordedStepCommonId`                          | string         | Stable step identifier shared across demo versions.                                                                                                                                                       |
| `recordedStepName`                              | string         | Name of the step.                                                                                                                                                                                         |
| `recordedFlowId` / `recordedFlowName`           | string         | ID and name of the flow.                                                                                                                                                                                  |
| `recordedProjectId` / `recordedProjectName`     | string         | ID and name of the demo (project).                                                                                                                                                                        |
| `recordedChecklistId` / `recordedChecklistName` | string         | ID and name of the checklist, for checklist events.                                                                                                                                                       |
| `recordedTaskId` / `recordedTaskName`           | string         | ID and name of the checklist task, for task events.                                                                                                                                                       |
| `recordedInterestId` / `recordedInterestName`   | string         | ID and name of the interest, for interest-driven demos.                                                                                                                                                   |
| `urlNavigated`                                  | string         | Destination URL, for `NAVIGATE` events.                                                                                                                                                                   |
| `workspaceId`                                   | string         | ID of the Navattic workspace.                                                                                                                                                                             |
| `projectId`                                     | string \| null | ID of the demo the event belongs to.                                                                                                                                                                      |
| `projectShareLinkId`                            | string \| null | ID of the share link the session came from.                                                                                                                                                               |
| `flowId`                                        | string \| null | ID of the flow the event belongs to.                                                                                                                                                                      |
| `checklistId`                                   | string \| null | ID of the checklist the event belongs to.                                                                                                                                                                 |
| `projectVersionId`                              | string \| null | ID of the published demo version being viewed.                                                                                                                                                            |
| `projectLanguage`                               | string \| null | Language of the demo version being viewed.                                                                                                                                                                |
| `guideId`                                       | string \| null | ID of the guide shown during the event.                                                                                                                                                                   |
| `sessionId`                                     | string \| null | ID of the session the event belongs to.                                                                                                                                                                   |
| `endUserId`                                     | string         | ID of the visitor who triggered the event.                                                                                                                                                                |
| `mobileId` / `mobileVersionId`                  | string \| null | IDs of the mobile demo and version, for mobile demos.                                                                                                                                                     |

### Request headers

| Header          | Value                                                                                |
| --------------- | ------------------------------------------------------------------------------------ |
| `Content-Type`  | `application/json`                                                                   |
| `User-Agent`    | `navattic-tour`                                                                      |
| `Authorization` | Only sent when configured on the webhook: `Basic <credentials>` or `Bearer <token>`. |

## Testing

A free service like [webhook.site](https://webhook.site/) can be an easy way to get started and test the Webhook integration.

<Info>
  Webhook.site is a public webhook testing service, so it is recommended only to send test data when
  using this, as you could inadvertently expose customer event data.
</Info>

<MediaCard type="video" title="Segment and Webhook" />

## Opportunity owner fields

When a Launchpad presentation is connected to a Salesforce opportunity, the webhook payload includes two additional fields for the opportunity owner:

| Field                   | Description                                                   |
| ----------------------- | ------------------------------------------------------------- |
| `opportunityOwnerEmail` | Email address of the Salesforce user who owns the opportunity |
| `opportunityOwnerId`    | Salesforce user ID of the opportunity owner                   |

These fields let you route webhook events to the right rep — for example, triggering a Slack notification or Zapier workflow that notifies the opportunity owner when their prospect views a demo.

## Send data to Zapier using Webhook

Sending webhook events to Zapier allows you further filter and format the data within Zapier before sending it to additional destinations like Google Sheets, Gmail, Notion, or more. This [setup demo](https://training.navattic.com/ss60pxn) includes all the steps you need to send data from Navattic to Zapier.

<MediaCard type="demo" title="Zapier Setup" />

<Info>
  Use the Webhook integration to integrate with a Zapier workflow using a Zap URL. Learn more about
  triggering [Zaps from
  webhooks](https://help.zapier.com/hc/en-us/articles/8496288690317-Trigger-Zaps-from-webhooks).
</Info>


# ZoomInfo
Source: https://docs.navattic.com/integrations/zoominfo

Enrich visitor and account data by connecting Navattic demo engagement with ZoomInfo.

The ZoomInfo integration lets you send demo engagement data from Navattic to ZoomInfo so you can enrich your prospect and account records with visitor activity.

Once connected, you can use [Playbooks](/integrations/playbooks) to:

* **Send visitor info to ZoomInfo** — Sync individual visitor engagement data to ZoomInfo contact records
* **Send account info to ZoomInfo** — Sync company-level engagement data to ZoomInfo account records

## Setting up the ZoomInfo integration

<Steps>
  <Step title="Get your ZoomInfo API key">
    Log in to your ZoomInfo account and locate your API key. You can typically find this under your account settings or developer portal.
  </Step>

  <Step title="Connect ZoomInfo in Navattic">
    In Navattic, navigate to **Settings** > **Integrations** and select **ZoomInfo**. Click **Connect** and enter your ZoomInfo API key in the field provided. Click **Connect** to save.

    <Note>
      Your API key is required to authenticate the connection. If you don't have one, contact your ZoomInfo account administrator.
    </Note>
  </Step>

  <Step title="Create a Playbook">
    With ZoomInfo connected, go to [Playbooks](/integrations/playbooks) to define when and how Navattic sends data to ZoomInfo.

    There are two ZoomInfo actions available:

    * **Send visitor info to ZoomInfo** — Triggers on visitor-level engagement and sends the visitor's data to ZoomInfo
    * **Send account info to ZoomInfo** — Triggers on account-level engagement and sends the account's data to ZoomInfo

    Choose the action that matches what you want to track, set your audience criteria, and save the Playbook.
  </Step>

  <Step title="Run a test">
    After saving your Playbook, click the three-dot menu next to the **Save** button and select **Test run** to verify that data flows correctly to ZoomInfo.
  </Step>
</Steps>

## What data is synced

The specific fields sent to ZoomInfo depend on the visitor and account data Navattic has captured. To get the most out of the integration, make sure you are [identifying visitors](/tracking/identify/visitors) in your demos so Navattic has contact information to sync.

<Note>
  ZoomInfo does not use field mappings. Data is sent using ZoomInfo's standard input format. If you need control over which fields are synced, use the [Webhook integration](/integrations/webhook) for a fully custom payload.
</Note>

## Disconnecting ZoomInfo

To remove the ZoomInfo integration, navigate to **Settings** > **Integrations** > **ZoomInfo** and click **Disconnect**. Any Playbooks using ZoomInfo actions will stop sending data once the integration is disconnected.


# Launchpad
Source: https://docs.navattic.com/launchpad-overview

Streamlined access to demos for sales teams.

<Frame>
  <img alt="Launchpad" />
</Frame>

## Introducing Launchpad

<Icon icon="circle-arrow-out-up-right" /> **Launchpad** is the way to scale interactive demos across
your sales department. With Launchpad, your sellers will have a streamlined way to access demos that
help to shorten sales cycles, improve the buying experience, and close more deals.

Learn more about Launchpad:

<CardGroup>
  <Card icon={<img src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/icons/launchpad-logo.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=dad3c35c02234ff5de704cd11c7cba78"/>} title="Launchpad docs" href="/launchpad">
    Streamlined access to demos for sales teams.
  </Card>
</CardGroup>


# Prepare your demos
Source: https://docs.navattic.com/launchpad/build/prepare

Select your gold-standard demos to showcase to your sales team.

<Frame>
  <img alt="Launchpad" />
</Frame>

Empower your sales teams to deliver top-performing demos with confidence. In order to do that, you'll have to first create and organize your best demos so that your sales team knows what to look for. Follow the below steps to prepare the demos in your workspace and your sales team streamlined access to the demos relevant to them:

<Steps>
  <Step title="Create a sales team">
    First, you'll create a new team in your workspace for your sales team.
    Navgigate to <Icon icon="users" /> <a href="https://app.navattic.com/w/settings/teams">
    Team Settings
    </a> and click `+ Create Team`. Name the team something recognizable for your
    organization ex. "Sales team" or "North America Sales" for example.

    <img alt="Create team" />

    <Info>
      Using Launchpad for multiple sales teams in your org (ex. split by segmentation or territory)? Create a team for each to allow sales managers to monitor each team seperately and/or give access to different demos relevant to their needs.
    </Info>
  </Step>

  <Step title="Create a board for the sales team">
    Navigate to <Icon icon="grid-3x3" /> <a href="https://app.navattic.com/w/settings/boards">Board Settings</a> and create a board for your newly created team. You can name the board anything memorable for your team ex. "Sales" or "Outbound demos". Any number of boards can be created for Launchpad.

    <img alt="Create board" />

    <Info>
      Overtime you can create boards per use case, product, team, etc. We recommend you start simple and create boards based on your organization's initial needs.
    </Info>
  </Step>

  <Step title="Add demos to the new board(s)">
    Under <Icon icon="layout-grid" /> <a href="https://app.navattic.com/w/settings/teams">Product demos</a>, find the top-performing demos relevant to your
    sales team. You can use the filters to narrow down the demos by activity or
    labels.

    Consult your top sales reps (AEs, SEs, BDRs, and SDRs) on what areas of the product are particuarly important for them to show off in demos.

    <img alt="Add demo to board" />

    <Tip>
      To identify top-performing demos for your sales team, prioritize demos that showcase an **"aha" moment** of your product.
    </Tip>
  </Step>
</Steps>

Congratulations -- you've created a board for your sales team with some initial demos for them to start sharing. Next, learn how to create demos that will be particuarly useful for sales use cases:

<CardGroup>
  <Card title="Personalizing demos" icon="user-pen" href="/launchpad/demos/personalized">
    Make demos personalized by adding user and account variables.
  </Card>

  <Card title="Building interest demos" icon="chart-no-axes-column-increasing" href="/launchpad/demos/interest">
    Unlock a powerful insight - what features prospects are interested in seeing.
  </Card>

  <Card title="Custom demos" icon="circle-fading-plus" href="/launchpad/demos/custom">
    Enable your sales team to assemble custom demos from pre-built templates.
  </Card>
</CardGroup>


# Custom demos
Source: https://docs.navattic.com/launchpad/demos/custom

Enable your sales team to assemble custom demos from pre-built templates.

<img alt="Custom Demo" />

<Icon icon="circle-fading-plus" /> **Custom demos** are a powerful way for your Sales team to follow up with prospects with relevant content based on their interests. It strikes the right balance between sharing a *standardized* experience while still allowing reps to customize based on the needs of the prospect.

There's nothing more empowering for teams than feeling like they have control of what's included in demos and can iterate themselves -- Custom demos makes this easy!

While it takes some prep work to create the templates, it's a time investment that will pay dividends for your sales team. Sales reps will be able to quickly re-arrange template flows in a way that best suits their needs. This saves you time and effort in the long run from having to building seperate demos for all variations of features.

#### How to create interest content

Interest flows and Interest videos are the building blocks of custom demos. They allow reps to create a custom demo by assembling pre-built templates.

It's highly recommended to create interest templates for your reps so that when they join the workspace they can create custom demos quickly for their deals.

<Steps>
  <Step title="Create a New Template">
    Navigate to **Interest Templates** and click on `+ Add Template`. Choose either to create a blank template or start from an existing flow.

    If you already have some demos built out, we recommend you use an existing flow so that you have a starting place to work from.

    <Frame>
      <img alt="Interest templates empty" />
    </Frame>
  </Step>

  <Step title="Enter template details">
    Select an `Interest` for the type of content you want to include and enter. Enter a checklist task `name` and `description` (optional). These will be displayed on the checklist if one is generated for the demo so it's helpful to use friendly public names.

    <img alt="Create interest template" />
  </Step>

  <Step title="Edit the template">
    Select an `Interest` for the type of content you want to include and enter.

    <img alt="Create interest template" />
  </Step>

  <Step title="Publish the template">
    Once you've finished editing the template, click the `Publish` button to make it available for use in custom demos.

    <img alt="Publish interest template" />
  </Step>
</Steps>

### How reps share demos

Once you've created interest templates, reps can use them to create custom demos. To create a custom demo, follow these steps:

<CardGroup>
  <Card title="Sharing demos" href="/launchpad/share/demos">
    Sharing demos from Launchpad
  </Card>
</CardGroup>

<p>
  <Icon icon="party-popper" /> **Congratulations** -- you've finished building your first
  <Icon icon="circle-fading-plus" /> **Custom demo**. Custom demos are a powerful way to follow up
  with a *relevant* demo once you know a prospect's interest. Learn more about how to use custom
  demos as a [Post-call follow-up](/launchpad/use-cases/post-call).
</p>

Once you've prepared your workspace with initial demos, you're ready for your sales team. Learn what steps to follow to invite your sales team to the workspace:

<CardGroup>
  <Card title="Adding the sales team" icon="user-round-plus" href="/launchpad/invite/add-reps">
    Customize your docs to your company's colors and brands
  </Card>
</CardGroup>


# Demos for sales teams
Source: https://docs.navattic.com/launchpad/demos/for-sellers

Learn how to create purpose-built demos for your sales team

**Sales teams** are unique, and every deal deserves a demo that feels tailored, not generic. Instead of relying on “canned” demos, empower your reps to deliver experiences that speak directly to each prospect’s needs.

Give your sales team the power to deliver demos that truly resonate with each prospect. From custom demos to sandbox environments and offline presentations, these purpose-built demos help you win deals by matching every buyer’s needs.

<CardGroup>
  <Card title="Demo Library" icon="library" href="/launchpad/demos/library">
    Access and organize all your demos in one unified library.
  </Card>

  <Card title="Interest demos" icon="chart-no-axes-column" href="/launchpad/demos/interest">
    Unlock a powerful insight - what features prospects are interested in seeing.
  </Card>
</CardGroup>

With sandbox and offline demos, you can deliver personalized, engaging experiences—whether you’re tailoring a walkthrough for an account or showcasing your product at a tradeshow.

<CardGroup>
  <Card title="Sandbox demos" icon={<img src="https://mintcdn.com/navattic-app/F-ocMwTZ1ZRknPbL/images/icons/sandbox.svg?fit=max&auto=format&n=F-ocMwTZ1ZRknPbL&q=85&s=4160abd437d29288d56a6ec31ed9ab69" />} href="/launchpad/demos/sandbox">
    Make demos personalized by adding user and account properties.
  </Card>

  <Card title="Offline demos" icon={<img src="https://mintcdn.com/navattic-app/F-ocMwTZ1ZRknPbL/images/icons/offline.svg?fit=max&auto=format&n=F-ocMwTZ1ZRknPbL&q=85&s=0a33f3be65cc6e3844dd2163a9c86400" />} href="/launchpad/demos/offline">
    Use your demos offline at tradeshows and conferences.
  </Card>

  <Card title="Personalized demos" icon="user-pen" href="/launchpad/demos/personalized">
    Make demos personalized by adding user and account properties.
  </Card>
</CardGroup>


# Interest demos
Source: https://docs.navattic.com/launchpad/demos/interest

Unlock a powerful insight - what features your prospects are interested in.

<Frame>
  <img alt="Interest Levels" />
</Frame>

## Interest Level demos

We highly recommend leveraging <Icon icon="chart-no-axes-column" /> **Interest Level demos** across your sales teams to gain valuable insights into prospect interests and create a better, more relevant experience for your buyers.

Interest level demos help create a better buying experience for both buyers and sellers:

<Tabs>
  <Tab title="For buyers">
    **Relevant content**

    <div>
      Buyers benefit from Interest demos by receiving a tailored experience that highlights the most relevant features for their specific needs.
    </div>
  </Tab>

  <Tab title="For sellers">
    **Interests insight**

    <div>
      One of the most valuable insights you can gain from interactive demos is understanding the level of interest prospects have in different features. Sales reps can use this insight to tailor their live demos and highlight the most relevant features for each prospect.
    </div>
  </Tab>
</Tabs>

## How Interests and Flows work together

Understanding the relationship between **Interests** and **Flows** helps you control exactly what content appears in a prospect's checklist.

<AccordionGroup>
  <Accordion title="Key concepts">
    * **Flows** are individual items in the checklist. Each flow represents a specific piece of demo content (e.g., "Payments Overview" or "Invoice Management").
    * **Interests** are groupings of flows. They represent broader product or feature areas (e.g., "Payments", "Invoicing"). An Interest can have one or more flows assigned to it.
    * **Interest Forms** allow prospects to indicate which Interests they care about. Based on their selections, the associated flows are added to their checklist.
  </Accordion>

  <Accordion title="What happens when a prospect selects an Interest">
    When a prospect indicates positive interest in an Interest (e.g., selects "Very Interested" in your Interest Form), all flows assigned to that Interest **that were included in the share link's content selection** are added to the checklist as separate items.

    For example, if you have an Interest called "Payments" with three flows assigned to it:

    * Payment Dashboard Overview
    * Creating an Invoice
    * Processing Refunds

    And all three flows are included in the share link, then when a prospect selects "Payments," all three flows appear as separate checklist items.
  </Accordion>

  <Accordion title="How to add multiple flows to a single Interest">
    To have multiple flows added when an Interest is selected:

    1. Create the Interest (e.g., "Reporting")
    2. Create multiple flows and assign them to that Interest
    3. All assigned flows will be added to the checklist when a prospect selects that Interest
  </Accordion>
</AccordionGroup>

### Controlling which flows are added

There are two ways to control which flows appear when an Interest is selected:

<CardGroup>
  <Card title="Use separate Interests" icon="layer-group">
    If you don't want certain flows to be grouped together, assign them to different Interests. Each Interest acts as an independent grouping, so prospects can select only the ones relevant to them.
  </Card>

  <Card title="Exclude from share link" icon="filter">
    When creating a share link, use the **content selection step** to exclude specific flows. Only flows included in the share link's content selection will be added to the checklist, even if they're assigned to a selected Interest.
  </Card>
</CardGroup>

<Info>
  **Example**: You have an Interest called "Analytics" with 5 flows. For a particular prospect, you only want to show 2 of those flows. When creating the share link, deselect the 3 flows you want to exclude. If the prospect selects "Analytics," only the 2 included flows will appear in their checklist.
</Info>

## Building an Interest Level Demo

Interest Level demos are created through the Launchpad share flow. Follow these steps to set up an Interest Level demo for discovery:

<Steps>
  <Step title="Create an Interest demo with Interest Areas">
    First, create an Interest demo using the Interest Area form type. On the Product Demo page, select `+ Create new`, then choose `Generating interest demo` and select `Interest areas` as your form type.

    Learn more about creating Interest demos in our [Interest demo guide](/demos/interest).

    <img alt="Select interests for your demo" />
  </Step>

  <Step title="Build your Interest flows">
    Create flows for each Interest area that you want prospects to be able to explore. Each Interest should have one or more flows assigned to it (5-15 steps recommended per flow).

    <Info>
      **Tip**: You can link multiple flows to a single Interest. When that Interest is selected, all its Flows appear in the Checklist in the order listed in the Flows menu.
    </Info>

    <img alt="Generated interest flows" />
  </Step>

  <Step title="Share with Interest Level form">
    When a sales rep shares the demo through Launchpad, they can choose to use an **Interest Level** form instead of the default Interest Area form. During the share flow, select `Interest Level` as the form type.

    This replaces the standard checkbox interface with a ranking interface where prospects can indicate their level of interest (High, Medium, or Low) for each topic.
  </Step>
</Steps>

<Icon icon="party-popper" /> **Congratulations** -- you've finished building your first <Icon icon="chart-no-axes-column" /> **Interest Levels demo** and it's ready to share!

Interest level demos are useful at several stages of the sales cycle, but are particularly useful for collecting interest during [Pre-call Discovery](/launchpad/use-cases/pre-call-discovery).

Interest Level demos are a powerful way to collect prospect interest.

You can also enable your reps to assemble Interest Level [custom demos](/launchpad/demos/custom) from pre-built Interest flows. Follow the below steps to get started:

<CardGroup>
  <Card title="Building custom demos" icon="circle-fading-plus" href="/launchpad/demos/custom">
    Enable your sales team to assemble custom demos from pre-built templates.
  </Card>
</CardGroup>


# Demo Library
Source: https://docs.navattic.com/launchpad/demos/library

Access and organize all your demos in one unified library - standard demos, custom flows, and videos.

<img alt="Demo Library" />

The **Demo Library** provides a unified view of all your demo content in one place. Sales teams can browse, search, and share demos without switching between different sections.

## How the Demo Library Works

### For Admins

Admins create the building blocks that reps will use:

1. **Standard Demos** - Complete, ready-to-share demos for common use cases
2. **Custom Flows** - Modular flow templates organized by interest/topic
3. **Custom Videos** - Video content that can be combined with flows

### For Reps

Reps access the Demo Library to:

* Browse all available demo content in one unified view
* Search and filter by interest, tags, or keywords
* View demo metadata and descriptions
* Share standard demos directly, or assemble custom demos from flows and videos

<Tip>
  Reps can assemble multiple **Custom Flows** and **Custom Videos** together to create personalized demos tailored to each prospect's interests.
</Tip>

## Creating Content for the Library

### Creating a Custom Flow

Custom flows are the building blocks for personalized demos. To create one:

<Steps>
  <Step title="Navigate to Demo Library">
    Navigate to **Demo Library** in Launchpad and click **+ Add**.
  </Step>

  <Step title="Select Custom Flow">
    Select **Custom Flow** from the options. Choose to create from scratch or start from an existing flow.
  </Step>

  <Step title="Configure the flow">
    Configure the flow details:

    * Select an **Interest** category (e.g., "Analytics", "Reporting")
    * Enter a **Name** that will display in the checklist
    * Add an optional **Description**
  </Step>

  <Step title="Edit and design">
    Edit and design your flow content.
  </Step>

  <Step title="Publish">
    Click **Publish** to make it available in the library.
  </Step>
</Steps>

### Creating a Custom Video

Videos can be combined with flows to enrich custom demos:

<Steps>
  <Step title="Navigate to Demo Library">
    Navigate to **Demo Library** in Launchpad.
  </Step>

  <Step title="Add Custom Video">
    Click **+ Add** and select **Custom Video**.
  </Step>

  <Step title="Upload or record">
    Upload or record your video content.
  </Step>

  <Step title="Assign Interest & Tags">
    Assign an **Interest** category and add **Tags** to organize your video.
  </Step>

  <Step title="Publish">
    Publish to make it available.
  </Step>
</Steps>

### Adding Standard Demos

Standard demos are complete projects that reps share without modification:

<Steps>
  <Step title="Create or select demo">
    Create or select an existing demo project.
  </Step>

  <Step title="Add to library">
    Add it to the Demo Library with appropriate tags and interests.
  </Step>

  <Step title="Share">
    Reps can then share it directly from the library.
  </Step>
</Steps>

## How Reps Share Demos

Once content is available in the Demo Library, reps can share demos:

<Card title="Sharing demos" icon="share" href="/launchpad/share/demos">
  Learn how to share demos from Launchpad
</Card>

## Next Steps

Once you've prepared your Demo Library with content, invite your sales team:

<Card title="Adding the sales team" icon="users" href="/launchpad/invite/add-reps">
  Invite reps to your Launchpad workspace
</Card>


# Offline demos
Source: https://docs.navattic.com/launchpad/demos/offline

Present Navattic demos offline from your own device.

Learn about <img /> **Offline demos** in the primary Navattic documentation:

<CardGroup>
  <Card title="Offline demos" icon={<img src="https://mintcdn.com/navattic-app/F-ocMwTZ1ZRknPbL/images/icons/offline.svg?fit=max&auto=format&n=F-ocMwTZ1ZRknPbL&q=85&s=0a33f3be65cc6e3844dd2163a9c86400" className="m-0 -mt-px inline-flex h-5 w-5" />} href="/demos/offline">
    Use your demos offline at tradeshows and conferences.
  </Card>
</CardGroup>


# Personalized demos
Source: https://docs.navattic.com/launchpad/demos/personalized

Make demos personalized by adding user and account properties.

Learn about <Icon icon="user-pen" /> **Personalized demos** in the primary Navattic documentation:

<CardGroup>
  <Card title="Personalized demos" icon="user-pen" href="/demos/personalized">
    Make demos personalized by adding user and account properties
  </Card>
</CardGroup>


# Sandbox demos
Source: https://docs.navattic.com/launchpad/demos/sandbox

Learn how to quickly build a lightweight sandbox demo.

<Info>
  Sandbox demos are available on Growth and Enterprise plans.
</Info>

<Frame>
  <img alt="Sandbox builder" />
</Frame>

<img />

**Sandbox demos** are a way to quickly build lightweight sandbox demos of your application.

Unlike other guided product demos, sandbox demos uniquely allow you to click elements to navigate many different parts of your application.

<Info>
  Sandbox demos are intended for [presenting](/launchpad/share/present) by sales reps in Launchpad and are not for sharing publicly or embedding on your website.
</Info>

## Building a Sandbox demo

<Steps>
  <Step title="Generate a Sandbox Demo">
    From the <Icon icon="layout-grid" /> **Product demos** page click `+ Create demo`. For the `Start by` option, Select `Generating sandbox demo`.

    <Frame>
      <img alt="Generating Sandbox Demo Modal" />
    </Frame>
  </Step>

  <Step title="Take captures with click to capture">
    Take captures as you normally would with `click to capture` by clicking through your application. Your clicks will be used as anchors to generate the links for your sandbox demo.

    <Frame>
      <img alt="Capturing Stripe" />
    </Frame>
  </Step>

  <Step title="Click Finish">
    When you're done taking captures, click `Finish` to generate your sandbox demo and be taken to the **Sandbox builder**.
  </Step>

  <Step title="Add remaining links">
    You can add any remaining links to your demo by clicking on an element while in `Link` mode.

    We recommend organizing your sandbox into seperate flows based on core features of the product.

    For example, if your app's navigation looked like this, a seperate flow should be created for each sidebar item / feature name.

    <Frame>
      <img />
    </Frame>

    Would be organized into the following flows and screens:

    ```txt Example flows and screens expandable {1} theme={null}
      Domains
        - Domains overview
        - Buy a domain
        - Add an existing domain
        - ...etc
      Usage
        - Usage overview
        - Usage invoices
        - Usage spend management
        - ...etc
      Observability
        - Observability overview
        - Notebooks
        - Middleware
        - ...etc
      Storage
       - Create database
       - Open database
       - Remove database
       - ...etc
      Flag
       - Feature flag overview
       - Create flag
       - Update flag
       - ...etc
      AI Gateway
       - Gateway overview
       - Quick start
       - Model list
       - ...etc
    ```

    We recommend keeping each sandbox relatively lightweight to \~50 screens to keep maintenance easy and help reps stay on course.

    <Frame>
      <img alt="" />
    </Frame>
  </Step>
</Steps>

<Icon icon="party-popper" /> **Congratulations** -- you've finished building your first <Icon icon="chart-no-axes-column" /> **Sandbox demo** and it's ready to present!

Sandbox demos are a powerful tool for sales teams to deliver a high-level overview of the platform to prospects.

They're especially useful for showcasing **Ah-ha moments** in your product, making it easy to showcase value early in the sales cycle.

<MediaCard type="demo" title="Sandbox demos" />

<img />

**Sandbox demos** can be presented on live calls. Learn more about presenting demos:

<CardGroup>
  <Card title="Present demos" icon="presentation" href="/launchpad/share/present">
    Share and present Navattic demos during live calls
  </Card>

  <Card title="Sandbox Builder guide" icon="hammer" href="/demos/sandbox">
    Full guide to the Sandbox Builder, NavLinks, and settings
  </Card>
</CardGroup>


# Quick Start Guide
Source: https://docs.navattic.com/launchpad/get-started/quick-start-guide

Get up and running with Launchpad in minutes.

<img alt="Launchpad" />

<Icon icon="circle-arrow-out-up-right" /> **Launchpad** gives you streamlined access to interactive demos that help shorten sales cycles, improve the buying experience, and close more deals.

This quick guide will get you started sharing interactive demos with prospects in just a few minutes.

## Install the Chrome Extension

The easiest way to access and share demos is through the **Launchpad Chrome Extension**. It follows you anywhere on the web and integrates with the tools you already use.

<img alt="Launchpad Extension" />

<Panel>
  <Card icon={<img src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/icons/launchpad-logo.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=dad3c35c02234ff5de704cd11c7cba78" className="my-0 h-6 w-6" />} title="Install Launchpad extension" href="https://chromewebstore.google.com/detail/navattic-launchpad/niekkpiejdapnjipjciadeddkpnpbbik">
    Download from the Chrome Web Store.
  </Card>
</Panel>

Once installed, you'll see the Launchpad icon in your browser toolbar. Click it anytime to access your demos and share them with prospects.

<Info>
  The extension integrates with Salesforce, LinkedIn, Gmail, and other tools you use daily, making it easy to share demos right where you're working.
</Info>

## Sharing Demos

You can access and share demos from several places. Follow these steps to create a personalized demo link for your prospect.

### Access Your Demos

**From the Chrome Extension**

Click the Launchpad icon in your browser toolbar and click `+ Share demo` to get started.

<img alt="Launchpad extension share demo" />

**From the Launchpad App**

Visit the <Icon icon="library" /> **My demos** page in the Launchpad app and click `+ Share demo` to create a new demo link.

<img alt="My demos - share demo" />

**From Your Email Client**

If your workspace has email integrations set up, you can share demos directly from Gmail, Outlook, Outreach, or Salesloft, and more.

<CardGroup>
  <Card title="Learn more about integrations" icon="sliders-vertical" href="/launchpad/integrations/overview">
    See all available integrations
  </Card>
</CardGroup>

### How to Share

Follow these steps to create a personalized demo link:

<Steps>
  <Step title="Click &#x22;+ Share demo&#x22;">
    Open the Launchpad extension or go to the Launchpad app and click `+ Share demo`.
  </Step>

  <Step title="Select demo type">
    <img alt="Select demo type" />

    Choose between:

    * **1-1 demo**: Specify the company domain for personalized content and tracking (recommended for most deals)
    * **1-many (outbound)**: For sharing with multiple prospects in campaigns

    <Info>
      In most cases, we recommend sharing **1-1 demos** as this allows you to share more relevant content and better track engagement.
    </Info>
  </Step>

  <Step title="Select content">
    <img alt="Select content for demo" />

    Choose the flows or standard demo that best matches your prospect's needs. You can filter by interests if you know what the prospect cares about.

    A **flow** is a focused walkthrough of a specific product area like reporting or integrations.

    **Standard demo**: Share a single pre-built standard demo.

    **Custom flow**: Assemble multiple flows into a custom demo.

    <Tip>
      We recommend using **custom flow**, as these can be assembled ad hoc based on your prospect's specific use case or areas of interest.
    </Tip>
  </Step>

  <Step title="Customize settings (optional)">
    Customize your demo to match your needs:

    * **Personal intro video** - Include a personal welcome to your demo
    * **Interests form** - Allow visitors to select their areas of interests
    * **Recipient form gate** - Require visitors to fill out a form before accessing the demo to identify new stakeholders
    * **Expiration date** - Set when the demo link expires to control access (can be updated after sharing)
    * **Custom URL** - Customize the URL path for your demo
    * **Downloadable files** - Include case studies, pricing docs, or other resources

    <Tip>
      Adding a personal intro video can significantly increase engagement. Reference the prospect by name or mention specific talking points from your conversation.
    </Tip>
  </Step>

  <Step title="Add invites">
    Add your prospect's details and any relevant stakeholders. This ensures everyone receives a personalized invite and their engagement is tracked.

    If prospects forward the demo to other stakeholders, you'll be notified and can track their engagement. Learn more in the [Tracking Engagement](#tracking-engagement) section.
  </Step>

  <Step title="Copy and send">
    <img alt="Copy Launchpad demo link" />

    Copy the demo link and include it in your email to the prospect. You can also include a preview of the demo for extra engagement.
  </Step>
</Steps>

<CardGroup>
  <Card title="Learn more about sharing" icon="link" href="/launchpad/share/demos">
    Detailed guide on sharing demos
  </Card>

  <Card title="When to share demos" icon="circle-arrow-out-up-right" href="/launchpad/share/when-to-share">
    Best practices for timing
  </Card>
</CardGroup>

## Tracking Engagement

### Monitoring Your Activity

View your demo performance in the Launchpad app:

* **Buyer Circle**: See how many stakeholders have engaged with your demos
* **Sessions**: Track total viewing sessions and engagement time
* **Interest Areas**: Discover what features prospects care about most

<img alt="Demo activity dashboard showing buyer circle, sessions, and interest areas" />

### What to Do When You Receive an Alert

After you send the demo link, here's what happens and what to do:

**What happens:**

1. **Prospect receives the link** - They can view the demo at their convenience
2. **You get an email alert** - When they finish viewing, you'll receive a notification with engagement details. You can also receive <Icon icon="slack" /> [Slack notifications](/launchpad/integrations/slack) for real-time updates.
3. **Alert shows engagement** - The alert includes what they viewed, interest levels, and engagement metrics. You'll also get alerts when new stakeholders are discovered as the demo is shared internally across the organization, updating your buyer circle.

<img alt="Email Alerts" />

**What to do next:**

When you receive demo view notification, your prospect has expressed intent by engaging with your demo. This is an ideal time to follow up:

**Act fast** - Reach out within the next few minutes while the demo is fresh in their mind.

**Reference interests** - Check what the prospect viewed and their interest levels, then personalize your message based on their engagement.

**Suggest next steps** - Use their interests to guide the conversation and, if appropriate, suggest a meeting to discuss next steps.

<Info>
  Email alerts are sent at the end of the visitor session, so you'll know exactly when someone has finished viewing your demo.
</Info>

<img alt="Prospect interests view showing interest levels" />

## Presenting Demos

You can <Icon icon="presentation" /> **present demos** during live calls, on-site with prospects, or at events to provide a consistent, interactive, hands-on product experience.

### How to Present

When creating a share link, you can enable **Presenter mode** to use demos in live calls. Key features include:

* **Presenter Notes** - Add talking points to each step so you can stay on message without switching screens
* **Keyboard Navigation** - Use arrow keys (`← →`) to move forward and backward through demo steps
* **Click to Progress** - Click anywhere in Presenter mode to advance steps, making presentations more fluid
* **Keyboard Shortcuts** - Use `⌘P` to launch Presenter mode and `⌘N` to toggle presenter notes

<img alt="Present demos" />

<Tip>
  Presenter notes are visible only to you, giving you confidence and consistency without distracting the prospect.
</Tip>

<CardGroup>
  <Card title="Present demos" icon="presentation" href="/launchpad/share/present">
    Learn more about presenting demos
  </Card>
</CardGroup>

## Next Steps

Now that you're set up, here are some ways to get the most out of Launchpad:

* **Share demos before calls** - Send demos before scheduled meetings to help prospects qualify themselves and bring in stakeholders
* **Use interest demos** - Learn what features prospects care about most
* **Follow up quickly** - Act on email alerts promptly to keep momentum going
* **Share feedback** - Let your team know which demos work best and how prospects respond

<CardGroup>
  <Card title="Pre-call discovery" icon="package-check" href="/launchpad/use-cases/pre-call-discovery">
    Learn about sharing demos before calls
  </Card>

  <Card title="Post-call followup" icon="user-round-check" href="/launchpad/use-cases/post-call">
    Send followup demos after meetings
  </Card>

  <Card title="Outbound campaigns" icon="mail-check" href="/launchpad/use-cases/outbound">
    Use demos in outbound emails
  </Card>
</CardGroup>


# Launchpad
Source: https://docs.navattic.com/launchpad/index

Streamlined access to demos for sales teams.

<img alt="Launchpad" />

## Welcome to Launchpad

<Icon icon="circle-arrow-out-up-right" /> **Launchpad** is the way to scale interactive demos across
your sales department. With Launchpad, your sellers will have a streamlined way to access demos that
help to shorten sales cycles, improve the buying experience, and close more deals.

This documentation will walk you through everything you need to prepare your workspace — from building demos to tracking engagement — so your sales team can start sending demos throughout the sales cycle.

## Building demos

Your sales team will only be as effective as the demos they have access to. In this section, we'll cover how to build high-impact demos designed for outbound, discovery, and closing.

You'll also learn how to organize Launchpad so the best demos are front and center for your sales team.

<CardGroup>
  <Card title="Prepare your demos" icon="layout-grid" href="/launchpad/build/prepare">
    Select your gold-standard demos to showcase to your sales team.
  </Card>

  <Card title="Demos for sellers" icon="circle-arrow-out-up-right" href="/launchpad/demos/for-sellers">
    Learn how to create purpose-built demos for your sales team
  </Card>
</CardGroup>

Give your sales team the power to deliver demos that truly resonate with each prospect. From custom demos to sandbox environments and offline presentations, these purpose-built demos help you win deals by matching every buyer's needs.

<CardGroup>
  <Card title="Custom demos" icon="circle-fading-plus" href="/launchpad/demos/custom">
    Enable your sales team to assemble custom demos for each deal.
  </Card>

  <Card title="Interest demos" icon="chart-no-axes-column" href="/launchpad/demos/interest">
    Unlock a powerful insight - what features prospects are interested in seeing.
  </Card>
</CardGroup>

<CardGroup>
  <Card title="Sandbox demos" icon={<img src="https://mintcdn.com/navattic-app/F-ocMwTZ1ZRknPbL/images/icons/sandbox.svg?fit=max&auto=format&n=F-ocMwTZ1ZRknPbL&q=85&s=4160abd437d29288d56a6ec31ed9ab69" />} href="/launchpad/demos/sandbox">
    Make demos personalized by adding user and account properties.
  </Card>

  <Card title="Offline demos" icon={<img src="https://mintcdn.com/navattic-app/F-ocMwTZ1ZRknPbL/images/icons/offline.svg?fit=max&auto=format&n=F-ocMwTZ1ZRknPbL&q=85&s=0a33f3be65cc6e3844dd2163a9c86400" />} href="/launchpad/demos/offline">
    Use your demos offline at tradeshows and conferences.
  </Card>

  <Card title="Personalized demos" icon="user-pen" href="/launchpad/demos/personalized">
    Make demos personalized by adding user and account properties.
  </Card>
</CardGroup>

## Inviting reps

Once your workspace is set up, it's time to bring in your sales team. We'll walk you through how to invite reps, set permissions, and make sure they're ready to start sharing demos immediately.

A smooth onboarding process helps your sales team start sharing interactive demos throughout the sales cycle. Here are some tips for onboarding:

<CardGroup>
  <Card title="Adding the sales team" icon="user-round-plus" href="/launchpad/invite/add-reps">
    Customize your docs to your company's colors and brands
  </Card>

  <Card title="Launchpad extension" icon="circle-arrow-out-up-right" href="/launchpad/invite/launchpad-extension">
    Provide reps frictionless access to demos with the extension.
  </Card>

  <Card title="Rep contact cards" icon="id-card" href="/launchpad/invite/rep-contact-card">
    Check out our showcase of our favorite documentation
  </Card>
</CardGroup>

## Sharing demos

Best practices for when and how to share demos throughout the sales cycle.

<CardGroup>
  <Card title="Sharing demos" icon="link" href="/launchpad/share/demos">
    Sharing demos in Launchpad.
  </Card>

  <Card title="Customize share defaults" icon="settings" href="/launchpad/share/defaults">
    Configure who can access demos with sharing strategies.
  </Card>

  <Card title="When to share demos" icon="circle-arrow-out-up-right" href="/launchpad/share/when-to-share">
    Tips and best practices for when to share demos in the sales process.
  </Card>

  <Card title="Emailing prospects" icon="mail-check" href="/launchpad/share/crafting-emails">
    Tips and best practices for crafting engaging emails with demos.
  </Card>
</CardGroup>

## Tracking

Understanding how your team is using demos — and how prospects are engaging with them — is key to optimizing your sales motion. This section covers how to track demo activity, sync views to your CRM, and automate follow-up tasks to streamline your sales process.

Learn how to uncover what's working in the ways your team are using demos and how to improve it.

<CardGroup>
  <Card title="Email alerts" icon="mail" href="/launchpad/tracking/email-alerts">
    Get notified when prospects engage with demos.
  </Card>

  <Card title="CRM & Playbooks" icon="cloud" href="/launchpad/tracking/crm-playbooks">
    Automations to operationalize your sales process.
  </Card>

  <Card title="Monitoring activity" icon="chart-line" href="/launchpad/tracking/monitoring-activity">
    Targets to help you benchmark your performance.
  </Card>
</CardGroup>

## Use Cases

Learn about some of the top use cases for using interactive demos throughout the deal cycle, including outbounding, pre-call discovery, post-call follow-up, and more. Learn how leading sales teams use Launchpad across the funnel:

<CardGroup>
  <Card title="Outbound" icon="mail-check" href="/launchpad/use-cases/outbound">
    Send demos in outbound email campaigns to book more meetings.
  </Card>

  <Card title="Pre-call discovery" icon="package-check" href="/launchpad/use-cases/pre-call-discovery">
    Learn about what the prospect is interested in before the first call.
  </Card>

  <Card title="Post-call followup" icon="user-round-check" href="/launchpad/use-cases/post-call">
    Send relevant followup demos to prospects after the call.
  </Card>
</CardGroup>

## Integrations

Connect Launchpad to the tools your sales team already uses. Share demo links directly from your CRM, email client, or sales engagement platform without switching tabs.

<CardGroup>
  <Card title="Salesforce" icon="cloud" href="/launchpad/integrations/salesforce">
    Share demos directly from Salesforce records.
  </Card>

  <Card title="HubSpot" icon="cloud" href="/launchpad/integrations/hubspot">
    Share demos from HubSpot contacts and deals.
  </Card>

  <Card title="Outreach" icon="mail" href="/launchpad/integrations/outreach">
    Insert demo links into Outreach sequences.
  </Card>

  <Card title="Salesloft" icon="mail" href="/launchpad/integrations/salesloft">
    Add demo links to Salesloft emails and cadences.
  </Card>

  <Card title="Gmail" icon="mail" href="/launchpad/integrations/gmail">
    Share demos directly from Gmail.
  </Card>

  <Card title="Outlook" icon="mail" href="/launchpad/integrations/outlook">
    Share demos directly from Outlook.
  </Card>

  <Card title="Gong" icon="phone" href="/launchpad/integrations/gong">
    Surface demos during Gong calls.
  </Card>

  <Card title="Seismic" icon="file-text" href="/launchpad/integrations/seismic">
    Access Navattic demos from Seismic.
  </Card>
</CardGroup>

<Card title="View all integrations" icon="circle-arrow-right" href="/launchpad/integrations/overview">
  See the full list of Launchpad integrations and setup guides.
</Card>


# Front
Source: https://docs.navattic.com/launchpad/integrations/front

Connect your demos with Front to send demos directly within Front conversations.

<Frame>
  <img alt="Front integration dashboard" />
</Frame>

Connect your demos with **Front** to send demos directly within Front conversations. The Front integration uses conversation or sidebar plugins to allow you to create and insert interactive Navattic demos directly in Front.

# Key Features

**Message Composer Plugin**: Create custom demos while drafting emails in Front. The integration automatically inserts demo links and previews directly into your message body.

**Sidebar Plugin**: Access Navattic from the conversation sidebar when viewing individual conversations. Create personalized demos based on the context of your ongoing discussions.

**Automatic Recipient Detection**: The integration automatically identifies email recipients from your Front conversation or draft, streamlining the demo creation process.

**Demo Previews**: Each demo link includes an eye-catching image or GIF preview to increase click-through rates and engagement.

# How it works

The Front integration uses conversation or sidebar plugins to allow you to create and insert interactive Navattic demos directly into Front conversations without leaving Front, with image previews to catch recipients' attention.

<Info>
  The Front integration requires both admin-level setup and user-level authentication. Admins must configure the OAuth app in Front and enable the feature flag, while individual users connect their Front accounts to enable the conversation composer feature.
</Info>

## Setup overview

The Front integration requires setup on both the Front and Navattic sides. Follow these steps to get started:

<Steps>
  <Step title="Install from Front Marketplace">
    First, install the Navattic integration in your Front workspace:

    1. Navigate to the [Front integration marketplace](https://front.com/integrations/navattic)
    2. Click **Install** to add Navattic to your Front workspace
    3. Follow Front's authentication prompts to authorize the integration
    4. Once installed, the Navattic plugin will be available in both your message composer and conversation sidebar

    <Note>
      You need admin permissions in Front to install integrations for your workspace.
    </Note>
  </Step>

  <Step title="Connect Navattic Account">
    After installing in Front, connect your Navattic account:

    1. Log in to your Navattic account as an administrator
    2. Go to Navattic and navigate to **Settings** → **Integrations** → **Front**
    3. Click **Connect** to link your Navattic account with Front
    4. This will open a Front authorization page requesting permissions:
       * **App Name**: Navattic
       * **Required Scopes**:
         * `conversations:write` - For inserting demos into Front conversations
         * `channels:read` - For accessing Front channels and inboxes
    5. Click **Allow** in Front to grant permissions
    6. You'll be redirected back to Navattic
    7. The integration status should show as "Connected"
  </Step>

  <Step title="Enable for Your Team">
    Once connected, individual users can access the integration:

    1. Each user needs to ensure they're logged into both Front and Navattic
    2. The Navattic icon will appear in the Front composer toolbar and sidebar
    3. Users can start creating and inserting demos directly from Front conversations

    <Note>
      The integration automatically detects recipients from your Front conversation or draft, streamlining the demo creation process.
    </Note>
  </Step>
</Steps>

## Conversation and Sidebar Plugins

<Frame>
  <img alt="Front conversation composer integration" />
</Frame>

The Front integration provides conversation or sidebar plugins that allow users to access Navattic directly within Front to create and insert interactive demos into their conversations. The demo is inserted as an interactive HTML element with an image or GIF preview.

<Note>
  The conversation and sidebar plugins require the Front integration to be connected at the user level. Ensure you've completed the setup steps above before using this feature.
</Note>

## Using the Message Composer Plugin

The message composer plugin works when you're drafting new emails or replies in Front:

1. While composing an email, locate the Navattic icon in your composer toolbar
2. Click the icon to launch the demo creation interface
3. Select a demo from your library or create a new custom demo
4. Configure any personalization options for your recipient
5. Click **Insert** to add the demo link and preview to your email

The demo content will automatically appear in your email body at your cursor position. You can continue editing your message as usual before sending.

<Note>
  The integration automatically identifies email recipients from your Front conversation or draft, streamlining the demo creation process.
</Note>

## Using the Sidebar Plugin

The sidebar plugin provides access to Navattic while viewing conversations:

1. Open any conversation in Front
2. Look for the Navattic icon in the right sidebar
3. Click the icon to open the integration
4. The integration will automatically detect recipients from the active conversation
5. Create or select a demo to share
6. Insert the demo into your draft message

<Note>
  The sidebar plugin requires an active draft in the conversation. If no draft exists, you'll see a message prompting you to create one first.
</Note>

## Common Use Cases

The Front integration uses **conversation or sidebar plugins** to add demos directly into your Front workflows:

### Outbound Campaigns

Insert demos into initial outreach emails to showcase your product's value immediately. The demo preview catches attention and encourages recipients to engage with the interactive experience.

### Pre-Call Discovery

Send a tailored demo before scheduled calls to help prospects explore relevant features at their own pace. This makes your actual meeting more productive and focused.

### Post-Call Follow-Up

After discovery calls or product demos, send a custom demo that reinforces the specific features and use cases you discussed. This keeps your solution top-of-mind and provides a resource prospects can share internally.

### Response Tracking

Enable email notifications in your Navattic workspace to receive alerts when recipients view your demos. Use this engagement signal to inform your follow-up timing and messaging.

## FAQs

<AccordionGroup>
  <Accordion title="I can't see the Navattic option in Front">
    If you're experiencing issues with the Front integration:

    1. **Verify your Front account is connected**: Navigate to **Settings** → **Integrations** → **Front** and confirm your account shows as "Connected"
    2. **Check user-level connection**: Ensure you've connected your individual Front account, not just the admin connection
    3. **Refresh Front**: Try refreshing your Front browser tab or restarting the Front app
  </Accordion>

  <Accordion title="How do I insert a demo into a Front conversation?">
    Once the integration is connected, you can access Navattic through the conversation or sidebar plugins in Front. Look for the Navattic plugin in the conversation composer or sidebar to browse and insert your interactive demos.
  </Accordion>

  <Accordion title="Plugin not appearing">
    Ensure the integration is installed for your Front workspace and that you're using a supported browser (Chrome, Firefox, Safari, or Edge).
  </Accordion>

  <Accordion title="Recipients not detected">
    The integration pulls recipient information from the email draft. Make sure your Front conversation email has recipient information available.
  </Accordion>

  <Accordion title="Demo won't insert">
    Verify that you have an active draft open in Front. The integration requires a draft to insert content.
  </Accordion>

  <Accordion title="Authentication issues">
    If you're prompted to authenticate repeatedly, clear your browser cache and cookies for Front, then reconnect your Navattic account through the integration settings.
  </Accordion>
</AccordionGroup>

## Related resources

<CardGroup>
  <Card title="Sharing demos" icon="share" href="/launchpad/share/demos">
    Learn how to share demos with prospects
  </Card>

  <Card title="Crafting emails" icon="mail" href="/launchpad/share/crafting-emails">
    Best practices for including demos in emails
  </Card>
</CardGroup>


# Gmail
Source: https://docs.navattic.com/launchpad/integrations/gmail

Create and share demos from within Gmail.

<Frame>
  <img alt="Gmail Inbox Navattic Integration" />
</Frame>

Sales reps can create and share demos from within <img alt="Gmail Logo" /> **Gmail**.

After installing the [Launchpad extension](/launchpad/invite/launchpad-extension), reps will see the Launchpad logo in their Gmail compose window.

## How to send a demo in Gmail

<Steps>
  <Step title="Click the Launchpad logo in the compose window">
    <img alt="" />

    In the Gmail compose window, click on the Navattic Launchpad logo next to the `Send` button.
  </Step>

  <Step title="Create a custom demo">
    Follow steps to create a custom demo.
  </Step>

  <Step title="Send the email">
    After creating the demo, the demo link and preview will be injected into the email body.
  </Step>
</Steps>

## Crafting emails with demos best practices

Read best practices for crafting emails based on use cases:

<CardGroup>
  <Card title="Outbound" icon="mail-check" href="/launchpad/use-cases/outbound" />

  <Card title="Pre-call discovery" icon="package-check" href="/launchpad/use-cases/pre-call-discovery" />

  <Card title="Post-call followup" icon="user-round-check" href="/launchpad/use-cases/post-call" />
</CardGroup>


# Gong
Source: https://docs.navattic.com/launchpad/integrations/gong

Connect your demos with Gong to track demo engagement and send demos directly within Gong Engage.

<Frame>
  <img alt="Gong integration dashboard" />
</Frame>

Connect your demos with **Gong** to track demo engagement and send demos directly within Gong Engage. The Gong integration enables bidirectional data flow between Navattic and Gong, allowing you to automatically send demo engagement data to Gong as Digital Interactions and create interactive demos directly in Gong's email composer.

# How it works

The Gong integration provides two main capabilities:

1. **Track Demo Engagement in Gong**: Automatically send demo engagement data from Navattic sessions to Gong as "Digital Interactions". This includes visitor information, session metrics, interest areas, and engagement data.
2. **Use Demos in Gong Engage**: Create and insert interactive Navattic demos directly into the Gong Engage email composer without leaving Gong, with image previews to catch recipients' attention.

<Info>
  The Gong integration requires both admin-level setup and user-level authentication. Admins must configure the OAuth app in Gong and enable the feature flag, while individual users connect their Gong accounts to enable playbooks and email composer features.
</Info>

## Setup overview

<Steps>
  <Step title="Connect to Gong App">
    An admin must be authenticated in Navattic as well as in Gong to enable the integration:

    1. Log in to your Gong account as an administrator
    2. Log in to you Navattic account as an administrator
    3. Go to Navattic and click Manage under the Gong Card in Settings -> Integrations
    4. Click the Connect button
    5. This will open a Gong page requesting permissions for the following entity:
       * **App Name**: Navattic
       * **Required Scopes**:
         * `api:integration-settings:write` - For allowing Navattic to manage it's own integration settings
         * `api:digital-interactions:write` - For creating digital interactions for contacts in Gong
    6. Click Allow
    7. You'll be redirected back to Navattic
    8. The integration status should show as "Connected"
  </Step>

  <Step title="Create a Playbook">
    Once your Gong integration is fully set up, visit [Playbooks](/integrations/playbooks) in your Workspace to start pushing data into Gong. You can use a Template or create your own Playbook.

    There are two separate Gong Playbook Actions that you can set up: Gong Visitor, Gong Account. See Common Use cases below for more details.

    <Note>
      A Playbook consists of [Audiences](/integrations/playbooks) and Actions. You can use one of the default Audiences or you can create your own. If you create your own, remember to add new demos to the Audience if you are choosing to filter by specific demos.
    </Note>
  </Step>
</Steps>

## Digital Interactions

When visitors complete Navattic demo sessions, the integration automatically creates Digital Interactions in Gong via their API. These interactions include:

* **Person details**: Email, name, location, company
* **Content information**: Demo title, share link URL
* **Custom fields**: Session length, total time, interest areas, interest levels, location, company info
* **Engagement metadata**: Event timestamp, session ID

<Info>
  Digital Interactions are sent when a playbook action is triggered. For visitor playbooks, the visitor must have an email. For account playbooks, the account must have a website domain.
</Info>

## Email Composer Integration

<Frame>
  <img alt="Gong integration dashboard" />
</Frame>

Users can access Navattic directly within Gong's Engage email composer interface to create and insert interactive demos into their emails. The demo is inserted as an interactive HTML element with an image or GIF preview.

<Note>
  The email composer integration requires the Gong integration to be connected at the user level. Ensure you've completed Step 4 above before using this feature.
</Note>

## Common Use Cases

### Track Identified Visitors in Gong

Automatically send visitor engagement data to Gong when prospects identify themselves in your demo.

**Setup**:

1. Ensure your Gong integration is connected
2. Go to **Playbooks** section in the Gong integration settings
3. A default playbook "Track identified visitors in Gong" is automatically created for visitor-type events
4. The playbook triggers on `Identified` visitor events
5. When a visitor provides their email/contact info, a Digital Interaction is automatically created in Gong

**Customization**: You can edit the playbook to adjust:

* Audience filters (which visitors trigger the action)

### Track Engaged Accounts in Gong

Send account-level engagement data to Gong for high-value accounts showing strong engagement signals.

**Setup**:

1. Ensure your Gong integration is connected
2. A default playbook "Track engaged accounts in Gong" is automatically created for account-type events
3. The playbook triggers on accounts with:
   * Engagement: `true`
   * Confidence Score: `High` or `Very High`
4. When triggered, sends comprehensive account data to Gong

### Insert Demos in Gong Emails

Create and insert interactive Navattic demos directly into emails you're composing in Gong.

## FAQs

<AccordionGroup>
  <Accordion title="I'm not receiving data in Gong">
    If you're experiencing issues with the Gong integration:

    1. **Verify your Gong account is connected**: Navigate to **Settings** → **Integrations** → **Gong** and confirm your account shows as "Connected"
    2. **Check playbook configuration**: Ensure your playbooks are active and have the correct audience filters
    3. **Check data requirements**:
       * Visitor playbooks require visitor email
       * Account playbooks require account website domain
  </Accordion>

  <Accordion title="What data is sent to Gong?">
    The integration sends Digital Interaction events including person details (email, name, location), company information (name, domain) when available, content details (demo title, share link URL), and custom fields like session length, total time, interest areas, interest levels, location, and company information.
  </Accordion>

  <Accordion title="Do I need both visitor and account playbooks?">
    No, you can use either or both:

    * **Visitor playbook**: Tracks individual prospects regardless of company association
    * **Account playbook**: Tracks at the company level with company data included
  </Accordion>
</AccordionGroup>

## Related resources

<CardGroup>
  <Card title="Email alerts" icon="mail" href="/launchpad/tracking/email-alerts">
    Learn about email notifications for demo engagement
  </Card>

  <Card title="Monitoring activity" icon="activity" href="/launchpad/tracking/monitoring-activity">
    Track and monitor demo engagement activity
  </Card>

  <Card title="Playbooks" icon="book-open" href="/integrations/playbooks">
    Learn how to set up and configure playbooks
  </Card>
</CardGroup>


# Highspot
Source: https://docs.navattic.com/launchpad/integrations/highspot

Create and share demos from within Highspot Digital Sales Rooms.

<Frame>
  <img alt="Highspot integration dashboard" />
</Frame>

Sales reps can create and share demos from within <img alt="Highspot Logo" /> **Highspot** Digital Sales Rooms.

The Highspot integration enables you to create Navattic demo share links directly from within your Highspot Digital Sales Rooms, providing a seamless workflow for adding interactive demos to your sales content.

<Info>
  The Highspot integration requires admin-level setup in Highspot. Once configured, users can access the Navattic integration button within Highspot Digital Sales Rooms.
</Info>

## Admin setup

Make sure you enable Navattic integration first by navigating to:

`Company Settings` → `Cloud Services` → `Navattic`

Then a new Navattic block will be visible in Digital Room

<Info>
  Only workspace admins can perform the initial Highspot integration setup. Once configured, all workspace members can access the integration within their Digital Sales Rooms.
</Info>

## How to create a demo in Highspot

<Steps>
  <Step title="Open a Highspot Digital Sales Room">
    Open a Highspot Digital Sales Room where you want to add the demo.
  </Step>

  <Step title="Choose Integrations → Navattic">
    Choose Integrations → Navattic from the Digital Room Builder.

    <Frame>
      <img alt="Choose Integrations Navattic" />
    </Frame>
  </Step>

  <Step title="Launch the Navattic iframe">
    This will launch the Navattic authenication window. Select Link Account to authenticate.

    <Frame>
      <img alt="Navattic iframe launched" />
    </Frame>
  </Step>

  <Step title="Create a demo link within Navattic">
    Create a demo share link within Navattic.

    <Frame>
      <img alt="Assign demo to Spot" />
    </Frame>
  </Step>

  <Step title="Assign the demo to a Spot">
    Once a demo has been created, assign it to a Spot using the Spot dropdown. Select Add once completed.

    <Frame>
      <img alt="Assign demo to Spot" />
    </Frame>
  </Step>

  <Step title="Demo added to Digital Room">
    Once created, the demo will be added to your Digital Sales Room.
  </Step>
</Steps>

## Common Use Cases

* **Sales Enablement**: Sales reps add interactive product demos to their Highspot Digital Sales Rooms, making demos easily accessible to prospects browsing the room.

* **Personalized Sales Rooms**: Create personalized demo experiences within Highspot rooms for different prospects or segments, enhancing engagement and relevance.

* **Content Organization**: Organize interactive demos alongside other sales materials in Highspot Digital Sales Rooms for comprehensive sales enablement.

* **Prospect Engagement**: Prospects can interact with demos directly within the Highspot Digital Sales Room, providing a seamless experience without leaving the room.

## FAQs

<AccordionGroup>
  <Accordion title="I'm not able to see the Navattic button in Highspot">
    Check the following:

    1. Highspot admin has added Navattic integration
    2. You have permissions to use integrations in Highspot
    3. The integration URL is correctly configured: `https://app.navattic.com/integration/highspot/email-editor`
    4. You're viewing a Digital Sales Room (not just email composer)
    5. Try refreshing the page
  </Accordion>

  <Accordion title="Failed to connect or authenticate">
    This can occur due to several reasons:

    1. **Authentication issues**: Verify you can log into Navattic normally
    2. **Session issues**: Try clearing browser cookies and retrying
    3. **Network issues**: Check your internet connection
    4. **Popup blockers**: Ensure popup blockers aren't interfering
    5. **CSP errors**: Check browser console for Content Security Policy errors - the integration requires proper CSP configuration

    If you see "app.navattic.com refused to connect" errors, this indicates a Content Security Policy issue that needs to be resolved by your admin.
  </Accordion>

  <Accordion title="Demo doesn't appear in my room">
    Troubleshooting steps:

    1. Check browser console for JavaScript errors
    2. Verify the demo was created successfully
    3. Try refreshing the Highspot Digital Sales Room
    4. Ensure you completed all steps in the demo creation process
    5. Check that the demo link was successfully generated
  </Accordion>

  <Accordion title="Content Security Policy (CSP) errors">
    If you see CSP errors in the browser console like "Refused to frame '[https://app.navattic.com/](https://app.navattic.com/)'", this means:

    1. The integration requires proper CSP configuration in Highspot
    2. The CSP must allow framing from `https://*.highspot.com`
    3. Contact your Highspot admin to configure the CSP headers correctly
    4. The CSP configuration should include: `frame-ancestors 'self' https://*.highspot.com`
  </Accordion>

  <Accordion title="Can I create multiple demos in one room?">
    Yes, you can create multiple demos and add them to your Highspot Digital Sales Room. Each demo will be independent and can be placed in different sections of your room as needed.
  </Accordion>

  <Accordion title="What happens to my demo data?">
    Demo data remains in your Navattic account. The integration creates share links that are added to your Highspot Digital Sales Room. Engagement data is tracked in Navattic, and you can monitor demo performance through Navattic's analytics.
  </Accordion>
</AccordionGroup>

## Crafting emails with demos best practices

Read best practices for crafting emails based on use cases:

<CardGroup>
  <Card title="Outbound" icon="mail-check" href="/launchpad/use-cases/outbound" />

  <Card title="Pre-call discovery" icon="package-check" href="/launchpad/use-cases/pre-call-discovery" />

  <Card title="Post-call followup" icon="user-round-check" href="/launchpad/use-cases/post-call" />
</CardGroup>

## Related resources

<CardGroup>
  <Card title="Share demos" icon="share-2" href="/launchpad/share/demos">
    Learn how to create and share demos in Launchpad
  </Card>

  <Card title="Monitoring activity" icon="activity" href="/launchpad/tracking/monitoring-activity">
    Track and monitor demo engagement activity
  </Card>

  <Card title="Email alerts" icon="mail" href="/launchpad/tracking/email-alerts">
    Learn about email notifications for demo engagement
  </Card>
</CardGroup>


# HubSpot
Source: https://docs.navattic.com/launchpad/integrations/hubspot

Connect your demos with HubSpot to create records from Visitors.

<Frame>
  <img alt="Hubspot integration" />
</Frame>

<Info>
  Check that you are [Identifying visitors](/tracking/identify/visitors) before setting up the
  Hubspot integration.
</Info>

The HubSpot integration is used to:

1. Create or update HubSpot Contacts with Navattic Visitor and Engagement data
2. Create and update HubSpot Companies with Navattic Account and Engagement data.

Once the data is available in HubSpot, HubSpot dashboards and reports can be created to answer questions like:

* Which demos generate the most leads?
* What % of leads originating from Navattic later convert to MQLs, and onwards?
* Which steps in my demo are most visitors dropping off at?

### Setting up the HubSpot Integration

Follow these steps to set up the Hubspot integration with Navattic:

<Steps>
  <Step title="Connect with HubSpot">
    Navigate to `Integrations` in Settings and select Hubspot. Click on Connect and follow the instructions to authorize your Hubspot account.
  </Step>

  <Step title="Set Up Field Mapping">
    [Field mappings](/navattic-field-mappings) allow you to control which pieces of Navattic's data go where. To set up field mapping, go to the "**Configuration**" tab of your HubSpot integration. Open the "Field Mapping" dropdown, and start mapping fields. If you have [Account-Based Engagement](/identify#RPJfe), you will also see the option to set up Company field mapping. Fields on the left are Navattic data, and fields on the right are destinations within your HubSpot instance. Navattic uses HubSpot Contact Properties as data destinations.

    <Note>If you are setting up field mappings for Contacts, Email is a required field.</Note>
  </Step>

  <Step title="Create a Playbook">
    Once your HubSpot integration is fully set up, visit [Playbooks](/integrations/playbooks) in your Workspace to start pushing data into HubSpot. You can use a Template or create your own Playbook.

    There are three separate HubSpot Actions that you can set up: Sync contact, Timeline events, Sync Account.

    <Note>
      A Playbook consists of [Audiences](/integrations/playbooks) and Actions. You can use one of the default
      Audiences or you can create your own. If you create your own, remember to add new demos to the
      Audience if you are choosing to filter by specific demos.
    </Note>
  </Step>

  <Step title="Run a Test">
    Once the Playbook is set up, run a quick test to ensure this test data populates in HubSpot. To run a test, click the three dots next to the **Save** button > **Test run.**
  </Step>

  <Step title="Create HubSpot Dashboards to see ROI">
    [Try a demo](https://navattic-website.navattic.com/k8puwxfx)
    to see how Navattic-created Contacts appear in HubSpot.

    * Once connected, Navattic will send **email** (required) and all of the selected mapped fields to your HubSpot CRM.
    * These Contacts will be identifiable by the property **Original source 2** is Navattic.
    * The Original Source will reflect "Offline sources", per [HubSpot's default conditions](https://knowledge.hubspot.com/contacts/understand-source-properties#:~:text=A%20contact%E2%80%99s%20Original%20source%20or%20Latest%20source%20value%20will%20be%20one%20of%20the%20following%3A). Now you can use HubSpot dashboards to visualize your demo engagment data! We recommend creating [this HubSpot dashboard](https://navattic-website.navattic.com/k8puwxfx) to see demo views, step views, conversions, and the number of Contacts created by each demo.

    <MediaCard type="demo" title="Hubspot Dashboard" />

    <br />

    <MediaCard type="video" title="HubSpot Dashboard" />
  </Step>
</Steps>

<Tip>
  Tip: You can also create [HubSpot
  sequences](https://knowledge.hubspot.com/sequences/create-and-edit-sequences) based on visitor
  engagement with demos. The [HubSpot Knowledge Base](https://knowledge.hubspot.com/) contains more
  information on creating dashboards, reports, and sequences.
</Tip>


# Outlook
Source: https://docs.navattic.com/launchpad/integrations/outlook

Create and share demos from within Outlook.

<Frame>
  <img alt="Salesloft Inbox Navattic Integration" />
</Frame>

Sales reps can create and share demos from within <img alt="Outlook Logo" /> **Outlook**.

To access the Outlook integration, please install the Navattic Outlook Add-in from the [AppSource store](https://appsource.microsoft.com/en-us/product/office/WA200009256).

<Panel>
  <Card href="https://appsource.microsoft.com/en-us/product/office/WA200009256" title="Install Navattic for Outlook" icon={<img src="https://mintcdn.com/navattic-app/c6crWyX_VwcL814J/images/outlook.png?fit=max&auto=format&n=c6crWyX_VwcL814J&q=85&s=25031c3e7d3c570ef0b056f50ac6909d" alt="Outlook Logo" className="h-6 w-6 inline-block m-0 -mt-px" /> }>
    Download from the Outlook AppSource store.
  </Card>
</Panel>

After installing the Add-in, reps will see the Add-in in their Outlook compose window.

<MediaCard type="demo" title="Outlook Setup" />

## How to send a demo in Outlook

<Steps>
  <Step title="Click the Apps icon in the compose window">
    <img alt="" />

    In the add-in window, click on the Navattic logo to launch the add-in.
  </Step>

  <Step title="Create a custom demo">
    Follow steps to create a custom demo.
  </Step>

  <Step title="Send the email">
    After creating the demo, the demo link and preview will be injected into the email body.
  </Step>
</Steps>

## Crafting emails with demos best practices

Read best practices for crafting emails based on use cases:

<CardGroup>
  <Card title="Outbound" icon="mail-check" href="/launchpad/use-cases/outbound" />

  <Card title="Pre-call discovery" icon="package-check" href="/launchpad/use-cases/pre-call-discovery" />

  <Card title="Post-call followup" icon="user-round-check" href="/launchpad/use-cases/post-call" />
</CardGroup>


# Outreach
Source: https://docs.navattic.com/launchpad/integrations/outreach

Create and share demos from within Outreach.

<Frame>
  <img alt="Outreach Inbox Navattic Integration" />
</Frame>

Sales reps can create and share demos from within <img alt="Outreach Logo" /> **Outreach**.

To access the Outreach integration, please install the Navattic integration from the [Outreach marketplace](https://marketplace.outreach.io/apps/navattic).

<Panel>
  <Card href="https://marketplace.outreach.io/apps/navattic" title="Install Navattic for Outreach" icon={<img src="https://mintcdn.com/navattic-app/c6crWyX_VwcL814J/images/outreach.png?fit=max&auto=format&n=c6crWyX_VwcL814J&q=85&s=5e5342a54f5fb9b93f3396108fb03dd7" alt="Outreach Logo" className="h-6 w-6 inline-block m-0 -mt-px" /> }>
    Download from the Outreach marketplace.
  </Card>
</Panel>

<Steps>
  <Step title="Compose an email">
    <img alt="" />

    In the email compose window, click on the Navattic logo to launch the integration.
  </Step>

  <Step title="Sign in to Navattic">
    The first time you open the integration, you'll be prompted to sign in to your Navattic account. After signing in, the plugin saves your session so you won't need to sign in again on future uses.
  </Step>

  <Step title="Create a custom demo">
    Follow steps to create a custom demo.
  </Step>

  <Step title="Send the email">
    After creating the demo, the demo link and preview will be injected into the email body.
  </Step>
</Steps>

## Crafting emails with demos best practices

Read best practices for crafting emails based on use cases:

<CardGroup>
  <Card title="Outbound" icon="mail-check" href="/launchpad/use-cases/outbound" />

  <Card title="Pre-call discovery" icon="package-check" href="/launchpad/use-cases/pre-call-discovery" />

  <Card title="Post-call followup" icon="user-round-check" href="/launchpad/use-cases/post-call" />
</CardGroup>


# Launchpad Integrations
Source: https://docs.navattic.com/launchpad/integrations/overview

Connect Launchpad with your CRM and email tools.

Launchpad supports the following <Icon icon="sliders-vertical" /> **Integrations** that help you automatically sync engagement data across your go-to-market stack.

Whether you're alerting sales in Slack or enriching CRM records, these integrations ensure your team has the right context to operationalize on demo engagement.

<CardGroup>
  <Card title="Slack" href="/launchpad/integrations/slack" icon={<img src="https://mintcdn.com/navattic-app/yNRyqX56abP0KBOE/images/slack.svg?fit=max&auto=format&n=yNRyqX56abP0KBOE&q=85&s=6fffe8d2804b4b0141bd3a2ac00faf90" className="my-0 h-6 w-6" />}>
    Get real-time Slack notifications when prospects engage with shared demos.
  </Card>

  <Card title="Salesforce" href="/launchpad/integrations/salesforce" icon={<img src="https://mintcdn.com/navattic-app/rptQv_Iq6w06CEaq/images/salesforce.svg?fit=max&auto=format&n=rptQv_Iq6w06CEaq&q=85&s=a52c32327bc98ac8fd07bce1941cccb1" className="my-0 h-6 w-6" />}>
    Sync engagement data to Salesforce Leads, Contact, and Accounts.
  </Card>

  <Card title="Hubspot" href="/launchpad/integrations/hubspot" icon={<img src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/hubspot.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=1431f8e82fd1d18212e66b684c438df0" className="my-0 h-6 w-6" />}>
    Sync engagement data with Hubspot Contacts, and Companies.
  </Card>

  <Card title="Seismic" href="/launchpad/integrations/seismic" icon={<img src="https://mintcdn.com/navattic-app/qnbu65r0xHm8-Lfh/images/seismic.png?fit=max&auto=format&n=qnbu65r0xHm8-Lfh&q=85&s=becb9127e1fd277856cdd887ce6d2053" className="my-0 h-6 w-6" />}>
    Sync demo links to Seismic records.
  </Card>

  <Card title="Gong" href="/launchpad/integrations/gong" icon={<img src="https://mintcdn.com/navattic-app/ASIrATcP1QlsXM3o/images/gong.svg?fit=max&auto=format&n=ASIrATcP1QlsXM3o&q=85&s=a40113e30365478a1ce101ba87f06b1b" className="my-0 h-6 w-6" />}>
    Sync engagement data to visitors and accounts within Gong.
  </Card>

  <Card title="Highspot" href="/launchpad/integrations/highspot" icon={<img src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/highspot.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=7836c897b621092ddaf766e9ebab7b02" className="my-0 h-6 w-6" />}>
    Create and share demos from within Highspot Digital Sales Rooms.
  </Card>
</CardGroup>

## Email integrations

Create and send demos right inside of your preferred email client.

Meet your sales reps inside the tools they already use. Quickly create and send demos seamlessly while you're drafting emails to prospects.

<CardGroup>
  <Card title="Gmail" href="/launchpad/integrations/gmail" icon={<img src="https://mintcdn.com/navattic-app/FQwkkhyafVZj-1wx/images/gmail.png?fit=max&auto=format&n=FQwkkhyafVZj-1wx&q=85&s=724fbc3b1c6507cb8c24c84241287819" className="my-0 h-6 w-6" />} />

  <Card title="Outreach" href="/launchpad/integrations/outreach" icon={<img src="https://mintcdn.com/navattic-app/c6crWyX_VwcL814J/images/outreach.png?fit=max&auto=format&n=c6crWyX_VwcL814J&q=85&s=5e5342a54f5fb9b93f3396108fb03dd7"  className="my-0 h-6 w-6" />} />

  <Card title="Salesloft" href="/launchpad/integrations/salesloft" icon={<img src="https://mintcdn.com/navattic-app/mHqR2iPe3ScBaXMu/images/salesloft.png?fit=max&auto=format&n=mHqR2iPe3ScBaXMu&q=85&s=17ffabd0c24eff5963531d2078b875bb" className="my-0 h-6 w-6" />} />

  <Card title="Outlook" href="/launchpad/integrations/outlook" icon={<img src="https://mintcdn.com/navattic-app/c6crWyX_VwcL814J/images/outlook.png?fit=max&auto=format&n=c6crWyX_VwcL814J&q=85&s=25031c3e7d3c570ef0b056f50ac6909d" className="my-0 h-6 w-6" />} />

  <Card title="Gong" href="/launchpad/integrations/gong" icon={<img src="https://mintcdn.com/navattic-app/ASIrATcP1QlsXM3o/images/gong.svg?fit=max&auto=format&n=ASIrATcP1QlsXM3o&q=85&s=a40113e30365478a1ce101ba87f06b1b" className="my-0 h-6 w-6" />} />
</CardGroup>


# Salesforce
Source: https://docs.navattic.com/launchpad/integrations/salesforce

Automations to operationalize your sales process.

## Overview

The Navattic Salesforce integration uses a direct connection through Salesforce's standard OAuth flow, connecting directly to your Salesforce instance using standard objects and custom fields.

## Salesforce Configuration

### Custom Object: Navattic Session

When connecting Salesforce to Navattic, you have the option to create a custom object called **Navattic Session** to track individual demo viewing sessions. This object includes:

<Accordion title="Session Data Fields">
  * Session ID (text, primary field)
  * Started At (datetime)
  * Full Name (text, 255 characters)
  * Email (text, 255 characters)
  * Duration (minutes) (number with 3 decimal places)
  * Steps Viewed (whole number)
  * Demos (text, 255 characters)
  * Flows (text, 255 characters)
  * Very Interested Areas (text, 255 characters)
  * Somewhat Interested Areas (text, 255 characters)
  * Not Interested Areas (text, 255 characters)
  * Opportunity (lookup to Opportunity)
  * Account (lookup to Account)
  * Contact (lookup to Contact)
  * Lead (lookup to Lead)
</Accordion>

### Integration User Requirements

The Salesforce user account that connects to Navattic needs specific permissions to sync demo engagement data.

<Accordion title="Required Object Permissions">
  The connected user must have **Read** and **Edit** access to:

  * Lead object
  * Contact object
  * Account object
  * Opportunity object
  * Navattic Session object (custom)
</Accordion>

<Accordion title="Required Field-Level Security">
  Field-Level Security (FLS) is separate from the object-level Edit permission in the permission set — you can grant object-level Edit while keeping FLS scoped to only the fields Navattic touches.

  **Always required (Read and Edit):**

  * Email (on Lead and Contact)
  * LastName (on Lead and Contact)
  * All Navattic custom fields

  **Required only in certain configurations (Read and Edit):**

  * Name (on Account) — only if account creation is enabled, or if the default Company Name field mapping is kept
  * Website (on Account) — only if account creation is enabled, or if the default Company Domain field mapping is kept
  * FirstName (on Lead and Contact) — only if the default FirstName field mapping is kept
  * Company (on Lead) — only if lead creation is enabled

  You can remove conditional mappings in the field mapper under your Salesforce integration settings.

  **Read only:**

  * Name (on Opportunity) — the integration reads but never writes to Opportunity records
</Accordion>

<Accordion title="Required System Permissions">
  * **API Enabled** - This permission must be enabled on the user's profile or permission set
  * **View All Data** (recommended) - Makes setup easier, though not strictly required
  * **Modify All Data** (recommended) - Makes setup easier, though not strictly required
</Accordion>

<Accordion title="Permission Set Creation">
  During the initial connection, Navattic automatically creates a Permission Set that grants access to:

  * The Navattic Session custom object
  * All fields on the Navattic Session object
  * Full CRUD permissions on Lead, Contact, Account, and Opportunity objects

  This permission set is automatically assigned to the connected integration user.
</Accordion>

<Accordion title="User Account Recommendations">
  **Option 1: Dedicated Integration User (Recommended)**

  Create a dedicated Salesforce user specifically for the Navattic integration:

  * Clear audit trail of all Navattic activities
  * Easy to troubleshoot permission issues
  * Can be disabled without affecting other integrations
  * Doesn't consume a regular user license (use Integration User license if available)

  Setup steps:

  1. Create a new user with Integration User or regular license
  2. Assign a profile with API Enabled permission
  3. Grant the required object and field permissions
  4. Use this user to connect Navattic

  **Option 2: System Administrator User**

  Use your Salesforce admin account to connect:

  * Quick setup with no permission configuration needed
  * Guaranteed to have all required permissions

  Disadvantages:

  * Less clear audit trail
  * All Navattic actions appear as admin actions
  * If admin leaves organization, integration may break
</Accordion>

## Setup Steps

<Steps>
  <Step title="Connect to Salesforce">
    In Navattic, navigate to Settings > Integrations > Salesforce and click **Connect**.

    <img alt="Salesforce Integration" />

    You'll be redirected to Salesforce to authorize the connection. Choose:

    * **Production** for your live Salesforce instance
    * **Sandbox** for testing in a Salesforce sandbox environment

    Log in with the user account that will serve as the integration user.

    Once you've connected your Salesforce account, a `Playbook` will be automatically created to send engagement data from demos to your Salesforce Opportunity, Leads, Contact, and Accounts.

    You can click view to manage the `Playbook` or refine the `Audience` filters.

    <img alt="Salesforce Integration Connected" />
  </Step>

  <Step title="Review Custom Fields">
    After connecting, Navattic automatically creates the custom fields on your Salesforce objects. You can verify these were created by:

    1. In Salesforce Setup, go to Object Manager
    2. Select Lead, Contact, Account, or Opportunity
    3. Click Fields & Relationships
    4. Look for fields starting with "Navattic\_"
  </Step>

  <Step title="Edit your Salesforce Object page">
    Navigate to your Salesforce object page that you'd like to edit (Opportunity, Lead, Contact, or Account). Select `Edit Page` under the `Setup Menu`.

    <Frame>
      <img alt="Salesforce Opportunity page" />
    </Frame>

    Search for `Dynamic Related List - Single` in the `Components` search field.

    <Frame>
      <img alt="Salesforce component list" />
    </Frame>

    Search for `Navattic Session` in the Related List field. Make sure that the Parent Record is set to the default `Use This Opportunity` (or the relevant Salesforce object).

    <Frame>
      <img alt="Salesforce Navattic Session" />
    </Frame>

    Update the `Related List Fields` to show the following fields:

    * Email
    * Demos
    * Duration (minutes)
    * Full Name
    * Flows
    * Steps Viewed
    * Very Interested Areas
    * Somewhat Interested Areas
    * Not Interested Areas
    * Session ID

    <Frame>
      <img alt="Salesforce Navattic Fields" />
    </Frame>

    Save the Page Builder and exit to the page layout.

    Once a visitor views the interactive demo share link and completes their session, this will be logged in Salesforce.

    <Frame>
      <img alt="Salesforce Opportunity Navattic Data" />
    </Frame>

    <Frame>
      <img alt="Salesforce Opportunity Navattic Session Data" />
    </Frame>

    <Icon icon="party-popper" /> **Congratulations** -- You've finished setting up Salesforce with Navattic. Reps can now connect <a href="/launchpad/share/demos#add-salesforce-opportunity">Salesforce opportunities to share links</a>.
  </Step>

  <Step title="Configure Field Mappings">
    Go to the Salesforce integration settings in Navattic and set up field mappings to control which engagement data syncs to which Salesforce fields.

    See [Field Mappings](/integrations/field-mappings) for detailed configuration options.
  </Step>

  <Step title="Set Up Playbooks">
    Create Playbooks to define when and how demo engagement data should sync to Salesforce.

    See [Salesforce Integration](/integrations/salesforce) for complete setup instructions.
  </Step>
</Steps>

## Opportunity owner data

When a presentation is connected to a Salesforce opportunity, Navattic automatically looks up the opportunity owner in Salesforce and stores their details as custom properties on the session.

| Property                  | Description                                                       |
| ------------------------- | ----------------------------------------------------------------- |
| **OpportunityOwnerEmail** | The email address of the Salesforce user who owns the opportunity |
| **OpportunityOwnerId**    | The Salesforce user ID of the opportunity owner                   |

These values are populated automatically — no additional configuration is required. They are included in webhook payloads and can be used in downstream workflows, such as routing notifications to the rep who owns the deal.

<Note>
  Opportunity owner data is only populated when a presentation share link has a Salesforce opportunity connected. See [Present demos](/launchpad/share/present#salesforce-opportunity) for instructions on connecting an opportunity to a share link.
</Note>

## Field guide: viewing Navattic sessions in Salesforce

Once your admin has completed the setup above, every demo session that originates from one of your share links is automatically logged as a **Navattic Session** record in Salesforce — no manual data entry required.

### Connect your share links to opportunities

Sessions only appear on an opportunity when your share link is connected to one at the time you create it. Without that connection, session data is still captured but won't surface on the opportunity record.

To connect a share link to an opportunity:

* When sharing a demo through Launchpad, see [Sharing demos](/launchpad/share/demos#add-salesforce-opportunity) for step-by-step instructions.
* When creating a presentation for a live call, see [Present demos](/launchpad/share/present#salesforce-opportunity).

<Tip>
  Opening Launchpad directly from a Salesforce Opportunity page automatically pre-fills the Opportunity field — no searching required. This auto-fill stays active for every additional share link you create from that same page.
</Tip>

### Find session data on the opportunity

Once a prospect views your demo, open the Opportunity record in Salesforce and scroll to the **Navattic Sessions** related list. Each row represents one individual viewing session — so if three people at the same account watch the demo, you'll see three separate rows.

### How to read each field

| Field                         | What it tells you                                                                                                                                      |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Full Name**                 | The name of the person who viewed the demo. Includes stakeholders who filled in the recipient form, even if they weren't on your original invite list. |
| **Email**                     | The email address of the viewer. Use this to identify new contacts and update your outreach.                                                           |
| **Started At**                | The date and time the session began. Use this to gauge recency and time your follow-up.                                                                |
| **Duration (minutes)**        | How long the viewer spent in the demo. Longer sessions typically signal stronger engagement.                                                           |
| **Steps Viewed**              | The number of demo steps the viewer completed. Helps you understand how far they got and where drop-off may have occurred.                             |
| **Demos**                     | Which demo or demos the viewer explored during the session.                                                                                            |
| **Flows**                     | Which flows within the demo the viewer clicked into.                                                                                                   |
| **Very Interested Areas**     | Topics the viewer flagged as high interest. Lead with these in your next conversation.                                                                 |
| **Somewhat Interested Areas** | Topics the viewer showed moderate interest in. Worth addressing, but not the headline.                                                                 |
| **Not Interested Areas**      | Topics the viewer skipped or flagged as low priority. Avoid spending call time on these.                                                               |
| **Opportunity**               | The Salesforce Opportunity this session is linked to.                                                                                                  |
| **Account**                   | The Account associated with the linked Opportunity.                                                                                                    |
| **Contact**                   | The Contact record matched to the viewer's email, if one exists.                                                                                       |
| **Lead**                      | The Lead record matched to the viewer's email, if one exists and no Contact match was found.                                                           |
| **Session ID**                | A unique identifier for this session. Share this with support if you ever need to troubleshoot a specific viewing event.                               |

### Plays to run

<AccordionGroup>
  <Accordion title="Pre-call prep: lead with what matters">
    Before any follow-up call, open the Navattic Sessions related list on the opportunity and note the **Very Interested Areas** for each viewer. Structure your agenda around those topics first — your prospect has already told you what they care about.

    Check **Not Interested Areas** so you know what to skip. Spending time on areas a prospect explicitly deprioritized can stall momentum.
  </Accordion>

  <Accordion title="Spot new stakeholders">
    If you see a **Full Name** or **Email** you don't recognize, the demo was likely forwarded internally. That's a buying signal — someone on your contact's team is doing their own research.

    Add that person as a contact on the opportunity and reach out directly. Multithreading early reduces the risk of a single point of failure in the deal.
  </Accordion>

  <Accordion title="Time your follow-up">
    Use the **Started At** field to follow up while the demo is still fresh. A same-day or next-day message referencing what the prospect explored tends to get a much higher response rate than a generic check-in.

    See [When to share demos](/launchpad/share/when-to-share) for more guidance on timing your outreach.
  </Accordion>

  <Accordion title="Re-engage stalled deals">
    If an opportunity has gone quiet and you see no new sessions in the past two weeks, it's a good time to re-engage. Create a fresh share link focused specifically on the prospect's **Very Interested Areas** from their last session, and send it with a short, personalized note.

    A targeted demo link gives the prospect a low-friction reason to re-engage without requiring them to join a call.
  </Accordion>
</AccordionGroup>

<Note>
  If the Navattic Sessions related list isn't visible on your opportunity records, ask your Salesforce admin to add it by following the [setup steps](#setup-steps) on this page.
</Note>

## Troubleshooting

### Connection Fails with "Insufficient Permissions"

**Cause:** The Salesforce user doesn't have API Enabled permission.

**Solution:**

1. Go to Salesforce Setup > Users > Profiles
2. Find the user's profile and edit it
3. Ensure "API Enabled" is checked under System Permissions
4. Save and retry the connection

### Custom Fields Not Created

**Cause:** The user may lack Modify Metadata permission or field creation is restricted.

**Solution:**

1. Use a System Administrator account to connect initially
2. Custom fields will be created automatically
3. You can then adjust permissions and reconnect with a different user if needed

### Data Not Syncing to Salesforce

**Cause:** Field-level security may be preventing writes to custom fields.

**Solution:**

1. Go to Salesforce Setup > Object Manager
2. Select the affected object (Lead, Contact, Account, or Opportunity)
3. Click Fields & Relationships
4. For each Navattic custom field, click the field name
5. Click "Set Field-Level Security"
6. Ensure the integration user's profile has "Visible" and "Editable" checked
7. Save changes

### "Record Locked" or "Unable to Lock Row" Errors

**Cause:** Salesforce record locking during high-volume updates.

**Solution:**

* These errors are typically temporary and Navattic will retry
* If persistent, check for workflow rules or validation rules that may be causing conflicts
* Consider adjusting the timing of your Playbook triggers to spread out updates

### Permission Set Assignment Fails

**Cause:** User already has maximum number of permission set assignments.

**Solution:**

1. In Salesforce Setup, go to Users > Permission Sets
2. Find "Navattic Permission Set"
3. Manually assign it to the integration user
4. Or consolidate other permission sets if the user has reached the limit

## Security Considerations

### OAuth Token Storage

Navattic stores OAuth tokens securely and uses them only to sync data according to your configured Playbooks. Tokens are:

* Encrypted at rest
* Only used for authorized API operations
* Automatically refreshed when needed
* Revocable at any time from Salesforce

### Data Access

The integration only:

* Reads data needed to match visitors to Leads/Contacts
* Writes engagement data to fields you've mapped
* Never modifies other Salesforce data
* Respects your Salesforce sharing rules and permissions

### Disconnecting the Integration

To disconnect Navattic from Salesforce:

1. In Navattic: Go to Settings > Integrations > Salesforce and click **Disconnect**
2. In Salesforce: Go to Setup > Connected Apps OAuth Usage to view and revoke the connection

Custom fields created during setup will remain in Salesforce but will no longer receive updates from Navattic.


# Salesloft
Source: https://docs.navattic.com/launchpad/integrations/salesloft

Create and share demos from within Salesloft.

<Frame>
  <img alt="Salesloft Inbox Navattic Integration" />
</Frame>

Sales reps can create and share demos from within <img alt="Salesloft Logo" /> **Salesloft**.

To access the Salesloft integration, please install the Navattic integration from the [Salesloft integration settings page](https://app.salesloft.com/app/settings/integrations).

See [Navattic Salesloft Marketplace listing](https://marketplace.salesloft.com/partners/navattic) for more details.

<Steps>
  <Step title="Compose an email">
    <img alt="" />

    In the email compose window, click on the Navattic logo to launch the integration.
  </Step>

  <Step title="Create a custom demo">
    Follow steps to create a custom demo.
  </Step>

  <Step title="Send the email">
    After creating the demo, the demo link and preview will be injected into the email body.
  </Step>
</Steps>

## Crafting emails with demos best practices

Read best practices for crafting emails based on use cases:

<CardGroup>
  <Card title="Outbound" icon="mail-check" href="/launchpad/use-cases/outbound" />

  <Card title="Pre-call discovery" icon="package-check" href="/launchpad/use-cases/pre-call-discovery" />

  <Card title="Post-call followup" icon="user-round-check" href="/launchpad/use-cases/post-call" />
</CardGroup>


# Seismic
Source: https://docs.navattic.com/launchpad/integrations/seismic

Access and share Navattic demos directly from Seismic.

The Navattic app for Seismic puts your interactive demos inside Seismic's main navigation. Reps can create and personalize demos without leaving Seismic, then drop them directly into LiveSend messages, Digital Sales Rooms, and WorkSpace assets.

<Note>
  A workspace admin must complete the admin setup before reps can connect their accounts.
</Note>

## Prerequisites

Before setting up, install the Navattic app from the [Seismic App Exchange](https://exchange.seismic.com/apps/navattic/navattic-app/) in Seismic. This step happens in Seismic and requires Seismic admin access.

## Admin setup

<Steps>
  <Step title="Open the Seismic integration">
    In Navattic, go to **Settings** > **Integrations** and select **Seismic**.
  </Step>

  <Step title="Connect and enter your Tenant ID">
    Click **Connect**. In the modal that appears, enter your Seismic Tenant ID. Your Seismic administrator can provide this if you don't have it.

    <img alt="Seismic integration connect" />
  </Step>

  <Step title="Save">
    Click **Connect** to complete the workspace-level setup. Reps can now connect their individual accounts.
  </Step>
</Steps>

## Rep setup

Each rep connects their Seismic account once. You can do this from Navattic or from within Seismic.

<Tabs>
  <Tab title="From Navattic">
    <Steps>
      <Step title="Open your Launchpad profile">
        In Navattic, go to **Launchpad** and open your **Profile**.
      </Step>

      <Step title="Connect Seismic">
        Find the **Seismic** card and click **Connect**. Follow the prompts to authorize your account in Seismic.

        <img alt="Seismic profile connect" />
      </Step>
    </Steps>
  </Tab>

  <Tab title="From Seismic">
    <Steps>
      <Step title="Open Navattic in Seismic">
        Click **Navattic** in Seismic's main navigation to open the app.
      </Step>

      <Step title="Connect from the setup screen">
        If your account isn't linked yet, you'll see a setup-required screen. Follow the prompts to connect your Navattic account.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Daily use

Once connected, you can access Navattic directly from the Seismic navigation.

<Steps>
  <Step title="Open Navattic in Seismic">
    Click **Navattic** in Seismic's main navigation.
  </Step>

  <Step title="Create or personalize a demo">
    Build a new demo or personalize an existing one for your prospect.
  </Step>

  <Step title="Copy the link into Seismic">
    Use **Copy link** or **Copy with image** to add the demo to a LiveSend message, Digital Sales Room, or WorkSpace asset.
  </Step>
</Steps>

<Info>
  On your first link, any existing Navattic share links are automatically added to your Navattic folder in Seismic.
</Info>

## Troubleshooting

<AccordionGroup>
  <Accordion title="I see a 'setup required' screen when opening Navattic in Seismic">
    This means either your rep account isn't linked yet or the workspace admin hasn't completed the admin setup. Complete the [rep setup](#rep-setup) steps above, or ask your Navattic workspace admin to verify the integration is configured.
  </Accordion>

  <Accordion title="I see a 'session expired' message">
    Close Navattic and reopen it from the Seismic navigation. This refreshes your session.
  </Accordion>

  <Accordion title="I don't see the Navattic app in Seismic's navigation">
    The Navattic app must be installed from the Seismic App Exchange by a Seismic admin. Contact your Seismic administrator to request the installation.
  </Accordion>
</AccordionGroup>


# Customize share defaults
Source: https://docs.navattic.com/launchpad/share/defaults

Manage the settings for how reps share demos

<Frame>
  <img alt="Launchpad share defaults" />
</Frame>

<Icon icon="settings" /> **Launchpad sharing settings** can be configured at the workspace level.

The share defaults allow you to configure settings such as 1) how recipients access demos 2) what is included in the demo link and 3) what types of alerts to receive.

#### Admin

<Accordion icon="settings" title="Allow reps to customize settings">
  Enable this setting to allow reps to override the default settings configured on this page when they are sharing demos.
</Accordion>

<Accordion icon="mail" title="Email template media">
  Choose the type of preview media to include in copied email templates: **Image** or **GIF**.

  <Note>Some email clients may not support GIFs in email templates.</Note>
</Accordion>

#### Access

<AccordionGroup>
  <Accordion icon="file-text" title="Recipient form gate">
    Require visitors to provide information before accessing the demo. This allows you to verify the receiver of the demo and receive insight about engaged stakeholders.

    <Tabs>
      <Tab icon="text-cursor-input" title="Name form">
        <Info>
          We recommend using the **Recipient name form** to increase the personalized-feel of the demo and unlocking more stakeholders.
        </Info>

        <Frame>
          <img alt="Recipient name gate" />
        </Frame>
      </Tab>

      <Tab icon="mail" title="Email form">
        <Frame>
          <img alt="Recipient email gate" />
        </Frame>
      </Tab>
    </Tabs>

    <div />

    <Accordion icon="rectangle-ellipsis" title="Access code">
      To add an additional layer of identity verification, you can require a unique access code for each recipient. Under the recipient form gate setting, enable `Require access code`. After the recipient enters their email address, they will be prompted to enter a unique access code sent to their email.

      Requiring an access code adds another layer of verification at the expense of friction for the buyer. Consider if this tradeoff is worth it for your use case.

      <img alt="Require access code" />
    </Accordion>
  </Accordion>

  <Accordion icon="calendar-clock" title="Expiration date">
    Set an expiration date for the demo.
  </Accordion>

  <Accordion icon="share" title="Demo share button">
    The demo share button is a powerful tool to allow your recipient to re-share your demo with other stakeholders. This powers the insight of <a href="#">Buyer's Circle</a> which alerts reps about new stakeholders involved in the buying process.

    When enabled, the demo share button will appear on the `Sidebar Checklist` or as a top banner if the Checklist is not available.

    <img alt="Demo share button" />
  </Accordion>
</AccordionGroup>

#### Demo

<AccordionGroup>
  <Accordion icon="file-text" title="Interests form">
    Customize the settings of the interests form.

    <Frame>
      <img alt="Interest Levels" />
    </Frame>

    <CardGroup>
      <Card title="Learn about interest demos" icon="chart-no-axes-column" href="/launchpad/demos/interest">
        Unlock a powerful insight - what features prospects are interested in seeing.
      </Card>
    </CardGroup>
  </Accordion>

  <Accordion icon="file-plus" title="Downloadable resources">
    Include additional files inside of the demo with a CTA button for the button to download them.

    These could be additional slide decks, custom pricing quotes, or other deal room material.

    <img alt="Downloadable resources" />
  </Accordion>

  <Accordion icon="arrow-right-to-line" title="Closing action">
    Configure what happens when a visitor reaches the end of a demo — the final step of the final flow with no next step to navigate to.

    Choose from three options:

    * **Open share modal** (default) — Shows the demo's share screen so the visitor can save or forward the link.
    * **Redirect to URL** — Sends the visitor to a URL of your choice, such as a booking page or your website.
    * **Open calendar link** — Opens a calendar link so the visitor can book a follow-up directly.

    This setting applies workspace-wide as the default for all Launchpad demos. Reps can override it per share link when **Allow reps to customize settings** is enabled.
  </Accordion>
</AccordionGroup>

#### Alerts

<AccordionGroup>
  <Accordion icon="mail" title="Email alerts">
    Manage the default email alerts that reps will recieve from their demos: `Visitor notifications`, `Re-share notification`, `Salesforce opportunity alerts`.
  </Accordion>

  <Accordion icon="slack" title="Slack alerts">
    Manage the default Slack alerts that reps will receive from their demos: `Visitor notifications`, `Re-share notification`.

    <Note>
      Slack notifications require both admin-level workspace setup and per-rep authentication. Reps must authenticate their individual Slack account before they can receive notifications, even if these defaults are enabled.
    </Note>

    <CardGroup>
      <Card title="Set up Slack notifications" icon="slack" href="/launchpad/integrations/slack">
        Learn how to configure Slack notifications for your Launchpad reps
      </Card>
    </CardGroup>
  </Accordion>
</AccordionGroup>

#### Present

<AccordionGroup>
  <Accordion icon="arrow-left-right" title="Keyboard navigation">
    Use your keyboard's arrow keys (`← →`) to move smoothly forward and backward through demo steps.
  </Accordion>

  <Accordion icon="target" title="Show beacons by default">
    When enabled, beacons start visible. Use Ctrl+B to toggle visibility.
  </Accordion>

  <Accordion icon="keyboard" title="Keyboard shortcuts">
    Turn on quick-access shortcuts, such as launching Presenter mode (`⌘P`) or toggling beacons (`⌘B`), to speed up navigation.
  </Accordion>

  <Accordion icon="mouse-pointer-click" title="Click anywhere to progress">
    Allow demo steps to advance with a simple click anywhere in Presenter mode, making live presentations more fluid and interactive.
  </Accordion>

  <Accordion icon="notepad-text" title="Presenter notes">
    (`⌘N`) Display your speaker notes alongside the demo so you can stay on track without switching screens.
  </Accordion>

  <Accordion icon="settings" title="Presentation customization">
    Control whether reps can adjust presentation settings when creating a share link.

    When enabled, reps can change settings such as keyboard navigation, keyboard shortcuts, click to progress, and presenter notes before presenting.

    When disabled, those settings are locked to the workspace defaults. Reps can still see the controls, but they appear greyed out and cannot be changed.
  </Accordion>
</AccordionGroup>


# Sharing demos
Source: https://docs.navattic.com/launchpad/share/demos

Sharing demos from Launchpad.

<Frame>
  <img alt="Launchpad Extension" />
</Frame>

Give every prospect a demo that feels built just for them. Launchpad makes it effortless for reps to share personalized, high-impact demos that speak directly to each buyer's needs.

Follow these steps to learn how to **share demos** with prospects that unlock interest and reveal new stakeholders:

## How to share demos

<Steps>
  <Step title="Click &#x22;+ Share demo&#x22;">
    <img alt="Launchpad extension share demo" />

    **Sharing demos** through Launchpad is designed to be as frictionless as possible and meet your sales reps in the tools they already use.

    The most convient way to share a demo is through the extension which will follow you anywhere on the web. To get started, click the <img /> [Launchpad extension](/launchpad/invite/launchpad-extension) in your browser and click `+ Share demo`.

    **Other places to share demos from:**

    <AccordionGroup>
      <Accordion icon="mail" title="Share a demo from your email client">
        Quickly create and send demos seamlessly while you're drafting emails to prospects. Follow the instructions on these pages to get started using these email client integrations:

        <CardGroup>
          <Card title="Gmail" href="/launchpad/integrations/gmail" icon={<img src="https://mintcdn.com/navattic-app/FQwkkhyafVZj-1wx/images/gmail.png?fit=max&auto=format&n=FQwkkhyafVZj-1wx&q=85&s=724fbc3b1c6507cb8c24c84241287819" className="my-0 h-6 w-6" />} />

          <Card title="Outlook" href="/launchpad/integrations/outlook" icon={<img src="https://mintcdn.com/navattic-app/c6crWyX_VwcL814J/images/outlook.png?fit=max&auto=format&n=c6crWyX_VwcL814J&q=85&s=25031c3e7d3c570ef0b056f50ac6909d" className="my-0 h-6 w-6" />} />

          <Card title="Outreach" href="/launchpad/integrations/outreach" icon={<img src="https://mintcdn.com/navattic-app/c6crWyX_VwcL814J/images/outreach.png?fit=max&auto=format&n=c6crWyX_VwcL814J&q=85&s=5e5342a54f5fb9b93f3396108fb03dd7"  className="my-0 h-6 w-6" />} />

          <Card title="Salesloft" href="/launchpad/integrations/salesloft" icon={<img src="https://mintcdn.com/navattic-app/mHqR2iPe3ScBaXMu/images/salesloft.png?fit=max&auto=format&n=mHqR2iPe3ScBaXMu&q=85&s=17ffabd0c24eff5963531d2078b875bb" className="my-0 h-6 w-6" />} />
        </CardGroup>
      </Accordion>

      <Accordion icon={<img src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/icons/launchpad-logo.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=dad3c35c02234ff5de704cd11c7cba78" className="my-0 h-6 w-6 -mt-1" noZoom />} title="Share a demo from the Launchpad app">
        On the <Icon icon="library" /> **My demos** page in the Launchpad app click `+ Share demo`.

        <img alt="My demos - share demo" />
      </Accordion>

      <Accordion title="More integrations">
        With the Launchpad extension, you can also share demos from:

        <CardGroup>
          <Card title="Salesforce" href="/launchpad/invite/launchpad-extension#salesforce" icon={<img src="https://mintcdn.com/navattic-app/rptQv_Iq6w06CEaq/images/salesforce.svg?fit=max&auto=format&n=rptQv_Iq6w06CEaq&q=85&s=a52c32327bc98ac8fd07bce1941cccb1" className="h-6 w-6" />} />

          <Card title="Linkedin" href="/launchpad/invite/launchpad-extension#linkedin" icon="linkedin" />
        </CardGroup>
      </Accordion>
    </AccordionGroup>
  </Step>

  <Step title="Select demo type">
    <img alt="Select demo type" />

    Next, choose the **type of demo** you want to share to match how you're engaging with your prospect.

    There are two types of demos sales reps can share:

    <Tabs>
      <Tab title="1-1 demo">
        Specify the **company domain** you are sharing the demo with. This will be used for personalizing the demo with relevant content and for tracking purposes.
        <Info>In most cases, we recommend sharing **1-1 demos** as this allows you to share more relevant content for each deal and better track engagement.</Info>

        <Note>
          Company is required by default. If your workspace admin has made Company optional in Launchpad settings, you can leave it blank. When Company is left empty, the recipient email-domain gate is automatically disabled for that link.
        </Note>
      </Tab>

      <Tab title="1-many (outbound)">
        1-many demos are intended to be used when you are sharing with multiple prospects / companies (ex in an outbound campaign).

        <div />
      </Tab>
    </Tabs>

    <Accordion icon={<img src="https://mintcdn.com/navattic-app/rptQv_Iq6w06CEaq/images/salesforce.svg?fit=max&auto=format&n=rptQv_Iq6w06CEaq&q=85&s=a52c32327bc98ac8fd07bce1941cccb1" className="h-6 w-6" style={{marginTop:'-4px'}} />} title="Add Salesforce Opportunity">
      When sharing a demo, you can also include a **Salesforce Opportunity**. This will associate the demo with a specific opportunity in Salesforce, allowing you to track the demo's performance and engagement within the context of the opportunity.

      <img alt="Salesforce Opportunity" />
    </Accordion>
  </Step>

  <Step title="Select content">
    <img alt="Select content for demo" />

    **Selecting content** to craft a demo that resonates with your prospect. Choose the most relevant content to highlight the features and value that matter most to them.

    Assemble the content of your demo by selecting flows or select an existing standard demo.

    <Info>Already know what the prospect is interested in from a demo request form or previous call? Filter by those interests to select flows.</Info>
  </Step>

  <Step title="Customize settings">
    <img alt="Customize demo settings" />

    Make your demo feel personal and relevant by **customizing the settings**. Add an intro video, supporting resources, and engagement options to create a tailored experience for every prospect.

    <Accordion icon="Video" title="Personal intro video">
      Include a personal welcome of your demo to add a personal touch for the prospect.

      To make it feel personalized you could refer to the prospect by name, reference specific talking points from a previous conversation, or generally get them excited about what they are about to see.

      <Frame>
        <img alt="Personal intro video" />
      </Frame>
    </Accordion>

    **Advanced settings**

    <AccordionGroup>
      <Accordion icon="file-text" title="Interests form">
        Customize the settings of the interests form.

        <Frame>
          <img alt="Interest Levels" />
        </Frame>

        <CardGroup>
          <Card title="Learn about interest demos" icon="chart-no-axes-column" href="/launchpad/demos/interest">
            Unlock a powerful insight - what features prospects are interested in seeing.
          </Card>
        </CardGroup>
      </Accordion>

      <Accordion icon="file-plus" title="Downloadable resources">
        Include additional files inside of the demo with a CTA button for the button to download them.

        These could be additional slide decks, custom pricing quotes, or other deal room material.

        <img alt="Downloadable resources" />
      </Accordion>

      <Accordion icon="link" title="Custom URL">
        Customize the URL path of the demo. For example you could personalize it with the company name eg `mycompany.navattic.com/yourcompany`
      </Accordion>

      <Accordion icon="file-text" title="Recipient form gate">
        Require visitors to provide information before accessing the demo. This allows you to verify the receiver of the demo and receive insight about engaged stakeholders.

        <Tabs>
          <Tab icon="text-cursor-input" title="Name form">
            <Info>
              We recommend using the **Recipient name form** to increase the personalized-feel of the demo and unlocking more stakeholders.
            </Info>

            <Frame>
              <img alt="Recipient name gate" />
            </Frame>
          </Tab>

          <Tab icon="mail" title="Email form">
            <Frame>
              <img alt="Recipient email gate" />
            </Frame>
          </Tab>
        </Tabs>

        <div />

        <Accordion icon="rectangle-ellipsis" title="Access code">
          To add an additional layer of identity verification, you can require a unique access code for each recipient. Under the recipient form gate setting, enable `Require access code`. After the recipient enters their email address, they will be prompted to enter a unique access code sent to their email.

          Requiring an access code adds another layer of verification at the expense of friction for the buyer. Consider if this tradeoff is worth it for your use case.

          <img alt="Require access code" />
        </Accordion>
      </Accordion>

      <Accordion icon="mail-open" title="Email tracking">
        When sharing a link using an email platform such as Apollo, Outreach, Salesloft, or Hubspot you can using **email tracking** to identify the visitor via query parameters.

        <img alt="Email tracking" />
      </Accordion>

      <Accordion icon="languages" title="Language">
        If your demo is available in more than one language, select which language visitors will see when they open this link. This option appears only when [multilingual demos](/demos/multilingual) are configured for your workspace.

        Use the **Language** dropdown to choose from the languages already added to this demo. Each share link can have its own language, so you can send targeted links to different audiences.
      </Accordion>
    </AccordionGroup>
  </Step>

  <Step title="Create invites">
    <img alt="Create invites for demo" />

    Add your prospect's details and include all relevant stakeholders involved in the deal. This ensures everyone receives a personalized invite and their engagement is tracked within Launchpad.

    <Accordion icon="mail" title="Send invite to demo">
      If you enable `Send invite to demo`, an automatic email invite will be sent to all the invited users asking them to visit the demo. Keep this option unchecked if you want to send the email yourself.

      <img alt="Send invite to demo" />
    </Accordion>
  </Step>

  <Step title="Copy & send the demo link ">
    <img alt="Copy Launchpad demo link" />

    <Icon icon="party-popper" /> **Congratulations** - your demo is ready to share! Copy the link and include it in your prospect email to deliver a personalized, engaging interactive demo.

    <Accordion icon="image" title="Copy with preview">
      When creating a link, you can also include a preview of the demo. This is particularly useful when sharing the link via email and can be an engaging way to showcase the demo.

      <img alt="Copy GIF" />
    </Accordion>
  </Step>
</Steps>

## Manage share defaults

To standardize the sharing settings across your workspace, you can set default values for the share settings. This includes the default recipients, personalization properties, and other settings.

<CardGroup>
  <Card title="Customize share defaults" icon="settings" href="/launchpad/share/defaults">
    Standardize the demo sharing settings across your workspace
  </Card>
</CardGroup>


# Present demos
Source: https://docs.navattic.com/launchpad/share/present

Share and present Navattic demos during live calls

<Frame>
  <img />
</Frame>

Navattic demos can be <Icon icon="presentation" /> **presented** during live calls to provide an interactive, personalized experience that keeps prospects engaged.

With features like **Presenter Notes** to guide your pitch and **Salesforce opportunity connection** to track every demo, your team can deliver with confidence and tie presentations directly to pipeline impact.

## Specifying recipient

When you create a share link, you can choose to specify a **Company** with a `Company domain` or **Visitor** recipient with an `email`.

<img alt="Presentation recipient" />

<Info>
  If you are presenting the demo to one recipient, the **Visitor** recipient is recommended. For
  most use cases, we recommend sticking to the **Company** recipient.
</Info>

## Presentation controls

When presenting a demo, you can enable or disable additional controls to fit your live demo workflow:

<Note>
  If your workspace admin has disabled **Presentation customization**, these settings will appear greyed out and reflect your workspace defaults. Contact your admin to change the defaults or re-enable customization.
</Note>

<AccordionGroup>
  <Accordion icon="arrow-left-right" title="Keyboard navigation">
    Use your keyboard's arrow keys (`← →`) to move smoothly forward and backward through demo steps. Presentation clickers that send **Page Up** and **Page Down** signals also work for navigation, making it easy to advance slides hands-free during an in-person or conference presentation.
  </Accordion>

  <Accordion icon="target" title="Show beacons by default">
    When enabled, beacons start visible. Use `Ctrl+B` to toggle visibility during the presentation.
  </Accordion>

  <Accordion icon="keyboard" title="Keyboard shortcuts">
    Turn on quick-access shortcuts to speed up navigation during a live call:

    | Shortcut        | Mac                    | Windows / Linux     | What it does                    |
    | --------------- | ---------------------- | ------------------- | ------------------------------- |
    | Presenter mode  | `Ctrl+P` or `Option+P` | `Ctrl+P` or `Alt+P` | Toggle presenter overlay on/off |
    | Presenter notes | `Ctrl+N` or `Option+N` | `Ctrl+N` or `Alt+N` | Show or hide your speaker notes |
    | Toggle beacons  | `Ctrl+B` or `Option+B` | `Ctrl+B` or `Alt+B` | Show or hide all beacons        |
  </Accordion>

  <Accordion icon="mouse-pointer-click" title="Click anywhere to progress">
    Allow demo steps to advance with a simple click anywhere in Presenter mode, making live presentations more fluid and interactive.
  </Accordion>

  <Accordion icon="notepad-text" title="Presenter notes">
    Display your speaker notes alongside the demo so you can stay on track without switching screens.
  </Accordion>
</AccordionGroup>

<img alt="Presentation advanced" />

## Presenter notes

Presenter notes let you add talking points to each step of your demo so you can stay on message during live presentations. These notes are visible only to the presenter, giving your team confidence and consistency without distracting the prospect.

<img alt="Presentation notes" />

## Salesforce Opportunity

When creating a presentation, you can connect a Salesforce Opportunity to associate the demo with a specific deal and track which demos are being shown to each opportunity.

<img alt="Salesforce Opportunity" />

If you open Launchpad from a Salesforce Opportunity page, the Opportunity field is automatically pre-filled with the current opportunity. This auto-fill persists when you create additional presentations from the same page — you don't need to re-select the opportunity each time.

## Manage present defaults

To standardize the present settings across your workspace, you can set default values for the share settings.

<CardGroup>
  <Card title="Customize share defaults" icon="settings" href="/launchpad/share/defaults#present">
    Standardize the demo sharing settings across your workspace
  </Card>
</CardGroup>


# When to share demos
Source: https://docs.navattic.com/launchpad/share/when-to-share

Tips and best practices for when to share demos in the sales process.

Interactive demos can be used at any stage of the sales process, from initial contact to closing the deal. They can help to build trust, demonstrate value, and provide a more personalized buying experience.

Sharing interactive demos throughout the sales cycle can be a new paradigm for sales reps. Following these recommendations can help you get the most out of Navattic.

## When to send a demo

One of the best times to share a demo with a prospect is before a scheduled call (**pre-call discovery**). Sharing a demo before a scheduled meeting allows prospects to educate and qualify themselves in advance. When positioned effectively, the demo can also be shared internally, helping bring additional stakeholders into the conversation.

If the prospect engages with the demo ahead of time, the sales rep gains valuable insights into <Icon icon="chart-no-axes-column" /> **Interest levels** and viewer behavior—enabling them to tailor the conversation and focus on the most relevant areas during the meeting.

<Tip>
  One of the best times to share a demo with a prospect is before a scheduled call (**pre-call
  discovery**).
</Tip>

Learn more about how to use demos for pre-call discovery before a scheduled call here:

<CardGroup>
  <Card title="Pre-call discovery" icon="package-check" href="/launchpad/use-cases/pre-call-discovery">
    Learn about what the prospect is interested in before the first call.
  </Card>
</CardGroup>

### Other use cases to consider

We recommend considering using interactive demos at the following stages:

* **Outbound**: Use interactive demos to explore the use cases and benefits of your product with potential customers.
* **Pre-call discovery**: Use interactive demos to explore the use cases and benefits of your product with potential customers.
* **Qualification demo**: Use an interactive demo as a Qualification tool when a prospect requests a demo before involving technical sales reps (SEs).
* **Live Demo**: Present demos on live demo calls.
* **Post-call followup**: Send relevant followup demos to prospects after the call.

## Follow up with prospects

Following up is *essential* -- the modern buyer evaluating software is busy and might have forgotten to open the demo. We recommend creating a reminder to follow up two days after sending a demo if there hasn't been any activity. <Icon icon="calendar" /> **After two days**:

#### <Icon icon="circle-check" /> If the prospect has viewed the demo

This is a great opportunity to invite the prospect to share it internally with other stakeholders or schedule a meeting.

#### <Icon icon="circle-x" /> If the prospect has not viewed the demo

Encourage them to try the demo so they're prepared for your upcoming conversation.

<Tip>
  Following up is *essential* -- set a reminder to **follow up two days after sending a demo**.
</Tip>

## What to do after the prospect views the demo

When a prospect views a demo, you'll receive an <Icon icon="mail" /> <a href="/launchpad/tracking/email-alerts">Email alert</a> as soon as the session has ended. In the email, you'll receive insight of what the prospect is interested in. We recommend viewing these interests before hopping on a call to get an idea of what information to prepare in advance. You can also use interests to follow up with other more relevant content. Here are a few things to consider when following up:

* **Speed to lead**. Act quickly when you receive a demo view alert. Prompt follow-up keeps the momentum going before the prospect's interest may fade. Timely outreach is often the difference between a missed opportunity and a meaningful next step.
* **Understand what the prospect cares about**. Use the Interest insight from the demo to quickly understand the prospect's motivation. This will help you tailor your follow-up message and prepare relevant content.

When you receive a view alert, use it as a prompt to re-engage the prospect. A well-timed message might look like:

<Email title="Pre-call discovery viewed demo email">
  I noticed you spent time exploring \{Interest}—it seems like that’s a key area of interest. Is
  there anyone else on your team who would benefit from seeing the demo or joining our upcoming
  call?
</Email>

<Info>
  Example email for **pre-call discovery**. Take a look at the below use case guides for how to
  craft emails based on the stage of the sales process.
</Info>

This approach helps reinforce relevance and encourages broader stakeholder involvement.

### Explore use cases for sharing demos

Take a look at the following guides for a more in-depth explanation for how to craft prospect messaging and include demos between meetings throughout the sales process.

<CardGroup>
  <Card title="Pre-call discovery" icon="package-check" href="/launchpad/use-cases/pre-call-discovery">
    Learn about what the prospect is interested in before the first call.
  </Card>

  <Card title="Post-call followup" icon="user-round-check" href="/launchpad/use-cases/post-call">
    Send relevant followup demos to prospects after the call.
  </Card>

  <Card title="Outbound" icon="mail-check" href="/launchpad/use-cases/outbound">
    Send demos in outbound email campaigns to book more meetings.
  </Card>
</CardGroup>


# Outbound
Source: https://docs.navattic.com/launchpad/use-cases/outbound

Send demos in outbound email to book more meetings.

Interactive demos can be a powerful asset for **Outbound** by driving engagement and increasing booked meetings. By sending demos to prospects, you can shorten sales cycles by providing hands-on access early in the buying process.

Sales reps responsible for development (SDRs, BDRs) can send demos to a broader list of prospects to quickly identify who is actively engaging and interested in learning more about the product or service. This approach helps prioritize follow-up with the most qualified leads.

## What to send prospects

When reaching out cold, craft a short, personalized email that introduces the demo, includes clear instructions on how to view it, and sets expectations around time investment (e.g., “This interactive demo takes just 3–5 minutes to explore”).

Position the demo as a quick way to get a feel for the product’s value—no meeting required.

<Email title="Outbound email">
  <div> **Subject**: 3 minute \{Company} demo</div>

  <div>**Hi \{First Name}**,</div>

  <div>How are you handling \{Challenge} today?</div>

  <div>Wanted to share a 3 minute product demo so you can see how \{Product} can help.</div>

  <div> Open to learning more?</div>

  <div>
    **Sarah Almonds**
    <div>Business Development <span>|</span> Navattic</div>
  </div>
</Email>

<Tip>
  Try short **(2–4 words)** email subject lines to boost open rates for outbound. Keep the message
  short and casual and avoid overly salesy language.
</Tip>

## How to follow up

Following up is *essential* for outbounding -- the modern buyer evaluating software is busy and might have forgotten to open the demo. We recommend creating a reminder to follow up two days after sending a demo if there hasn't been any activity. <Icon icon="calendar" /> **After two days**:

#### <Icon icon="circle-check" /> If the prospect has viewed the demo

This is a great opportunity to invite the prospect to book time for a live demo.

<Email title="Outbound viewed demo email">
  <div> I saw that you've had a chance to look at the demo and that you are interested in \{Interest}.</div>

  <div> Would it make sense to schedule a call to discuss this further? Here is my calendar link to book time to chat: \{Calendar link}.</div>
</Email>

#### <Icon icon="circle-x" /> If the prospect hasn’t viewed the demo

Encourage them to try the demo and offer assistance if they have any questions.

<Email title="Outbound hasn't viewed demo email">
  <div>Just wanted to send a quick reminder to check out the demo I shared.</div>

  <div>Let me know if you have any questions when you get the chance to check it out!</div>
</Email>

<Tip>
  Following up is *essential* for outbounding -- for targeted outreach, set a reminder to **follow
  up two days after sending a demo**.
</Tip>

## What to do when a prospect views the demo

When a prospect views a demo, you'll receive an <Icon icon="mail" /> [Email alert](/launchpad/tracking/email-alerts) as soon as the session has ended. We recommend reaching out to the prospect as soon as you receive this alert either by phone or email. In the email, you'll receive insight of what the prospect is interested in. We recommend focusing your discussion on the prospect's selected interests.

<img alt="Email Alerts Interest Levels" />

## Example outbound plays

Looking for inspiration? Check out our example plays—like competitor takedowns, role-based personalization, or re-engaging churned customers—to spark ideas for your next outbound strategy. These approaches can help you tailor your outreach and stand out in the inbox.

<AccordionGroup>
  <Accordion icon="git-pull-request-closed" title="Closed lost (feature)">
    Use Interactive demos to highlight features that previously lost or stalled deals.

    <Email title="Outbound email">
      <div>**Subject**: We just shipped \{Feature name}</div>

      <div>**Hi \{First Name}**,</div>

      <div>Since we last spoke, we've shipped \{Feature name}, something I recall was critical to your team. Here's a short walkthrough in case it's worth revisiting:</div>
    </Email>
  </Accordion>

  <Accordion icon="replace" title="Competitor takedown">
    Use Interactive demos to highlight how your product performs better than your competitors.

    <Email title="Outbound email">
      <div>**Subject**: We just shipped \{Feature name}</div>

      <div>**Hi \{First Name}**,</div>

      <div>Thought you’d find this quick demo helpful—it shows how we stack up against \{Competitor} and where we tend to outperform.</div>
    </Email>
  </Accordion>

  <Accordion icon="briefcase-business" title="Role/persona personalization">
    * Different roles care about different aspects of your product, SEs want depth, PMMs want storytelling, Demand Gen wants conversions.
      * For SEs: a demo that shows how the platform integrates, configures, or scales, i.e. technical proof points.
      * For Product Marketing: a demo built to highlight a new feature or message launch, showcasing the story they want to tell.
      * For Demand Gen: a short, conversion-focused demo that mirrors the website journey and encourages action.
  </Accordion>

  <Accordion icon="refresh-ccw-dot" title="Churned customer re-engagement">
    Outbound to churned customers who churned due to: strategy fit, feature functionality, etc.

    <Email title="Outbound email">
      <div>**Subject**: We just shipped \{Feature name}</div>

      <div> **Hi \{First Name}**,</div>

      <div>Teams that left and came back usually cite \{Feature name}, here’s a quick look at how the platform’s evolved since you last used it:</div>
    </Email>
  </Accordion>
</AccordionGroup>

### Example outbound email templates

Try some of other example email templates for outbounding we created to get started. We recommend tailoring them to your product and use case.

<AccordionGroup>
  <Accordion title="Customized demo for {Company}">
    <Email title="Outbound email">
      <div>**Subject**: Customized demo for \{Company}</div>

      <div>**Hi \{First Name}**,</div>

      <div>How are you handling \{Challenge} today?</div>

      <div>Wanted to share a 3 minute product demo so you can see how \{Product} can help.</div>

      <div>Open to learning more?</div>
    </Email>
  </Accordion>

  <Accordion title="Interactive demo for {Company} – no signup needed">
    <Email title="Outbound email">
      <div>**Subject**: Interactive demo for \{Company} – no signup needed</div>

      <div>**Hi \{First Name}**,</div>

      <div>I saw a few people from \{Company} were spending time on our website.</div>

      <div>I put together a quick interactive walkthrough of \{Product}—no login, no setup required.</div>
      <div>It’s the fastest way to see if it’s a fit.</div>

      <div>Open to learning more?</div>
    </Email>
  </Accordion>

  <Accordion title="See how {Problem} gets solved in 2 minutes">
    <Email title="Outbound email">
      <div>**Subject**: See how  gets solved in 2 minutes</div>

      <div>**Hi \{First Name}**,</div>

      <div>We built a quick interactive demo showing how  helps teams like yours solve \{Problem}.</div>

      <div>No slides or long videos—just click through and see it in action.</div>

      <div>Open to scheduling a call?</div>
    </Email>
  </Accordion>

  <Accordion title="A faster way to evaluate {Product}">
    <Email title="Outbound email">
      <div>**Subject**: A faster way to evaluate \{Product}</div>

      <div>**Hi \{First Name}**,</div>

      <div>Instead of booking time right away, here’s a quick hands-on demo. It’s an easy way to see what  can do.</div>

      <div>If it’s relevant, happy to chat: \{Calendar link}</div>
    </Email>
  </Accordion>

  <Accordion title="Thought this demo might be relevant">
    <Email title="Outbound email">
      <div>**Subject**: Thought this demo might be relevant</div>

      <div>**Hi \{First Name}**,</div>

      <div>Given that you were looking at \{X} on our website, I put together this demo to show how  can help teams like yours solve \{Problem}.</div>

      <div>Takes less than 3 minutes to explore.</div>
    </Email>
  </Accordion>
</AccordionGroup>

## Create templates for your emails

Once your happy with your copy, create email templates to save yourself time and effort when sending out emails.

<CardGroup>
  <Card title="Adding demos to email templates" href="/launchpad/share/crafting-emails#adding-demos-to-email-templates">
    Save email templates in your preferred email outbounding tool
  </Card>
</CardGroup>


# Post-call followup
Source: https://docs.navattic.com/launchpad/use-cases/post-call

Send relevant followup demos to prospects after the call.

Interactive demos can be a great way to send the prospect a relevant **post-call followup**. Keep the momentum going by sharing a tailored demo as a follow-up. A post-call demo reinforces key takeaways, gives the prospect something tangible to share internally, and helps continue the conversation asynchronously.

Sharing a demo after the meeting allows prospects to revisit the product on their own time and loop in additional stakeholders who may have missed the call. When framed correctly, it can accelerate internal alignment and keep your deal moving forward.

## What to send prospects

Send a follow-up email that includes a link to the personalized demo, sets expectations around time commitment (e.g., “This will only take 10–15 minutes to explore”), and reinforces the main points discussed on the call.

Encourage the prospect to share the demo with others involved in the buying process. This helps extend your reach and ensures your message stays consistent as it moves through their organization.

<Email title="Post-call followup email">
  <div>**Subject**: Follow-Up Demo – Tailored to Our Conversation</div>

  <div>**Hi \{First Name}**,</div>

  <div>
    Great speaking with you earlier! I put together a quick interactive demo that highlights the areas we discussed and how \{Product} can support your team. It takes about **10–15 minutes to explore**  and is personalized to your use case.
  </div>

  <div>
    You can go through it at your own pace and even customize the experience based on what’s most relevant. Feel free to share it with others on your team who might be involved in the evaluation process.
  </div>

  <div>
    Let me know if any questions come up or if you'd like to dive deeper into anything we didn’t cover during the call.
  </div>

  <div>
    **Mark Antihill**
    <div>Account Executive <span>|</span> Navattic</div>
  </div>
</Email>

## How to follow up

Following up with with the prospect after sending the demo helps reinforce key takeaways and keep the deal moving forward. Even if a prospect was engaged during the call, they may forget to revisit the demo—so timely follow-up is critical.

We recommend setting a reminder to follow up two days after sending the post-call demo if there hasn’t been any activity. <Icon icon="calendar" /> **After two days**:

#### <Icon icon="circle-check" /> If the prospect has viewed the demo

This is a great chance to ask your champion to share it internally with other decision-makers or stakeholders who couldn’t attend the call.

<Email title="Post-call viewed demo email">
  <div>
    I saw that you've had a chance to look at the demo and that you are interested in \{Interest}. Here is \{X} that might be also relevant to you.
  </div>

  <div>
    I’d love to hear your thoughts now that you've had a chance to explore —or feel free to invite other colleagues to the demo.
  </div>
</Email>

#### <Icon icon="circle-x" /> If the prospect hasn’t viewed the demo

Send a gentle reminder encouraging them to check it out—framing it as a helpful recap and resource for sharing with their team.

<Email title="Post-call hasn't viewed demo email">
  <div>
    Just wanted to send a quick reminder to check out the demo I shared after our call. It’s a
    helpful summary of what we covered—and a great resource to pass along to others on your team.
  </div>

  <div>Let me know if you have any questions when you get the chance to check it out!</div>
</Email>

## What to do when a prospect views the demo

When a prospect engages with a post-call demo, you'll receive an <Icon icon="mail" /> <a href="/launchpad/tracking/email-alerts">Email alert</a> shortly after their session ends. This alert includes insights into which parts of the demo they explored—helping you understand what stood out most.

We recommend reaching out promptly by email or phone to build on that momentum. Reference the specific areas they showed interest in, and use that information to guide the next conversation or share additional resources relevant to their priorities.

<img alt="Email Alerts Interest Levels" />

<Tip>
  **Speed to lead**: Act quickly when you receive a demo view alert. Prompt follow-up keeps the
  momentum going before the prospect's interest may fade.
</Tip>

## Custom demos

<Icon icon="circle-fading-plus" /> **Custom demos** allow reps to assemble tailored demos based on
what they learn about the prospect's interests and priorities. Learn how to create Custom Demos:

<CardGroup>
  <Card title="Custom demos" icon="circle-fading-plus" href="/launchpad/demos/interest">
    Enable your sales team to assemble custom demos from pre-built templates.
  </Card>
</CardGroup>

### Explore example emails for post-call followups

Try some of our example email templates we created to get started. We recommend tailoring them to your product, industry, and use case.

<AccordionGroup>
  <Accordion title="Recap: Here’s the demo we discussed">
    <Email title="Post-call followup email">
      <div>**Subject**: Recap: Here’s the demo we discussed</div>

      <div>**Hi \{First Name}**,</div>

      <div>Great talking today! Here’s that interactive demo I mentioned—walk through the key workflows we discussed at your own pace.</div>

      <div>Let me know what stands out.</div>
    </Email>
  </Accordion>

  <Accordion title="Let your team see {Product} in action">
    <Email title="Post-call followup email">
      <div>**Subject**: Let your team see \{Product} in action</div>

      <div>**Hi \{First Name}**,</div>

      <div>Thanks again for your time! If others on your team want to see what \{Product} does, here’s an interactive demo they can explore.</div>
    </Email>
  </Accordion>

  <Accordion title="Your personalized demo of  {Interest A}, {Interest B}, and {Interest C}">
    <Email title="Post-call followup email">
      <div>**Subject**: Your personalized demo of \{Interest A}, \{Interest B}, and \{Interest C}</div>

      <div>**Hi \{First Name}**,</div>

      <div>Thanks for the time. You mentioned you were interested in \{Interest A}, \{Interest B}, and \{Interest C}. Here's a custom demo I put together that highlights those features:</div>
    </Email>
  </Accordion>

  <Accordion title="Click through this tailored interactive demo">
    <Email title="Post-call followup email">
      <div>**Subject**: Click through this tailored interactive demo</div>

      <div>**Hi \{First Name}**,</div>

      <div>As promised, here’s a quick interactive demo tailored to what we covered on the call.
      You can revisit the key flows we discussed—click through anytime.</div>
    </Email>
  </Accordion>

  <Accordion title="Follow-up from our chat – try the demo">
    <Email title="Post-call followup email">
      <div>**Subject**: Let your team see \{Product} in action</div>

      <div>**Hi \{First Name}**,</div>

      <div>Enjoyed our conversation! I’ve pulled together a short demo that shows \{Product} solving the exact use case we talked about.</div>

      <div>Take it for a spin—no setup needed.</div>
    </Email>
  </Accordion>
</AccordionGroup>


# Pre-call discovery
Source: https://docs.navattic.com/launchpad/use-cases/pre-call-discovery

Learn about what the prospect is interested in before the first call.

Getting a prospect to attend a live meeting is already a win—don’t waste that time on basic overviews. Instead, use a **pre-call discovery demo** to educate the prospect and uncover additional stakeholders ahead of time. This allows your first call to focus on deeper discovery, addressing questions, and advancing the deal—instead of starting from square one.

Sharing a demo before a scheduled meeting allows prospects to educate and qualify themselves in advance. When positioned effectively, the demo can also be shared internally, helping bring additional stakeholders into the conversation. Sales reps can use this insight to tailor their approach and prepare for the call.

## What to send prospects

Craft an email to the prospect that includes instructions on how to view the demo and sets expectations for how long it will take. Ensure that it will provide helpful context and set the stage for a more productive conversation.

Also encourage them to forward the demo to others on their team who might be involved in the buying decision.

<Email title="Pre-call discovery email">
  <div>**Subject**: Your personalized demo ahead of our call</div>

  <div>**Hi \{First Name}**,</div>

  <div>Here’s the interactive demo I mentioned. Please take a few minutes to explore it before our call on Monday—it should only take about 10 minutes to complete. You’ll also be able to customize the demo based on what you’re interested in seeing.</div>

  <div>You can also share the demo with colleagues by clicking the Invite button in the lower-left corner of the demo.</div>

  <div>Let me know if any questions come up ahead of the call!</div>

  <div>
    **Mark Anthill**
    <div>Account Executive <span>|</span> Navattic</div>
  </div>
</Email>

<Tip>
  Encouraging prospects to share the demo early in the sales cycle can help **uncover new
  stakeholders and reveal the buying circle.**
</Tip>

## How to follow up

Following up with with the prospect after sending the demo, but before the scheduled meeting, helps ensure the prospect is prepared for the call and can uncover new stakeholders to join the meeting that may be involved in the buying decision.

We recommend setting a reminder to follow up two days after sending the pre-call discovery demo. <Icon icon="calendar" /> **After two days**:

#### <Icon icon="circle-check" /> If the prospect has viewed the demo

This is a great chance to ask your champion to share it internally with other decision-makers and invite other stakeholders to join the scheduled meeting.

<Email title="Pre-call discovery viewed demo email">
  I noticed you spent time exploring \{Interest}—it seems like that’s a key area of interest. Is
  there anyone else on your team who would benefit from seeing the demo or joining our upcoming
  call?
</Email>

#### <Icon icon="circle-x" /> If the prospect hasn’t viewed the demo

Send a gentle reminder encouraging them to check it out—framing it as a helpful resource before the scheduled meeting that will help focus the conversation.

<Email title="Pre-call hasn't viewed demo email">
  <div>Just wanted to send a quick reminder to check out the demo I shared before our call on \{Date}. It's a helpful to see this in **advance of our call** to help focus our conversation.</div>

  <div>Feel free to invite other colleagues to the demo and join our upcoming call.</div>
</Email>

## What to do when the prospect views the demo

When the prospect views the demo, you'll receive an <Icon icon="mail" /> **Email alert** with a summary of their session and a summary of what they are interested in. Take a minute to review this information before the call so that you know in advance what to prepare.

<img alt="Email Alerts Interest Levels" />

## Interest demos

<Icon icon="chart-no-axes-column" /> **Interest demos** are extremely useful for **pre-call
discovery**: because they can be used to collect what the prospect is interested in and what their
priorities are.

Learn how to create Interest Demos:

<CardGroup>
  <Card title="Building interest demos" icon="chart-no-axes-column-increasing" href="/launchpad/demos/interest">
    Unlock a powerful insight - what features prospects are interested in.
  </Card>
</CardGroup>

### Explore example emails for pre-call exploration

Try some of our example email templates we created to get started. We recommend tailoring them to your product, industry, and team needs.

<AccordionGroup>
  <Accordion title="Here's a demo ahead of our call">
    <Email title="Pre-call discovery email">
      <div>**Subject**: Here's a demo ahead of our call</div>

      <div>**Hi \{First Name}**,</div>

      <div>Thanks for scheduling time on my calendar. I'll be looking forward to our demo call on \{Date}.</div>

      <div>In preparation for the call, here's an interactive demo that you can try for yourself when you have a moment. Please take a few minutes to explore the demo **before the call**.</div>
    </Email>
  </Accordion>

  <Accordion title="Quick demo before our call">
    <Email title="Pre-call discovery email">
      <div>**Subject**: Quick demo before our call</div>

      <div>**Hi \{First Name}**,</div>

      <div>Ahead of our chat, I wanted to share this short interactive demo. It’s a quick way to get familiar with \{Product} before we dive in.</div>

      <div>Takes less than 2 minutes.</div>
    </Email>
  </Accordion>

  <Accordion title="See {Product} in action before we talk">
    <Email title="Pre-call discovery email">
      <div>**Subject**: See \{Product} in action before we talk</div>

      <div>**Hi \{First Name}**,</div>

      <div>Before our meeting, here’s a quick walkthrough showing how \{Product} solves \{Problem}.</div>

      <div>Gives a head start so we can go deeper on the call.</div>
    </Email>
  </Accordion>

  <Accordion title="Get a head start before our meeting">
    <Email title="Pre-call discovery email">
      <div>**Subject**: Get a head start before our meeting</div>

      <div>**Hi \{First Name}**,</div>

      <div>Here’s an interactive demo that covers the basics of  so you can explore it before our conversation.</div>

      <div>It should help frame our discussion and speed things up.</div>
    </Email>
  </Accordion>

  <Accordion title="Try this demo before we connect">
    <Email title="Pre-call discovery email">
      <div>**Subject**: Try this demo before we connect</div>

      <div>**Hi \{First Name}**,</div>

      <div>To make the most of our upcoming call, I thought you might want to try this short demo of \[Product].</div>

      <div>You’ll get a feel for how it works in under 90 seconds.</div>
    </Email>
  </Accordion>

  <Accordion title="Intro to {Product} – quick demo">
    <Email title="Pre-call discovery email">
      <div>**Subject**: Intro to \{Product} – quick demo</div>

      <div>**Hi \{First Name}**,</div>

      <div>Looking forward to our call! In the meantime, here’s a quick interactive demo that walks through the core experience.</div>

      <div>No setup or login—just click through.</div>
    </Email>
  </Accordion>
</AccordionGroup>


# Embed your demo
Source: https://docs.navattic.com/share/embed

Embed your demo on your marketing website or product.

Once you've created your gold-standard demo, it's time to <Icon icon="square-code" /> **Embed** the demo on your marketing website or product.

Embedding your demo on your marketing website is a powerful way to generate top of funnel leads, drive demand, or educate new prospects.

## Embedding a demo

Follow these steps to embed your demo on a webpage:

<Steps>
  <Step title="Click share and select embed option">
    On a Product Demo, select `Share`. For `Share via` select `Website embed`. Select between the
    sharing options to embed your demo on your website or product.

    <img alt="Embed demo options" />
  </Step>

  <Step title="Click Get Embed Code">
    Click `Get Embed Code` to copy the code snippet. Drop this code snippet into your website or
    product.

    <img alt="Embed demo code" />
  </Step>
</Steps>

## Embedding a Navattic Agent

Navattic Agents support the same three embed strategies as product demos — inline, full page, and pop-up.

To get the embed code for a Navattic Agent:

1. Open the Navattic Agent from the **Agents** section. The demo must be published.
2. Click **Share** in the editor toolbar.
3. Under **Embed on your website**, click **Embed**.
4. Choose an embed strategy (inline, full page, or pop-up) and click **Get Embed Code**.
5. Copy the code and drop it into your website.

<Note>
  The lazy-load overlay option is available for Navattic Agent embeds, but the auto-generated background image is not supported. Upload a custom background image in the embed settings instead.
</Note>

## Choosing an embed type

Navattic offers three embed types. Select the one that best fits where and how you want to present your demo.

<Tabs>
  <Tab title="Inline embed">
    The inline embed renders the demo directly on the page, scaling to fit its parent container. Visitors see the demo immediately without needing to click anything.

    **When to use:**

    * Blog posts and content marketing pages
    * Product or feature pages where you want to showcase a workflow
    * Landing pages where the demo is the primary content
    * Tutorial or documentation pages

    ```html theme={null}
    <iframe
      src="https://capture.navattic.com/your-demo-id"
      style="border: none; width: 100%; aspect-ratio: 16 / 10;"
      allow="fullscreen"
    ></iframe>
    ```
  </Tab>

  <Tab title="Full page embed">
    The full page embed takes up the entire browser window with fixed positioning. It provides an immersive, app-like experience with no surrounding content.

    **When to use:**

    * Dedicated demo pages (e.g., yoursite.com/demo)
    * Full-screen experiences where you want maximum visitor focus
    * Standalone demo pages linked from email campaigns or ads

    ```html theme={null}
    <iframe
      src="https://capture.navattic.com/your-demo-id"
      style="position: fixed; top: 0; left: 0; width: 100%; height: 100%; border: none; z-index: 999999;"
      allow="fullscreen"
    ></iframe>
    ```
  </Tab>

  <Tab title="Pop-up embed">
    The pop-up embed opens the demo in a modal overlay when a visitor clicks a button. The demo stays hidden until triggered, keeping the page lightweight.

    **When to use:**

    * Call-to-action buttons on marketing pages
    * Navigation menus or site headers
    * Pages where the demo should complement, not replace, the existing content
    * When you want to minimize initial page load time

    **HTML version:**

    ```html theme={null}
    <button data-navattic-open="https://capture.navattic.com/your-demo-id" data-navattic-title="Product Demo">
      View Demo
    </button>
    <script src="https://js.navattic.com/embeds.js"></script>
    ```

    **JavaScript version:**

    ```html theme={null}
    <button id="demo-button">View Demo</button>
    <script src="https://js.navattic.com/embeds.js"></script>
    <script>
      NavatticEmbed.initPopup("https://capture.navattic.com/your-demo-id", {
        title: "Product Demo"
      });
      document.getElementById("demo-button").addEventListener("click", function() {
        NavatticEmbed.openPopup("https://capture.navattic.com/your-demo-id");
      });
    </script>
    ```
  </Tab>
</Tabs>

<Info>
  **Recommendation:** Use **inline embeds** for content-heavy pages where the demo is part of the narrative. Use **full page embeds** for dedicated demo pages where you want an immersive experience. Use **pop-up embeds** for CTA buttons where you want to keep the page lightweight and let visitors choose when to engage.
</Info>

## Inline sizing options

When using an inline embed, you can choose how the demo scales within its container. Select a sizing strategy in the embed modal after choosing the inline embed type.

<Tabs>
  <Tab title="Fixed aspect ratio">
    The demo fills 100% of the container width, and the height scales automatically to maintain a consistent aspect ratio. The default ratio is **16:10**.

    **When to use:** Most marketing pages and landing pages. This option provides responsive width while maintaining consistent proportions across all screen sizes.

    ```html theme={null}
    <iframe
      src="https://capture.navattic.com/your-demo-id"
      style="border: none; width: 100%; aspect-ratio: 16 / 10;"
      allow="fullscreen"
    ></iframe>
    ```
  </Tab>

  <Tab title="Responsive">
    The demo fills 100% of both the width and height of its parent container. This is the default sizing option.

    **When to use:** When you're embedding inside a container that already has defined dimensions, such as a fixed-height column or a card component.

    <Warning>
      The parent container must have an explicit height set, otherwise the iframe may collapse to zero height.
    </Warning>

    ```html theme={null}
    <iframe
      src="https://capture.navattic.com/your-demo-id"
      style="border: none; width: 100%; height: 100%;"
      allow="fullscreen"
    ></iframe>
    ```
  </Tab>

  <Tab title="Fixed dimensions">
    The demo uses exact pixel dimensions. The default is **1100px x 600px**. The size stays constant regardless of screen size or container.

    **When to use:** When you need precise control over the demo size and your layout can accommodate fixed dimensions. Use sparingly, as this doesn't adapt to smaller screens.

    ```html theme={null}
    <iframe
      src="https://capture.navattic.com/your-demo-id"
      style="border: none; width: 1100px; height: 600px;"
      allow="fullscreen"
    ></iframe>
    ```
  </Tab>
</Tabs>

<Info>
  **Recommendation:** Use **Fixed aspect ratio (16:10)** for most marketing pages -- it looks great on desktop and scales down gracefully on mobile. Use **Responsive** when embedding inside a container with a defined height. Use **Fixed dimensions** only when you need exact pixel control.
</Info>

For more details on how your demo content adapts to different screen sizes, see [Responsive strategies](/build/responsive).

## Customizations

Follow the instructions below to enable AI visibility, enable Lazy Load, disable demo pre-loading, or manage the embed lifecycle using JavaScript.

**AI visibility**

When AI visibility is enabled, Navattic uses Copilot to generate a plain-text walkthrough of your demo and include it in the embed code. The text is hidden from visitors but readable by AI crawlers and search engines, making your demo's content discoverable even though it runs inside an iframe.

To enable AI visibility:

1. In the embed modal, select the **AI visibility** toggle under **Customizations**.
2. Wait for Copilot to generate the walkthrough. The copy buttons are disabled until generation is complete.
3. Copy your embed code. The AI-readable text is already included in the snippet.

The generated text is derived from your demo's step content, including step names, dialog text, and button labels. Because the text is baked into the snippet at copy time, re-embedding the demo after publishing changes does not automatically update already-embedded copies.

**Lazy Load Overlay**

When the lazy load overlay toggle is selected for an embedded interactive demo, an overlay will appear over the top of the demo frame. This can be helpful to improve page load times, reduce load traffic to the demo, or provide better guidance on how to engage with the interactive demo.

The default background image (the first capture in the Product Demo) as well as the call to action to launch the interactive demo can be adjusted by updating the embed code as shown in [this video](https://www.loom.com/share/7c2502238002410592067f2df430943c?sid=a32339c2-9ef6-4575-aa3d-ac7cf2c980b6).

<img alt="" />

**Disable pre-loading demo**

The pop-up demo embed preloads the demo on the page so that it loads instantly when the visitor opens it. This behavior can be undesirable in some situations like, for example, when there are many demos on a page.

To disable this behavior, add the `data-navattic-preload="false"` data attribute to the button that is opening the demo.

**Control lifecycle of the embed with Javascript**

The default embed code for the lazy-load and pop-up embed types use HTML in order to make the embed process as simple as possible. If more control over the initialization and loading of the embed is required, the embeds.js script includes the Javascript class, `NavatticEmbed` which includes a few methods that can be helpful for controlling the lifecycle of the embed elements:

* `NavatticEmbed.loadEmbeds()`: initializes all lazy-load embeds on the page
* `NavatticEmbed.initPopup(<embed_url>, <config>)`**:** adds the pop-up embed to the page but hides it until the below method is called
  * The second argument is an object containing configuration properties for the embed. The following (optional) properties are supported:
    * `title`: the title that will appear in the header of the demo
    * `preload`: if this is set to false, the demo won't be pre-loaded when it's initialized. It will only start to render the demo when it's opened. Defaults to true.
    * `onClose`: a callback that is triggered when the visitor closes the pop-up.
* `NavatticEmbed.openPopup(<embed_url>)`: opens the demo so that the modal appears overlayed on the page. This would usually be attached to a click handler on the button that would be opening the pop-up demo.

## Closing a pop-up from within the demo

Browsers prevent an iframe from directly controlling its parent page, so Navattic does not have a built-in button to dismiss a pop-up embed. You can work around this using [Navattic JS](/tracking/navattic-js) to listen for events fired by the demo and close the pop-up in your own JavaScript.

The most common pattern is to close the pop-up when the visitor reaches the final step and clicks a button set to **Mark as Converted**.

<Steps>
  <Step title="Set the final step's button action">
    In the Flow Builder, select the button on your final step. Set its action to **Mark as Converted**.
  </Step>

  <Step title="Add Navattic JS to your page">
    Add the [Navattic JS](/tracking/navattic-js) snippet to the page hosting your pop-up embed, alongside your existing embed code. Follow the setup instructions to get the snippet.
  </Step>

  <Step title="Listen for the Converted event and close the pop-up">
    Use `navattic.onEvent()` to detect when the visitor converts, then hide or remove your pop-up container:

    ```javascript theme={null}
    navattic.onEvent(function(event) {
      if (event.type === "Converted") {
        // Replace this with your own code to remove or hide the pop-up container
        document.getElementById("your-popup-container").style.display = "none";
      }
    });
    ```
  </Step>
</Steps>

<Note>
  This approach works with any pop-up implementation — replace the example code in step 3 with whatever your pop-up library or custom JavaScript uses to close the modal.
</Note>

## Examples

See how leading companies embed Navattic demos on their websites:

<CardGroup>
  <Card title="Wiz" href="https://wiz.io/academy/application-security/sast-vs-dast">
    Pop-up embed on an academy page
  </Card>

  <Card title="Atlan" href="https://atlan.com/">
    Inline embed on homepage
  </Card>

  <Card title="Lattice" href="https://lattice.com/tour">
    Inline embed on dedicated tour page
  </Card>
</CardGroup>


# Exporting a demo
Source: https://docs.navattic.com/share/export

Export your demo as a PDF, GIF, or MP4 video.

The **Export preview** option in the demo builder lets you generate a shareable file from your demo — as a PDF document, an animated GIF, or an MP4 video.

<img alt="Export Preview" title="Export Preview" />

## How to export

1. Open your demo in the builder.
2. Click the **Export preview** button (available from the demo builder toolbar or the **More** menu).
3. Select an export type:
   * **Video** — exports an MP4 file you can embed or attach to emails
   * **GIF** — exports an animated GIF suited for email and social media
   * **Document** — exports a PDF with screenshots and step narration text

## Exporting as a PDF

The Document export type generates a PDF that includes a screenshot and narration text for each step.

### Selecting flows

When you choose **Document**, a multi-select appears listing all flows in the demo. Select one or more flows to include in the PDF. If you select multiple flows, they are combined into a single file named `Demo flows (N).pdf`. A single-flow export is named `[Flow name] (N).pdf`.

### Step limit

PDF exports support up to **60 steps** across all selected flows. If your selection exceeds 60 steps, an inline warning appears and the export is capped at 60 steps.

<Note>
  Only the narration text visible on each step is included in the PDF. Steps without narration still appear as screenshots.
</Note>

### Copy as text

Instead of downloading a PDF, you can copy the narration text from all selected steps to your clipboard. Click the dropdown arrow next to **Export PDF** and select **Copy as Text**. The text is structured by flow and step, separated by flow dividers.

## Exporting as a video or GIF

For Video and GIF exports, select a single flow and configure:

* **Number of steps** — how many steps to include (up to 15)
* **Time per step** — how long each step displays (1–5 seconds)

The exported file renders each step in sequence and loops (for GIF) or plays once (for MP4).


# Navattic Forms
Source: https://docs.navattic.com/tracking/forms/index

Capture and track visitor information through forms in your demos

<Frame>
  <img alt="Form builder" />
</Frame>

<Icon icon="file-text" /> **Forms** are one of the most effective ways to capture visitor information during demos. Forms can identify visitors, qualify leads, and trigger personalized follow-ups based on demo engagement.

## Why use forms in demos?

Forms serve multiple purposes in your interactive demos:

* **Lead capture**: Collect visitor contact information for follow-up
* **Lead qualification**: Gather company and role information to prioritize outreach
* **Personalization**: Use form data to customize the demo experience
* **Analytics**: Track conversion rates and identify drop-off points
* **Integration**: Sync form submissions with your CRM and marketing automation tools

### How to create a form

Forms can be created from within the flow builder or on the forms page. Once a form has been created, it can be reused across different demos. To create a form, follow these steps:

<Steps>
  <Step title="Click +Create on the Forms page">
    Click `+Create` to be taken directly into the form builder.
  </Step>

  <Step title="Add form fields">
    Add form fields by clicking on the <Icon icon="text-cursor-input" /> [Properties](/tracking/forms/properties) in the left sidebar. Every form field has an associated property. A property is field of information stored on a Visitor or an Account.

    Mark the field as `required` if you want to require every visitor to fill it out. <img alt="Form builder properties" />
  </Step>

  <Step title="Adjust settings (optional)">
    Adjust the settings of the form by clicking `Settings` in the top right. You can configure things like the submit button text, the company logo on the form, and the repeat visitor behavior.

    <Tabs>
      <Tab title="Skip if already identified">
        Visitors who have already submitted the form will bypass it and continue to the next step.
      </Tab>

      <Tab title="Pre-fill previous submissions">
        Form fields are automatically populated with data from the visitor's previous submissions.
      </Tab>

      <Tab title="Leave form blank">
        Form fields remain empty regardless of previous submissions, requiring visitors to fill out all fields again.
      </Tab>
    </Tabs>

    <img alt="Form builder repeat behavior" />
  </Step>

  <Step title="Configure the submit button action (optional)">
    By default, submitting the form advances the visitor to the next step. You can instead send visitors to a specific URL after they submit.

    In the **Demo builder**, select the form step and open **Step Settings**. Under the submit button, change the action to **Navigate** and enter the destination URL. The URL supports [personalization tokens](/build/captures/personalization) so you can pass collected form values (such as email or company) directly into the redirect link.

    <Note>
      Form data is flushed before the redirect, so all submitted values are captured even when navigating away from the demo.
    </Note>
  </Step>

  <Step title="Publish your form">
    Once you've finished adding form fields, click `Publish` to save your form. Inside the form builder, you can now add the form by adding a form step and selecting the form.
  </Step>
</Steps>

<Icon icon="party-popper" /> **Congratulations** -- you've finished building your first form, next learn how to view submissions and connect it to your CRM.

<CardGroup>
  <Card title="Form Submissions" icon="table" href="/tracking/forms/submissions">
    View and export form submission data
  </Card>

  <Card title="Field Mappings" icon="arrow-left-right" href="/integrations/field-mappings">
    Configure how form fields map to your CRM
  </Card>
</CardGroup>

#### FAQs

<AccordionGroup>
  <Accordion title="How do I remember form submissions between sessions?">
    <Info>
      Cookies must be enabled on the demo for properties to persist between sessions. Workspace admins can enable cookies by default within the Workspace **Settings** > **Defaults** > toggle on **Cookie tracking.**

      To enable cookie tracking for just one demo, locate the demo in the **Product Demos** tab > Click the three dots that appear when you hover over the demo > **Edit details** > toggle on **Cookie tracking.**
    </Info>
  </Accordion>

  <Accordion title="Form submissions aren't appearing when I test — what should I check?">
    Ad blockers and browser privacy extensions can intercept Navattic's form tracking events, causing submissions to appear missing during testing even when they would work for real visitors.

    If you're testing a form and submissions aren't showing up:

    1. Disable any ad blockers or privacy extensions for the page you're testing on.
    2. Alternatively, open the demo in an incognito/private window with extensions disabled.
    3. Re-submit the form and check again.

    Real visitors without ad blockers will not experience this issue.
  </Accordion>

  <Accordion title="Can I block visitors from using personal email addresses in forms?">
    Yes. When you add an **Email** field to a form, you can configure a list of blocked domains directly on that field. Visitors who enter an email address from a blocked domain will see an error ("Please enter a valid work email") and cannot submit the form.

    To configure blocked domains:

    1. Open the form in the form builder.
    2. Click the **Email** field to select it.
    3. In the field settings panel, enable the **Blocked domains** toggle.
    4. Add the domains you want to block (for example, `gmail.com`, `yahoo.com`). You can add them one at a time or paste a list.

    The block applies only to the specific Email field where it is configured. Other fields in the same form are not affected.
  </Accordion>
</AccordionGroup>


# Custom properties
Source: https://docs.navattic.com/tracking/forms/properties

Create and manage custom form fields to capture specific visitor information

<Frame>
  <img alt="Custom properties" />
</Frame>

<Icon icon="text-cursor-input" /> **Custom properties** allow you to collect specific information
from visitors beyond standard fields like name and email. Create custom fields tailored to your
business needs, qualification criteria, and integration requirements.

## What are custom properties?

Custom properties are configurable form fields that you define to capture additional visitor information. They can be:

* **Lead qualification data**: Budget, timeline, team size
* **Demographic information**: Industry, role, department
* **Product interests**: Features, use cases, integrations
* **Custom identifiers**: Account ID, customer number, campaign code

Custom properties are used as a centralized way to track information about visitors. It is used across Forms, Personalization, Identification, and Integration field mappings.

### Property types

<CardGroup>
  <Card title="Text" icon="text-cursor">
    Single-line text for names, titles, or short answers
  </Card>

  <Card title="Textarea" icon="align-left">
    Multi-line text for comments or detailed responses
  </Card>

  <Card title="Email" icon="at-sign">
    Email address field with automatic validation
  </Card>

  <Card title="Checkbox" icon="square-check">
    Boolean fields for opt-ins or confirmations
  </Card>

  <Card title="Multiselect" icon="list-check">
    Multiple choice options for features or preferences
  </Card>

  <Card title="Phone" icon="phone">
    Phone number field with formatting validation
  </Card>

  <Card title="Date" icon="calendar">
    Date picker for timelines or scheduling
  </Card>

  <Card title="Number" icon="hash">
    Numeric inputs for quantities, budget, or team size
  </Card>

  <Card title="Select" icon="chevron-down">
    Dropdown with single selection from predefined options
  </Card>

  <Card title="URL" icon="link">
    Validated URL inputs for websites or resources
  </Card>

  <Card title="Image" icon="image">
    Upload field for logos, screenshots, or visual content
  </Card>
</CardGroup>


# Identifying accounts
Source: https://docs.navattic.com/tracking/identify/accounts

Track visitors at the company level.

<Info>Enabled in workspaces on the Base plan and above.</Info>

<Frame>
  <img alt="Accounts page" />
</Frame>

<Icon icon="building" /> **Account Based Engagement** is used to automatically reveal the companies
that engage with your demos, even if individual Visitors do not engage with a Visitor Identification
method outlined above.

Navattic partners with Clearbit to reveal the company and firmographic information of visitors.

Each identified Account will include an engagment rating (high vs. low) based on the actions they took in your demo, the number of unique Visitors at the account who viewed your demos, the total time spent in your demos, and more. Click any column header to sort the table; click again to reverse the sort order. This data may be exported as a CSV or sent to Hubspot or Salesforce via a direct integration.

<Image alt="">
  \*\*
</Image>

## Overview

While knowing which companies are engaging with your content is always helpful, this tool was designed especially with these audiences in mind.

*Customers using gated or ungated demos in a top-of-funnel strategy:*

* Navattic will identify the companies with the most unique visitors viewing your account. Use this data to set up the most effective ABM campaigns.
* Send Account-level demo engagement information to Salesforce, to be shared with SDR teams for targeted outreach.
* Supplement an existing gated demo: identify the company Accounts for Visitors who drop off without completing the current form.

*Customers using demos as leave-behind assets:*

* Send a real-time alert to Slack if your prospected account engages with your content
* Use Accounts to understand if your buyer or champion is circulating your demos internally, without needing to use a gate
* Send Account-level demo engagement information to Salesforce, to identify your most-engaged Accounts and influenced Opportunities


# Identifying visitors
Source: https://docs.navattic.com/tracking/identify/visitors

Learn about who is viewing your demos.

<Frame>
  <img alt="" />
</Frame>

<Icon icon="user-round-search" /> **Identification** helps you understand which **Visitors** and
**Accounts** are engaging with your demos. This section covers the various methods of identifying
Visitors and Accounts in Navattic.

## How to identify visitors

There are a few different ways to identify visitors in Navattic:

<CardGroup>
  <Card icon="file-text" title="Forms" href="#forms">
    Add a form gate to your demo (Good for website embeds)
  </Card>

  <Card icon="link" title="Query Params" href="#query-params">
    Add tracking params to the URL (Good for email campaigns)
  </Card>

  <Card icon="code" title="Navattic JS" href="#navattic-js">
    Track logged in users in your app (Good for in-app demos)
  </Card>
</CardGroup>

For real-world examples of these approaches in practice, see [5 Ways to Identify Demo Visitors without a Form](https://www.navattic.com/blog/ungated-interactive-demos).

<Tabs>
  <Tab title="Forms">
    One easy way to identify visitors to your interactive demos is through a form. Follow these steps to add a Navattic or third-party (ex Marketo, Hubspot, etc) form:

    <CardGroup>
      <Card title="Navattic Forms" icon="file-text" href="/tracking/forms">
        Capture and track visitor information through forms in your demos.
      </Card>

      <Card title="Embedded forms" icon="square-code" href="/tracking/forms/embedded">
        Integrate third-party forms and scheduling tools directly in your demo.
      </Card>
    </CardGroup>
  </Tab>

  <Tab title="Query Params">
    Query strings can be used to add identification tokens to demo share links at scale. This occurs outside of the Navattic app and is a quick way to identify demo recipients if you are sending a quick email or setting up an email campaign.

    ### Manual Entry of Query Strings

    Full Name, Email, and Company Name can be added to any demo share link as identification tokens, using the corresponding Attribute Names:

    | Value        | Type   | Attribute Name |
    | ------------ | ------ | -------------- |
    | Full name    | STRING | user.fullName  |
    | Email        | STRING | user.email     |
    | Company name | STRING | company.name   |

    Use this format when adding attributes to the end of any Navattic demo share link:

    * `navattic-demo-link``?``attribute=value`

    For example, this link will now identify the recipient as [jane.doe@navattic.com](mailto:jane.doe@navattic.com), since the "user.email" attribute is set to "[jane.doe@navattic.com](mailto:jane.doe@navattic.com)".

    * [https://training.navattic.com/rd3v0zhg?user.email=jane.doe@navattic.com](https://training.navattic.com/rd3v0zhg?user.email=jane.doe@navattic.com)

    You may add more attributes by adding a **&** in between clauses:

    * `navattic-demo-link?user.email=value&user.fullName=value&company.name=value`

      ### Assisted Entry of Query Strings

      If you are using a sales automation tool such as Hubspot, Outreach, Salesloft, or other similar tools that contain contact email addresses, you may use the email variable already present in these tools to identify recipients.

      Simply append the `?user.email={{email}}` query string to the end of your demo URL in any templates you create, and these tools will unfurl the demo URL containing the correct value.

      Example link:

      * `navattic-demo-link?user.email={{EMAIL_VARIABLE}}&user.fullName={{NAME_VARIABLE}}`

      Take care to use the correct attribute name as these may vary between platforms. Here are a few common examples:

      | Platform                                                                                              | Value | Attribute Name        | Complete query string for outreach                  |
      | ----------------------------------------------------------------------------------------------------- | ----- | --------------------- | --------------------------------------------------- |
      | [HubSpot](https://knowledge.hubspot.com/website-pages/personalize-your-content)                       | Email | `{{contact.email}}`   | `navattic-demo-link?user.email={{contact.email}}`   |
      | [Outreach](https://support.outreach.io/hc/en-us/articles/226680368-Outreach-Variables-Overview)       | Email | `{{email}}`           | `navattic-demo-link?user.email={{email}}`           |
      | [Salesloft](https://help.salesloft.com/s/article/Available-Dynamic-Fields?language=en_US#Person_Tags) | Email | `{{email_address}}`   | `navattic-demo-link?user.email={{email_address}}`   |
      | [Pardot](https://help.salesforce.com/s/articleView?id=sf.pardot_handlebars_merge_fields.htm\&type=5)  | Email | `{{Recipient.Email}}` | `navattic-demo-link?user.email={{Recipient.Email}}` |
  </Tab>

  <Tab title="Navattic JS">
    If you need more flexibility about when and how to identify visitors, the following implementation will allow Navattic to receive Visitor or Account identification data that is gathered elsewhere on your marketing website. Share these steps with your website team for implementation.

    ### Implementation

    By including the JavaScript snippet in Step 1 of [Navattic JS](/navattic-js#NuYfC), we unlock the ability to programattically identify users from your marketing website. The Embed Events script will expose a global `window.navattic` object for your marketing website to use.

    To identify a user programmatically, call `window.navattic.identify` in your code.

    ```javascript theme={null}
    navattic.identify({
      'user.email': 'steve@apple.com',
      'user.fullName': 'Steve Jobs',
      // ...any other fields you want to use!
    });
    ```
  </Tab>
</Tabs>

# Other Use Cases and Workflows

The following workflows require you to add the [Navattic JS](/tracking/navattic-js) snippet to the `head` of your website(s).

## Identifying visitors across subdomains

If you have demos embedded on multiple subdomains or you want to identify Visitors on one subdomain and track their demo engagement on another subdomain, it is possible for the Visitors identity to be shared across these subdomains. This can be enabled with the following steps:

1. Install [Navattic JS](/tracking/navattic-js) on each site
2. On the Navattic JS **Configuration** page (in your Navattic Workspace under Settings > Navattic JS), enable [Domain-level Visitor Tracking](/tracking/navattic-js)
3. Follow the above steps to identify Visitors

## Tracking UTM Parameters

Embedded iframe demos do not automatically receive UTM parameters from the page on which they are embedded. However, you can automatically pass on UTM parameters by adding [Navattic JS](/tracking/navattic-js) to the \<head> of your site and enabling the **Query Parameter Tracking** option shown below.

<img alt="" />

You will now see Visitor UTMs appear in your CSV export and your Visitors tab > expand a Visitor > "Tracking" section.

### Manually Tracking UTMs

If you would prefer to manually set up UTM tracking use [these steps](https://stackoverflow.com/questions/20366731/how-can-i-pass-utm-parameters-from-url-to-an-iframe) to pass UTM parameters from the landing page URL into the iframe src URL. This step makes UTMs visible to Navattic.

Once this is set up, navigate to the Flow Builder and select the CTA button that uses a **Navigate to URL** action > include your UTM variables using this format:

`?utm_medium={{utm_medium}}&utm_campaign={{utm_campaign}}`

To automatically add utm\_source=navattic, check the box for **Add tracking params.**

<img alt={true} />

### Passing non-standard parameters

The standard UTM set (`utm_source`, `utm_medium`, `utm_campaign`, `utm_term`, `utm_content`, `utm_referrer`) is the only set forwarded automatically when you enable **Add tracking params**. Parameters outside this set — such as Google Ads click parameters (`gad_source`, `gbraid`, `gclid`) or any custom attribution params — are not auto-forwarded and require a manual placeholder setup.

#### Set up a custom property placeholder

<Steps>
  <Step title="Create a custom property">
    In your Navattic workspace, go to **Settings** > **Custom properties** and create a new property for each non-standard parameter you want to carry (for example, `gad_source`).
  </Step>

  <Step title="Pass the value in the iframe src">
    On the page where your demo is embedded, append the parameter to the iframe `src` URL so Navattic can read it:

    ```html theme={null}
    <iframe
      src="https://capture.navattic.com/your-demo-id?gad_source=VALUE_HERE"
      style="border: none; width: 100%; aspect-ratio: 16 / 10;"
      allow="fullscreen"
    ></iframe>
    ```

    If you use a tag manager, populate the value dynamically from the page URL before injecting it into the src.
  </Step>

  <Step title="Reference the property as a placeholder on your CTA button">
    In the Flow Builder, open the **Navigate to URL** action on your CTA button and include the property as a placeholder:

    `https://your-destination.com/register?gad_source={gad_source}`

    Navattic substitutes `{gad_source}` with the value that was passed in via the iframe src.
  </Step>
</Steps>

#### Empty-parameter behavior

When a placeholder resolves to an empty value — for example, if a visitor arrives without a `gad_source` param in the page URL — Navattic substitutes an empty string, producing a URL like:

`https://your-destination.com/register?gad_source=`

Navattic does not strip parameters with empty values. If you need to omit the parameter entirely when no value is present, handle the conditional logic before it reaches the iframe. The most common approach is to build the full query string conditionally in Google Tag Manager and pass the result as a single custom property:

1. In GTM, create a variable that reads `gad_source` from the page URL.
2. Write a custom JavaScript variable that returns `&gad_source=VALUE` only when the value is non-empty, or an empty string otherwise.
3. Concatenate this output into the iframe `src` before injecting it into the page.

This keeps your destination URL clean and avoids empty params reaching your analytics or ad platform.

#### Tracking CRM Cookies

If you are using a Hubspot or Marketo cookie on your marketing site, [Navattic JS](/tracking/navattic-js) can associate the cookie when identifying Visitors. This can make it easier to route Visitor and engagement data to these CRMs.

To include CRM cookies when identifying visitors, enable the Navattic JS `CRM Cookie Tracking`.

## Benefits of Identifying visitors

**Once a Visitor is identified, you can:**

* Connect demo engagement data with the correct Visitor record in the [Visitors tab](/analyze#_MXGs)
* Send combined visitor and demo engagement data to third-party platforms for additional analysis (ex. see in Hubspot, "*Jessica* at *Navattic* viewed *8 steps* of the *Get Started Product Tour*")
* Personalize demos for the visitor (ex., "Hi, , welcome to your demo!")

**Once an Account is identified, you can:**

* Prioritize your most engaged Accounts in ABM strategies
* See which demos the Account interacted with to prepare relevant resources
* Send this data to Slack, Salesforce, or Hubspot to alert the right teams

<Note>
  If a visitor is identified by email, their associated account is always visible in the Visitors tab — even if Account Based Engagement (ABE) is not enabled on your workspace.
</Note>

***

#### FAQs

<Accordion title="What are the following app.navattic.com cookies used for?">
  The following filtered cookies are used for Navattic app auth and are not used for Visitor tracking. These cookies would never be sent from a Visitor page.

  ```text theme={null}
  __Secure-xxxxxxx
  ```

  ```text theme={null}
  __Host-next-auth-.csrf-token'
  ```
</Accordion>


# Install Navattic JS
Source: https://docs.navattic.com/tracking/navattic-js/index

Install and configure the Navattic JS tracking script.

<Icon icon="square-code" /> **Navattic JS** is a script that can be added to your website or application to identify and track visitors to your demos.

It's a powerful tool to track visitors since it integrates with the existing identity layer of your application or website. There are two useful ways to use Navattic JS:

<CardGroup>
  <Card title="Identify Visitors" icon="user-round-check" href="#identify-visitors-with-navattic-js">
    Unlock significantly more identified visitors by calling `navattic.identify()` whenever you have the visitor's email.
  </Card>

  <Card title="Subscribe to events" icon="code" href="/tracking/navattic-js/subscribe-to-events">
    Integrate with any tracking scripts already installed on your website by calling `navattic.onEvent()`.
  </Card>
</CardGroup>

## Navattic JS Setup

Follow these steps to add the Navattic JS tracking scripts to your websites and applications.

<Steps>
  <Step title="Navigate to setup steps">
    Navigate to the [Navattic JS settings](https://app.navattic.com/w/settings/js) and then follow steps to add the Navattic JS tracking scripts to your website and app.

    <img alt="Navattic JS Setup" />
  </Step>

  <Step title="Decide which websites and apps to track">
    Navattic JS can be added to any website or application that you want to track.

    To unlock the greatest number of identified visitors, we recommend adding Navattic JS to your app (**app.company.com**), as well as any websites hosting your demos. <img alt="" />
  </Step>

  <Step title="Copy and paste the tracking script">
    Under the `Implementation checklist`, copy the script and follow instructions to add it to the `<head>` of your website or application.

    [Calling Navattic JS Identify](#calling-navattic-js-identify) (Recommended).
  </Step>

  <Step title="Adjust configuration (optional)">
    Customize the behavior of Navattic JS by adjusting the configuration settings.

    <Tabs>
      <Tab title="Auto form tracking">
        Automatically track visitor information from external forms embedded outside of your Navattic demo.

        For example, if a Visitor completes a HubSpot form elsewhere on your marketing website, their email address will now be surfaced in the Navattic Visitors tab and available to use in Navattic Playbooks (i.e., Integrations).

        <Info>
          See [Capturing forms in iframes](#capturing-forms-in-iframes) for details on browser and Pardot restrictions.
        </Info>
      </Tab>

      <Tab title="Cross-domain tracking">
        Track visitors across sub-domains. For example, this will allow you to track the same visitor on your marketing website (**company.com**), docs (**docs.company.com**), and blog (**blog.company.com**).
      </Tab>

      <Tab title="CRM tracking scripts">
        Navattic JS can automatically match demo visitors to HubSpot or Marketo contacts using existing cookies. Their demo activity will sync to your CRM, and if email capture is enabled (via automatic form submissions or JavaScript), the visitor’s email will also appear in the Navattic Visitors tab.
      </Tab>

      <Tab title="Query parameter tracking">
        Automatically include page query parameters from the parent page as Navattic visitor attributes. For example, if a demo visitor views an embedded demo on `navattic.com/pricing?utm_medium=internal\&client_id=chromestore`, the parameters `utm_medium` and `client_id` will automatically turn into Visitor properties.
      </Tab>
    </Tabs>
  </Step>
</Steps>

## Identify visitors with Navattic JS

Once you've [installed Navattic JS](#navattic-js-setup), you can call the `identify` method to anytime you have the visitor's email address available.

This identification method will be prioritized over other [automatic tracking configuration methods](#auto-form-tracking).

```javascript theme={null}
// Add to a place where user.email is available
navattic.identify({ email: user.email })
```

### FAQ

<Accordion title="Capturing Forms in iFrames">
  Due to browser security restrictions, [Navattic JS](/tracking/navattic-js) can’t automatically capture form submissions from iframes. For those cases, as a workaround, it is possible to add code to the form that will send the submission to the parent page so that Navattic JS can identify the visitor and associate them with the demos elsewhere on your site.

  For Pardot and other form providers that allow you to include a script tag within the form, below is an example of a script that can be added to your form that will pass the form submission to Navattic JS.

  Note: you may need to update the `KEYS_TO_SEND` and the element ID values of your script with values that are specific to your form configuration.

  ```html theme={null}
  <script>
    function sendFormToNavattic(event) {
      event.preventDefault();

      const form = event.target;
      const formData = new FormData(form);
      const KEYS_TO_SEND = ['name', 'email', 'phone']; // This can be customized

      const data = {};

      for (const [key, value] of formData.entries()) {
        if (KEYS_TO_SEND.includes(key)) {
          data[key] = value;
        }
      }

      if (Object.keys(fields).length > 0) {
        window.parent.postMessage({
          kind: 'navattic:iframe-form-submission',
          fields,
        });
      }
    }
    const formElement = document.getElementById('iframe-form'); // use the actual form selector
    formElement?.addEventListener('submit', sendFormToNavattic);
  </script>
  ```
</Accordion>


# Google Analytics (GA4)
Source: https://docs.navattic.com/tracking/navattic-js/subscribe-to-events/ga4

Track demo events in Google Analytics 4 for comprehensive user behavior analysis.

Follow these steps to integrate Navattic JS events with <img alt="GA4 Logo" /> **Google Analytics 4**:

<Note>
  `navattic.onEvent` callbacks only fire when event tracking is enabled. If your site uses a cookie consent banner, configure [cookie tracking](/integrations/cookie-consent) so that events are only sent after consent is granted.
</Note>

<Steps>
  <Step title="Install Navattic JS">
    Follow these instructions to install [Navattic JS](/tracking/navattic-js). This JS snippet should be installed *after* your [existing GA4 tag.](https://support.google.com/analytics/answer/9744165?hl=en#zippy=%2Cin-this-article%2Cinstall-a-google-tag)

    <Info>
      Use these instructions if you are using <img alt="GTM Logo" /> [Google Tag Manager](/tracking/navattic-js/subscribe-to-events/google-tag-manager) instead.
    </Info>
  </Step>

  <Step title="Send Navattic events to GA4">
    The above script has some tools to help your website communicate bi-directionally with the embedded demo. To send Navattic event data to GA4, add the following script to the `<head>` right after the script above.

    ```javascript theme={null}
    <script>
    	navattic.onEvent(function(eventData){
    		gtag("event", `navattic_event`, eventData);
    	});
    </script>
    ```
  </Step>

  <Step title="See Navattic Events in GA4">
    Once the JS snippet is installed on your website, no further configuration is needed in Google Analytics to start seeing Navattic events. You should now see a new event named `navattic_event` under the [events sections](https://support.google.com/analytics/answer/9322688?hl=en#zippy=%2Crealtime-report%2Cdebugview-report) of GA4.

    <Info>
      Google Analytics can take [24-48 hours to process
      data](https://support.google.com/analytics/answer/9333790?hl=en#:~:text=Many%20of%20your%20reports%20and,your%20website%20or%20app%20successfully)' ' from your website or Navattic demo.
    </Info>

    To troubleshoot your integration, use [real-time reporting](https://support.google.com/analytics/answer/9271392?sjid=13083582562165458896-NA). The event `navattic_event` should appear under the **Event count by Event Name** widget in real-time reporting.

    <Frame>
      <img alt="" />
    </Frame>

    Navattic events include all actions a user takes within a demo such as step viewed, flow completed, checklist started, and various click actions (ex. navigate to URL).
  </Step>

  <Step title="Building Custom Reports">
    To view the specific action, project, flow, or step of a `navattic_event`, use [Event Parameters](https://support.google.com/analytics/answer/9216061?hl=en\&sjid=13083582562165458896-NA) in Google Analytics 4.

    | Navattic Event Trait                                                                                                                                                             | in GA           |
    | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- |
    | Project Name                                                                                                                                                                     | project\_\_name |
    | Flow Name                                                                                                                                                                        | flow\_\_name    |
    | Step Number                                                                                                                                                                      | step\_\_index   |
    | Event Name (View\_step, Start\_checklist, Navigate, etc.) See [Navattic events ](https://docs.navattic.com/tracking/navattic-js/subscribe-to-events#navattic-events) for a list. | type            |

    To build reports using these Event Parameters, you can create a [Custom Dimension](https://support.google.com/analytics/answer/10075209?hl=en\&sjid=13083582562165458896-NA) under the Custom Definitions section of Properties. Below is an example of a Custom Dimension for Navattic Projects.

    <Frame>
      <img alt="" />
    </Frame>

    <Tip>
      Tip: For the most helpful tracking, give each Demo and Flow an informative name. This will help organize your data in Google Analytics.
    </Tip>
  </Step>
</Steps>


# Google Tag Manager
Source: https://docs.navattic.com/tracking/navattic-js/subscribe-to-events/google-tag-manager

Integrate Navattic events with Google Tag Manager for flexible tracking configurations.

Follow these steps to integrate Navattic JS events with <img alt="GTM Logo" /> **Google Tag Manager**:

<Note>
  `navattic.onEvent` callbacks only fire when event tracking is enabled. If your site uses a cookie consent banner, configure [cookie tracking](/integrations/cookie-consent) so that events are only sent after consent is granted.
</Note>

<Steps>
  <Step title="Create and configure the Navattic JS tag">
    In Google Tag Manager, create a new tag:

    1. Go to **Tags** → **New** and name it "Navattic JS"
    2. Under **Tag Configuration**, select **Custom HTML**
    3. Navigate to Navattic Settings > [Navattic JS](https://app.navattic.com/u/settings/js) and copy the installation code
    4. Paste the code into the Custom HTML field

    <Frame>
      <img />
    </Frame>

    <Note>
      If you have **GA4 + Google Tag Manager integration** enabled in Navattic JS configuration, events will be automatically tracked. Otherwise, add this to your installation snippet:

      <Expandable title="push events to dataLayer">
        ```html theme={null}
        <script>
            navattic.onEvent(function(event){
                dataLayer.push({
                  event: "navattic_event",
                  data: navattic.flatten(event)
                });
            });
        </script>
        ```
      </Expandable>
    </Note>

    <Accordion title="View complete GTM tag code">
      ```html theme={null}
      <script>
          void 0 === window.navatticQueue &&
            ((window.navatticQueue = []),
            (window.navattic = new Proxy(
              {},
              {
                get: function n(t, u, e) {
                  return function () {
                    for (var n = arguments.length, t = Array(n), e = 0; e < n; e++)
                      t[e] = arguments[e];
                    return navatticQueue.push({ function: u, arguments: t });
                  };
                },
              }
            )));
      </script>
      <script async src="https://js.navattic.com/sdk.js?key=<your_key>"></script>
      <script>
          navattic.onEvent(function(event){
              dataLayer.push({
                event: "navattic_event",
                data: navattic.flatten(event)
              });
          });
      </script>
      ```
    </Accordion>

    5. Under **Triggering**, select **All Pages** or create a custom trigger for specific pages
    6. Click **Save**

    <Frame>
      <img alt="" />
    </Frame>
  </Step>

  <Step title="Create a custom event trigger">
    Set up a trigger to capture Navattic events:

    1. Go to **Triggers** → **New**
    2. Under **Trigger Configuration**, select **Custom Event**
    3. Set **Event name** to `navattic_event`
    4. Under **This trigger fires on**, select **Some Custom Events**
    5. Add condition: `{{Event}}` equals `navattic_event`
    6. Save the trigger

    <Frame>
      <img alt="" />
    </Frame>
  </Step>

  <Step title="Create data layer variables">
    Define variables for the below Navattic event fields:

    | Variable Name       | Type                | Data layer variable name |
    | ------------------- | ------------------- | ------------------------ |
    | Navattic event type | Data Layer Variable | data.type                |
    | Navattic demo name  | Data Layer Variable | data.project\_\_name     |
    | Navattic flow name  | Data Layer Variable | data.flow\_\_name        |
    | Navattic step name  | Data Layer Variable | data.step\_\_name        |

    1. Go to **Variables** → **User-Defined Variables** → **New**
    2. For each variable in the table above:
       * Set variable name
       * Set **Variable Type** to **Data Layer Variable**
       * Enter the corresponding data layer variable name (e.g., `data.type`, `data.project__name`)
    3. Save each variable

    <Frame>
      <img alt="" />
    </Frame>

    <Info>
      These variables will be used in the following step to make the Navattic event data accessible to your GA4 event tag.
    </Info>
  </Step>

  <Step title="Configure GA4 event tag">
    Create a tag to send Navattic events to GA4:

    1. Go to **Tags** → **New** and name it "Navattic event tag"
    2. Under **Tag Configuration**, select **Google Analytics: GA4 Event**
    3. Enter your **Measurement ID** for GA4
    4. Set **Event Name** to `navattic_engagement`
    5. Add **Event Parameters**:

    | Event Parameter   | Data layer variable name  |
    | ----------------- | ------------------------- |
    | navatticEventType | `{{Navattic event type}}` |
    | navatticDemoName  | `{{Navattic demo name}}`  |
    | navatticFlowName  | `{{Navattic flow name}}`  |
    | navatticStepName  | `{{Navattic step name}}`  |

    6. Under **Triggering**, select the custom event trigger from Step 2
    7. Save the tag

    <Frame>
      <img alt="" />
    </Frame>
  </Step>

  <Step title="Preview, test, and publish">
    Click "Preview" in Tag Manager and navigate to a page with a demo.

    When you engage with the demo, you should see "navattic\_event" and "navattic\_engagement" events with the variables we defined above populated with the correct values for your demo.
  </Step>
</Steps>


# HubSpot Forms
Source: https://docs.navattic.com/tracking/navattic-js/subscribe-to-events/hubspot-forms

Automatically populate HubSpot forms with visitor data from demo interactions.

<Note>
  As of May 2024, you can embed a Hubspot form directly. Learn more about adding a [Hubspot embed
  step](/flows#s-Gs6) .
</Note>

# Overview

This section covers how to use a HubSpot form to identify website Visitors who engage with your Navattic demo. This allows you to consolidate A) visitor data gathered by HubSpot with B) demo engagement data gathered by Navattic, and view the full data story in both platforms.

# Implementation

### Step 1: Create a HubSpot form and add this to the page hosting your Navattic demo iFrame

The first step is to create a HubSpot form and add this to the page hosting the Navattic demo iFrame. This will allow HubSpot to create HubSpot Contacts when visitors fill out the HubSpot form.

**Tips:**

* Here is [HubSpot documentation](https://developers.hubspot.com/docs/cms/building-blocks/forms) on how to embed a HubSpot form that disappears on submission.
* If it's not already added, be sure to enable the [HubSpot tracking code](https://knowledge.hubspot.com/reports/install-the-hubspot-tracking-code) across your site. The tracking code is automatically included on HubSpot blog pages, landing pages, and website pages.

### Step 2: Add the Navattic script to this same page

Copy the [Navattic JS](/tracking/navattic-js) snippet and add it below the header on the page hosting the Navattic demo embed (this is the same page from step 1). This JS snippet should be installed **after your existing third-party script tags.**

The Navattic script is used to send the website visitor's HubSpot Cookie to Navattic, which allows Navattic to send the demo engagement to the corresponding Hubspot Contact later in Step 4. This step does not allow HubSpot form fill data to enter Navattic.

### Step 3: Pass HubSpot form fill data into Navattic

<Note>
  This step is used to send Visitor data from your HubSpot form into Navattic so that Visitor emails are attached to the appropriate demo engagement data within the Navattic application.

  While highly recommended, this step is not necessary if your organization has privacy concerns with Visitor emails entering the Navattic platform.
</Note>

**Option 1:**

Enable the **Automatic Form Submission Tracking** feature in [Navattic JS](/tracking/navattic-js) to automatically send any identification information provided in the form to Navattic without requiring any additional JavaScript code.

**Option 2:**

If you require more flexibility about which fields get sent to Navattic, use the `navattic.identify` method to send the submitted form fields to Navattic.

The Navattic snippet gives you access to our `Identify` API (more [here](/analyze#sngew)). With this, You can call `window.navattic.identify` in your website code to pass in data to Navattic for things like email, name, company name, etc. To complete the form connection, have a website engineer use this API to pass the submitted form data into Navattic.

1. Any known UTMs (pulled from the parent page URL) will automatically be passed into Navattic via the `Identify` API
2. Since each HubSpot form can contain different field names, this step does require custom implementation from your team to call `window.navattic.identify`
3. Here is an example snippet that your team can build on:

```javascript theme={null}
// Sample Hubspot snippet that pulls in first name and email to Navattic

<script charset="utf-8" type="text/javascript" src="//js.hsforms.net/forms/embed/v2.js">
</script>

<script>
	hbspt.forms.create({
		region: "na1",
		portalId: "PORTAL_ID",
		formId: "FORM_ID",
		onFormSubmit: function($form) {
			console.log($form);
			$hs_fname = $form[0].fullName.value;
			$hs_email = $form[0].email.value;
			window.navattic.identify({
				'user.fullName': $hs_fname,
				'user.email': $hs_email
			})
		}
	});
</script>
```

### Step 4: Set up the direct Navattic HubSpot integration

You have completed the necessary steps for identifying Navattic Visitors using a HubSpot form! The last step is to [enable the HubSpot direct integration.](/integrations/hubspot)

This connects all the available demo engagement and visitor identification data to the corresponding HubSpot Contact.


# Subscribe to Events
Source: https://docs.navattic.com/tracking/navattic-js/subscribe-to-events/index

Connect to tracking scripts you already have installed.

Once you've [installed Navattic JS](/tracking/navattic-js#navattic-js-setup), you can connect to any tracking script you already have installed on pages with Navattic JS by **subscribing to events**.

<CardGroup>
  <Card title="Any tracking script" icon="code">
    <Expandable title="code">
      ```javascript theme={null}
      <script>
      navattic.onEvent(function(eventData){
          // Your custom tracking code here
      });
      </script>
      ```
    </Expandable>
  </Card>

  <Card title="Amplitude" icon={<img src="https://logo.navattic.com/amplitude.com" className="my-0 h-6 w-6" />}>
    <Expandable title="code">
      ```javascript theme={null}
      <script>
        navattic.onEvent(function(eventData){
          amplitude.track("navattic_event", eventData);
        });
      </script>
      ```
    </Expandable>
  </Card>

  <Card title="Mutiny" icon={<img src="https://mintcdn.com/navattic-app/sbomoyxYqCTZHNO1/images/integrations/mutiny.jpg?fit=max&auto=format&n=sbomoyxYqCTZHNO1&q=85&s=d9c73d21fdbf53f8d21a3cff6aee4ea5" className="my-0 h-6 w-6" />}>
    <Expandable title="code">
      ```javascript theme={null}
      <script>
        navattic.onEvent(function(eventData){
          mutiny.track("navattic_event", eventData);
        });
      </script>
      ```
    </Expandable>
  </Card>

  <Card title="Mixpanel" icon={<img src="https://mintcdn.com/navattic-app/2TSaKTXFRjfdIO0O/images/integrations/mixpanel.svg?fit=max&auto=format&n=2TSaKTXFRjfdIO0O&q=85&s=2150a1debf5251f2f5df2e16dd4cf29d" className="my-0 h-6 w-6" />}>
    <Expandable title="code">
      ```javascript theme={null}
      <script>
        navattic.onEvent(function(eventData){
          mixpanel.track("navattic_event", eventData);
        });
      </script>
      ```
    </Expandable>
  </Card>

  <Card title="Posthog" icon={<img src="https://logo.navattic.com/posthog.com" className="my-0 h-6 w-6" />}>
    <Expandable title="code">
      ```javascript theme={null}
      <script>
        navattic.onEvent(function(eventData){
          posthog.capture("navattic_event", eventData);
        });
      </script>
      ```
    </Expandable>
  </Card>

  <Card title="Segment" icon={<img src="https://www.navattic.com/img/integrations/logos/segment.png" className="my-0 h-6 w-6" />}>
    <Expandable title="code">
      ```javascript theme={null}
      <script>
        navattic.onEvent(function(eventData){
          analytics.track("navattic_event", eventData);
        });
      </script>
      ```
    </Expandable>
  </Card>

  <Card title="Adobe Analytics" icon={<img src="https://logo.navattic.com/adobe.com" className="my-0 h-6 w-6" />}>
    <Expandable title="code">
      ```javascript theme={null}
      <script>
        navattic.onEvent(function(eventData){
          s.tl(true, 'o', 'navattic_event', eventData);
        });
      </script>
      ```
    </Expandable>
  </Card>

  <Card title="Pendo" icon={<img src="https://logo.navattic.com/pendo.io" className="my-0 h-6 w-6" />}>
    <Expandable title="code">
      ```javascript theme={null}
      <script>
        navattic.onEvent(function(eventData){
          pendo.track("navattic_event", eventData);
        });
      </script>
      ```
    </Expandable>
  </Card>

  <Card title="Unify" icon={<img src="https://logo.navattic.com/unifygtm.com" className="my-0 h-6 w-6" />}>
    <Expandable title="code">
      ```javascript theme={null}
      <script>
        navattic.onEvent(function(eventData){
          unify.track("navattic_event", eventData);
        });
      </script>
      ```
    </Expandable>
  </Card>

  <Card title="Pocus" icon={<img src="https://logo.navattic.com/pocus.com" className="my-0 h-6 w-6" />}>
    <Expandable title="code">
      ```javascript theme={null}
      <script>
        navattic.onEvent(function(eventData){
          pocus.track("navattic_event", eventData);
        });
      </script>
      ```
    </Expandable>
  </Card>
</CardGroup>

<CardGroup>
  <Card title="Google Analytics" href="/tracking/navattic-js/subscribe-to-events/ga4" icon={<img src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/integrations/google-analytics.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=1e67de3105a3931e70a0a6d7848d397d" className="my-0 h-6 w-6" />}>Follow instructions for setting up GA4</Card>
  <Card title="Google Tag Manager" href="/tracking/navattic-js/subscribe-to-events/google-tag-manager" icon={<img src="https://www.svgrepo.com/show/353827/google-tag-manager.svg" className="my-0 h-6 w-6" />}>Follow instructions for setting up GTM</Card>
</CardGroup>

### Navattic Events

Event data for each Navattic Product Demo includes:

| **Event Name**    | **Description**                                                               |
| ----------------- | ----------------------------------------------------------------------------- |
| `VIEW_STEP`       | A Flow step is viewed.                                                        |
| `START_FLOW`      | A visitor starts a Flow.                                                      |
| `COMPLETE_FLOW`   | A visitor reached the last step of a flow OR completed a "Complete flow" step |
| `START_CHECKLIST` | A visitor loads a Checklist for the first time.                               |
| `OPEN_CHECKLIST`  | A visitor expands a Checklist.                                                |
| `CLOSE_CHECKLIST` | A visitor clicks "x" to close a Checklist or starts a flow.                   |
| `COMPLETE_TASK`   | A visitor completed a Task in a Checklist.                                    |
| `CONVERTED`       | A visitor completed a step tagged "Mark as converted".                        |
| `NAVIGATE`        | A visitor clicked a button with the click action "Navigate to URL".           |
| `IDENTIFY_USER`   | A form has been filled out in the demo that can identify the user.            |
| `ENGAGE`          | A visitor makes it past the first step of a flow.                             |

<Expandable title="full event shape">
  ```javascript theme={null}
  {
  	// event can be one of:
  	// - VIEW_STEP
  	// - START_FLOW
  	// - COMPLETE_FLOW
  	// - START_CHECKLIST
  	// - OPEN_CHECKLIST
  	// - CLOSE_CHECKLIST
  	// - IDENTIFY_USER
  	// - CONVERTED
  	// - NAVIGATE
  	// - COMPLETE_TASK
  	type: "VIEW_STEP",

    // Current project.
    project: {
       	id: "ID_OF_PROJECT",
       	name: "NAME_OF_PROJECT",
    },

    // Current flow.
    flow: {
       	id: "ID_OF_CURRENT_FLOW",
       	name: "NAME_OF_CURRENT_FLOW",
    },

    // Current step.
    step: {
       	name: "NAME_OF_CURRENT_STEP",
       	indx: 0, // Steps start counting at 0!
    },

    // NOTE: checklist can be undefined if the project
    // has no checklist.
    checklist: {
       	id: "ID_OF_CHECKLIST",
       	name: "NAME_OF_CHECKLIST",
    },

    // Current task (only defined if on checklist).
    task: {
        title: "TITLE_OF_TASK",
        id: "ID_OF_TASK",
    }

    // List of IDs of completed tasks.
    completions: ["...", "..."],

    // URL that the visitor clicked.
    // Only populated if event is NAVIGATE.
    url: "",

    // shows up at https://app.navattic.com/your-workspace/customers/{customerId}
    customerId: "ID_OF_CURRENT_VISITOR",

    // a session is scoped to a browser tab, so any action
    // performed in that tab is tied to a session
    sessionId: "ID_OF_CURRENT_SESSION",

    // Technical metadata about the user (ex: browser, device, etc).
    clientSideMetadata: ...,

    // Properties that have been identified from the user.
    properties: [{
        name: "NAME_OF_PROPERTY"

        // The object can be one of
        // - END_USER
        // - COMPANY_ACCOUNT
        object: "OBJECT_OF_PROPERTY"

        value: "VALUE_OF_PROPERTY"

        // The source can be one of
        // - FORM
        // - IDENTIFY
        // - QUERY_PARAMS
        // - SHARE_LINK
        // - PRESENTATION
        // - ENRICHMENT
        // - INTEGRATION
        // - OTHER
        source: "SOURCE_OF_PROPERTY_VALUE",

        // The capture method can be one of
        // - DEMO
        // - SCRIPT_AUTO
        // - SCRIPT_MANUAL
        // - INTEGRATION
        captureMethod: "CAPTURE_METHOD_OF_PROPERTY",


        // Form properties, if the property was identified from a form submission.
        form: {
        id: "ID_OF_FORM",
        versionId: "VERSION_ID_OF_FORM",
        Subscribe: "SUBMISSION_ID_OF_FORM",
        }
    }]
    projectShareLinkId: "ID_OF_PROJECT_SHARE_LINK"
    projectVersionId: "VERSION_ID_OF_PROJECT"
    projectLanguage: "LANGUAGE_CODE_OF_PROJECT"
  }
  ```
</Expandable>

Once the JS snippet is installed on your website, you should now see a new event named "navattic\_event" in your third-party platform.

<Tip>
  Tip: For the most helpful tracking, give each Demo and Flow an informative name. This will help
  organize your data in third-party platforms.
</Tip>


# Marketo Forms
Source: https://docs.navattic.com/tracking/navattic-js/subscribe-to-events/marketo-forms

Enhance Marketo forms with demo engagement data for better lead qualification.

<Note>
  As of May 2024, you can embed a Marketo form directly. Learn more about adding a [Marketo embed
  step](/flows#nonNy) .
</Note>

# Overview

This section covers how to use a Marketo form to identify website Visitors who engage with your Navattic demo. This allows you to consolidate A) visitor data gathered by Marketo with B) demo engagement data gathered by Navattic, and view the full data story in both platforms.

# Implementation

### Step 1: Create a Marketo form and add this to the page hosting your Navattic demo iFrame

The first step is to create a Marketo form and add this to the page hosting the Navattic demo iFrame. This will allow Marketo to create Marketo Leads when visitors fill out the Marketo form.

**Tips:**

* Here is [Marketo documentation](https://developers.marketo.com/blog/hide-lightbox-after-form-submission/) on how to embed a Marketo form that disappears on submission.
* If it's not already added, be sure to install the Marketo Munchkin tracking code onto the site. Here is [Marketo documentation](https://experienceleague.adobe.com/docs/marketo/using/product-docs/administration/additional-integrations/add-munchkin-tracking-code-to-your-website.html?lang=en) on how to find and install the tracking code.

### Step 2: Add the Navattic script to this same page

Copy the below Navattic snippet and add it below the header on the page hosting the Navattic demo embed (this is the same page from step 1). This JS snippet should be installed **after your existing third-party script tags.**

```javascript theme={null}
<script> window.navatticQueue=[],window.navattic=new Proxy({},{get:function n(t,u,e){return function(){for(var n=arguments.length,t=Array(n),e=0;e<n;e++)t[e]=arguments[e];return navatticQueue.push({function:u,arguments:t})}}}); </script> <script src="https://js.navattic.com/embed-events.js"></script>
```

The Navattic script is used to send the website visitor's Marketo Munchkin to Navattic, which allows Navattic to send the demo engagement to the corresponding Marketo Lead later in Step 4. This script does not allow Marketo form fill data to enter Navattic.

### Step 3: Pass Marketo form fill data into Navattic

<Note>
  This step is used to send visitor data from your Marketo form into Navattic, so that Visitor emails are attached to the appropriate demo engagement data within the Navattic Visitor's .

  While highly recommended, this step is not necessary if your organization has privacy concerns with visitor emails entering the Navattic platform.
</Note>

If you would like to pass Marketo form fill data into Navattic, the Navattic snippet gives you access to our `Identify` API (more [here](/analyze#sngew)). With this, You can call `window.navattic.identify` in your website code to pass in data to Navattic for things like email, name, company name, etc. To complete the form connection, have a website engineer use this API to pass the submitted form data into Navattic.

1. Any known UTMs (pulled from the parent page URL) will automatically be passed into Navattic via the `Identify` API
2. Since each Marketo form can contain different field names, this step does require custom implementation from your team to call `window.navattic.identify`
3. Here is an example snippet that your team can build on:

```javascript theme={null}
// Sample Marketo snippet that pulls in first name and email to Navattic

<script src="//app-xyz.marketo.com/js/forms2/js/forms2.js"></script>
<form id="mktoForm_###"></form>

<script>
MktoForms2.loadForm("//app-xyz.marketo.com", "###-####-####", ###, function(form) {
	form.onSuccess(function(){
		var vals = form.vals();
			window.navattic.identify({
				'user.firstname': vals.first_name,
				'user.email': vals.email
			});
	});
});
</script>
```

### Step 4: Set up the direct Navattic Marketo integration

You have completed the necessary steps for identifying Navattic Visitors using a Marketo form! The last step is to [enable the Marketo direct integration](/integrations/marketo).

This connects all the available demo engagement and visitor identification data to the corresponding Marketo Lead.


# 6sense
Source: https://docs.navattic.com/tracking/tracking-scripts/6sense

Add 6sense web tags to track anonymous demo visitors and identify buying signals.

Adding a **6sense** tracking script to your Navattic demos will allow you to add the 6sense Web Tag to your demo.

### Add 6Sense to your demos

Follow these steps to add 6Sense tracking to your Navattic demos:

<Steps>
  <Step title="Create a new Web Tag identified in 6sense">
    It should look something like this:

    ```html theme={null}
    <script id="6senseWebTag" src="https://j.6sc.co/j/<web_tag_id>.js"></script>
    ```
  </Step>

  <Step title="Add your 6sense Web Tag ID to Navattic Demos">
    Visit your **Navattic demo** > click the three dots next to the Share button > **Tracking
    scripts**. Paste your JavaScript Snippet into the input field. You do not need to publish your
    demo for the changes to take effect.
  </Step>

  <Step title="See page views and button clicks in 6Sense">
    You should start to see your demo visitor engagement show up in 6Sense as page views and button clicks.
  </Step>
</Steps>


# Demandbase
Source: https://docs.navattic.com/tracking/tracking-scripts/demandbase

Add the Demandbase script to track anonymous demo visitors and account activity.

Use a **Demandbase** tracking script to load the Demandbase tag on your Navattic demos.

### Add Demandbase to your demos

Follow these steps to add Demandbase tracking to your Navattic demos:

<Steps>
  <Step title="Get your Demandbase key">
    Demandbase keys are 16-character hex strings, such as `162a6962a6a8177c`.
  </Step>

  <Step title="Add the Demandbase script in Navattic">
    Visit your **Navattic demo** > click the three dots next to the Share button > **Tracking scripts**.
    Paste this snippet into the input field:

    ```html theme={null}
    <script src="https://tag.demandbase.com/<demandbase_key>.min.js"></script>
    ```

    You do not need to publish your demo for the change to take effect.
  </Step>

  <Step title="Validate tracking in Demandbase">
    Open the demo and confirm page views and engagement activity appear in Demandbase.
  </Step>
</Steps>


# Drift
Source: https://docs.navattic.com/tracking/tracking-scripts/drift

Add a chat widget for real-time customer conversations.

Adding a **Drift** script to your Navattic demos will allow the Drift chat widget to pop up in your Navattic demo. This allows your team to chat with customers as they view the demo.

### Add a Drift chat widget to your demos

Follow these steps to add Drift to your Navattic demos:

<Steps>
  <Step title="Locate your Drift Script Key">
    To enable this tracking script, you'll need to find your Drift Script Key. To find this, log into Drift > go to Settings > App Settings > Drift Widget > and expand the JavaScript section under Install. Find your Drift Script Key as shown highlighted below.

    <img alt="" />
  </Step>

  <Step title="Add your Drift Script Key to Navattic Demos">
    Visit your **Navattic demo** > click the three dots next to the Share button > **Tracking
    scripts**. Paste your Drift Script Key into the Drift input field. Once the Drift key is added,
    publish your demo in Navattic.
  </Step>

  <Step title="Hold Conversations in Drift">
    Drift will automatically pop up inside the demo, and viewers can hold conversations with your team from inside.

    * These conversations will show up in the "Conversations" tab of Drift.
    * These conversations will use the demo URL as the URL.

    <Frame>
      <img alt="" />
    </Frame>
  </Step>
</Steps>


# Tracking scripts
Source: https://docs.navattic.com/tracking/tracking-scripts/index

Add third-party tracking scripts to your demos.

<Icon icon="activity" /> **Tracking Scripts** can be enabled on individual Navattic demos to track
things like session recordings, demo engagement, as well allow chat or calendar widgets to be
included within the demo. These scripts run on directly on your demo and send data directly to a
third-party platform.

You can enable Tracking Scripts on any demo in just a few clicks. Visit your **Navattic demo** > click the three dots next to the Share button > **Tracking scripts** > add the appropriate ID.

<CardGroup>
  <Card icon={<img src="https://logo.navattic.com/6sense.com" className="my-0 h-6 w-6" />} title="6sense" href="/tracking/tracking-scripts/6sense">
    Track visitor engagement as page views and clicks.
  </Card>

  <Card icon={<img src="https://logo.navattic.com/demandbase.com" className="my-0 h-6 w-6" />} title="Demandbase" href="/tracking/tracking-scripts/demandbase">
    Track account-level engagement and buyer intent activity.
  </Card>

  <Card icon={<img src="https://logo.navattic.com/drift.com" className="my-0 h-6 w-6" />} title="Drift" href="/tracking/tracking-scripts/drift">
    Add chat widget for real-time customer conversations.
  </Card>

  <Card
    icon={
  <img
    src="https://mintcdn.com/navattic-app/CaLa6x42vs1NHRL9/images/integrations/hubspot.svg?fit=max&auto=format&n=CaLa6x42vs1NHRL9&q=85&s=82b201671090d1c88fc8ebea2e90edb0"
    className="my-0 h-6 w-6"
  />
}
    title="HubSpot JS"
    href="/tracking/tracking-scripts/hubspot"
  >
    Integrate demo engagement with HubSpot CRM.
  </Card>

  <Card
    icon={
  <img
    src="https://www.navattic.com/img/integrations/logos/marketo.png"
    className="my-0 h-6 w-6"
  />
}
    title="Marketo Munchkin"
    href="/tracking/tracking-scripts/marketo"
  >
    Track demo interactions in Marketo campaigns.
  </Card>

  <Card icon={<img src="https://logo.navattic.com/posthog.com" className="my-0 h-6 w-6" />} title="PostHog" href="/tracking/tracking-scripts/posthog">
    Analyze demo usage with product analytics.
  </Card>

  <Card icon={<img src="https://logo.navattic.com/qualified.com" className="my-0 h-6 w-6" />} title="Qualified" href="/tracking/tracking-scripts/qualified">
    Deploy chatbots for automated demo engagement.
  </Card>
</CardGroup>


# Qualified
Source: https://docs.navattic.com/tracking/tracking-scripts/qualified

Deploy chatbots for automated demo engagement.

Adding a **Qualified** tracking script to your Navattic demos will allow you to add Qualified chatbots to your demo.

### Add Qualified to your demos

Follow these steps to add a Qualified chatbot to your Navattic demos:

<Steps>
  <Step title="Locate your Qualified JavaScript Snippet">
    To enable this tracking script, you'll need to find your Qualified "[JavaScript Snippet](https://www.qualified.com/university/articles/qualified-setup/installing-the-javascript)". To find this, log into Qualified > go to "Settings > Setup > copy your "JavaScript Snippet". Find your Qualified Script Snippet as shown highlighted below. The script needed is between token= and ".

    <img alt="" />
  </Step>

  <Step title="Add your Qualified JavaScript Snippet to Navattic Demos">
    Visit your **Navattic demo** > click the three dots next to the Share button > **Tracking
    scripts**. Paste your JavaScript Snippet into the Qualified input field. Once the Qualified
    Snippet is added, publish your demo in Navattic.
  </Step>

  <Step title="See Qualified Directly in your Demo">
    Qualified's chatbots will automatically pop up inside the demo. Demo visitors can interact with the chatbot anytime.

    * These conversations will appear in your Qualified dashboard.

    <Frame>
      <img alt="" />
    </Frame>
  </Step>
</Steps>


# Academy demos
Source: https://docs.navattic.com/use-cases/academy

Use interactive demos in Academies to help customers master essential workflows or train on advanced features.

<Icon icon="graduation-cap" /> **Academy demos** are a great way to activate new users and educate existing customers.

At Navattic, we recently launched the [Navattic Academy](https://academy.navattic.com/), which uses demos throughout. Here is a behind-the-scenes demo of how we set up Navattic and Thinkific (our LMS) to create engaging content.

Keep in mind that demos can support your internal team's enablement efforts, too.

### Recommendations

For training purposes, we recommend:

* **Keep demos digestible**: Break content into Flows of 5–8 steps each.
* **Use a** [checklist](https://docs.navattic.com/build#AIJEa) or demonstrate multiple workflows to showcase important features.
* **Introduce early**: Add demo onboarding via in-app chat or onboarding resources to support different learning styles.
* **Provide immediate value**: Keep demos ungated so customers can access them right away.
* **Use demos for variety**: Reinforce information across formats (text, video, demo) to support different learners.
* **Keep lessons engaging**: Replace long text or “reading lessons” with interactive demos when possible.
* **Embed effectively**: Scale Width is usually the best responsiveness strategy (most platforms display iframes at 50–80% of the screen).

### Implementation Guide

Follow the guidance below to create training demos that will drive product adoption and usage across your existing customer base. Remember to check the [Analytics](http://localhost:3000/analyze#analytics-dashboard) to view drop-offs for each step and use that data to continue improving your demo.

<Steps>
  <Step title="Structure">
    **Starting Flow:** Start with a goal-oriented introduction to the training module (ex. "Take the Navattic Crash Course to see how to create a demo, view visitor data, and invite your teammates.")

    **Checklist:** Include a Checklist to help users find the content that is most relevant to them. Make sure each Checklist task includes a clear goal-oriented description, just like your starting flow. Isolate your most essential workflows to help users get activated ASAP.

    **Navigation:** It's important to make your onboarding resources as user-friendly as possible. Turn on Navigation Buttons in your [Flow Settings](https://demo-staging.navattic.com/docs) to help first-time users navigate smoothly throughout your demo. Consider adding a Progress Bar to your [Theme](https://docs.navattic.com/themes), to help users view their progress and manage their time.

    <Info>
      Use a training demo to excite users about the product solutions **they are about to unlock**. No need to show every single click or feature in your onboarding demo, as users will likely have access to your product already.
    </Info>
  </Step>

  <Step title="CTAs">
    **Consider your audience and get creative**: Use the appropriate CTA for each part of the customer journey. Consider linking to a:

    * Knowledge base
    * Webinar registration page
    * Product feedback form
    * Pricing page for additional features

    **Existing users may have some product familiarity already and be ready to skip ahead.** Turn on [**Escape View**](https://training.navattic.com/7429hwxgx) to make your demo CTAs accessible at any time.
  </Step>

  <Step title="Deployment">
    To locate your embed code in Navattic, locate your demo > click **Share** > select **Website Embed** > choose **Inline embed** > select **Get embed code.**

    <Tip>
      Use [query strings](https://docs.navattic.com/tracking/identify/visitors#assisted-entry-of-query-strings) with LMS parameters to help identify visitors who visit your LMS.
    </Tip>

    For step-by-step instructions on embedding a demo in your LMS, see the links below:

    <CardGroup>
      <Card title="Thinkific" icon={<img src="https://logo.navattic.com/thinkific.com" className="my-0 h-6 w-6" />} href="https://support.thinkific.com/hc/en-us/articles/360030739873-Create-a-Multimedia-Lesson#externallyhosted" />

      <Card title="WorkRamp" icon={<img src="https://logo.navattic.com/workramp.com" className="my-0 h-6 w-6" />} href="https://help.workramp.com/en/articles/5225918-using-the-embed-object" />

      <Card title="Rise360" icon={<img src="https://logo.navattic.com/articulate.com" className="my-0 h-6 w-6" />} href="https://community.articulate.com/blog/tips-tricks/how-to-embed-multimedia--web-content-in-rise-360/1215507" />

      <Card title="SkillJar" icon={<img src="https://logo.navattic.com/skilljar.com" className="my-0 h-6 w-6" />} href="https://support.skilljar.com/hc/en-us/articles/38190341601677-Embed-Content-in-a-Lesson" />
    </CardGroup>
  </Step>

  <Step title="Maintenance">
    Navattic demos are easy to update, even after they have been **Published** and shared with your customers. No need to re-record a training video every time there is a UI update in your product.

    When it is time to update your demo, simply edit the associated Captures, Flows, or Checklists and click "**Publish**". This will push changes directly to all instances of this demo that has been shared or embedded without having to update the embed code.

    Replace outdated Captures at any time without impacting the rest of your demo.
  </Step>
</Steps>

## Customer Interview Series

See how JumpCloud uses Navattic to **transform their product education strategy** from non-interactive simulations to dynamic, no-code interactive demos: [**Customer Show + Tell: Educational Product Courses with Nikki Stubbs**](https://www.navattic.com/blog/customer-interview-series-educational-product-courses-with-nikki-stubbs)


# Conferences
Source: https://docs.navattic.com/use-cases/conferences

Stand out at trade shows and conferences with interactive demos that prospects can explore.

<CustomerQuote name="Equus" />

Stand out at <Icon icon="users" /> **Conferences** events by providing immediate access to your product. Use an interactive demo to tell a streamlined and engaging user story and share your mobile accessible project link afterwards - customers are sure to ask for it!

# Customer Examples

Below are some conference demos we love. Keep an eye out for:

* Interactivity: How memorable is this on-site experience?
* Navigation and ease-of-use: Can a first-time user find their way through the demo?
* Integrations: How does your product fit seamlessly into existing workflows?

<CardGroup>
  <Card title="Xello: Educator Tools" href="https://xello.navattic.com/docs-example" />

  <Card title="Navattic: Try it out" href="https://www.navattic.com/" />

  <Card title="Nuvolo: Optimise your Workplace" href="https://nuvolo.navattic.com/el4d0pvj" />

  <Card title="Nuvolo: Fix Today, Plan for Tomorrow" href="https://nuvolo.navattic.com/8xh06zk?g=cmf2dr8ir000b04jremmm5tg2&s=0" />
</CardGroup>

***

# Implementation Guide

Use the guidance below to maximize engagement at your conference booth. We recommend providing desktops or laptops for participants to engage with, although iPads and mobile devices are also supported.

<Steps>
  <Step title="Content">
    **Make it memorable**: Aim for a 2-3 minute memorable experience that will demonstrate the wow moments of your product

    **Make it interactive**: Use tooltips, triggers, and beacons to let viewers envision using your product in their day to day

    **Customize it for your audience**: Incorporate the theme of the conference throughout your demo by using custom Themes or uploading images.
  </Step>

  <Step title="Navigation">
    **Keep text minimal**: The product demo will likely support organic conversations that are already taking place at the booth. Smaller dialog boxes will also take up less space on mobile devices like iPads or smartphones, leaving more space for your product to shine.

    **Use backdrops**: Conference attendees may be seeing your product for the first time ever. Using backdrops alongside tooltips will help attendees find the most important areas of your product.

    **Consider a Checklist**: Allow interested viewers to explore multiple features in-depth while keeping the intro demo short.
  </Step>

  <Step title="Accessibility">
    **Make it accessible**: Optimize demos for viewing on a variety of devices. Include a QR code at your booth to send viewers directly to your demo.

    **Enable internal champions**: Share your demo afterwards to ensure engaged attendees are able to continue selling your product internally.

    **Track engagement**: Create a conference-specific project link to separate engagement data from multiple events.
  </Step>

  <Step title="Booth Setup">
    Below are a few tried and true conference setups. Reach out to [team@navattic.com](mailto:team@navattic.com) for tips on how to optimize your specific setup.

    * TV connected to a laptop or desktop to expand the reach of your demo
    * Multiple iPads for asynchronous learning
    * Kiosks equipped with an iPad or laptop
  </Step>

  <Step title="Tracking Visitors">
    Below are a few tips for individualized visitor tracking on shared devices:

    1. Present the demo in an incognito browser and reload the tab each time there's a new Visitor
    2. To maximize identification opportunities, add an optional Form with an email field at the start of the demo. Learn more about [Forms](/tracking/forms/index).
    3. To ensure the demo progresses smoothly, incorporate a [Timer Trigger](https://docs.navattic.com/build/flows#timer-trigger) to each step after Step 1. For instance, you could add a 2-minute Timer Trigger with the "Continue" action. Additionally, on the last step, include a button that uses the "Navigate to URL" action. This button should link to the demo and open in the same tab, automatically refreshing the window. This will end the current visitor's session and start a new session for the next visitor, effectively resetting the time tracking.
  </Step>
</Steps>

***

# Supporting Mobile Devices

It is important for conference demos to be supported on multiple end-user devices including laptops, tablets, and smartphones. Below are our tips for maximizing accessibility across devices.

<Steps>
  <Step title="Take Captures">
    If you know the conference devices you will have access to beforehand, try to take Captures at these dimensions. If you are uncertain of the devices, we recommend resizing your browser window to about 1440 x 900px when taking Captures for your demo. This is the "standard laptop size" that will scale up and down accordingly on most end-user devices.

    <Warning>
      **Note**: Avoid taking Captures on widescreen monitors as these may not scale well on mobile
      devices.
    </Warning>
  </Step>

  <Step title="Set your Mobile Strategy">
    <MediaCard type="demo" title="Conferences" />

    Keep in mind that demos will appear differently on mobile devices with a width below 800px. This includes iPad minis in portrait mode as well as most smartphones. For reference, here is an [index](https://screensiz.es/) of various device screen sizes.

    **Navattic includes four main options for mobile viewers:**

    1. Mobile zoom (default) serves the desktop demo with pinch-to-zoom enabled
    2. Mobile swipe demo is used to engage your mobile visitors with a short and visual experience they can *swipe* through
    3. Mobile scaled view presents a scaled down version of your demo
    4. Mobile alert presents a message that asks the visitor to return on a larger device

    To set your mobile strategy, access your demo > select **Mobile** > and select an option.

    <img />
  </Step>

  <Step title="Preview Demos">
    If possible, preview your demo across various devices beforehand. An extension like [this mobile simulator](https://chrome.google.com/webstore/detail/mobile-simulator-responsi/ckejmhbmlajgoklhgbapkiccekfoccmk/related) can help simulate different device dimensions, even if you do not have access to the conference devices just yet.

    **Here is how the Mobile swipe demo will appear on devices below 800px wide:**

    <img alt="" />

    **Here is how demos with Mobile scaled view appear on various devices.**

    <img alt="" />

    <img />

    <img />
  </Step>
</Steps>


# Demo center
Source: https://docs.navattic.com/use-cases/demo-center

Create a centralized hub for all your product demos to drive self-service exploration.

<CustomerQuote name="Accord" />

Equip your sales team with a <Icon icon="layout-grid" /> **Demo Center** to engage prospects at every step of the journey. Turn prospects into internal champions by encouraging them to share the Demo Center widely.

These demos often have a more limited scope than [Website Overview](/use-cases/website-demos) demos and include detailed walkthroughs of specific use cases.

<Note>
  **Blog**: Read [Implementing Interactive Demos for Multiple Product Lines](https://www.navattic.com/blog/interactive-demo-enterprise) to see how enterprise customers demo a variety of use cases.
</Note>

# Customer Examples

Below are some customer examples we love. Keep an eye out for:

* Ability to tag and filter demos by use case or persona
* Interactivity and ease-of-use
* Ungated experiences
* Consistent CTAs

<CardGroup>
  <Card title="Fivetran: Demo Center" href="https://resources.fivetran.com/demo-center" />

  <Card title="Digital Ocean: Product Tours" href="https://www.digitalocean.com/product-tours" />

  <Card title="Absolute: Interactive product and feature tours" href="https://www.absolute.com/platform/product-tours" />

  <Card title="Vitally Academy" href="https://www.vitally.io/academy#interactive-product-tours" />

  <Card title="Cvent: Interactive Demo Library" href="https://www.cvent.com/en/interactive-demo-library" />

  <Card title="UserEvidence: Demo Ranch" href="https://userevidence.com/demo-ranch/" />

  <Card title="Airbyte: Explore key features" href="https://airbyte.com/interactive-demo" />
</CardGroup>

# Implementation Guide

Use the guidance below to launch a Demo Center in no time! Use [Project Analytics](/analyze) to identify your most engaging demos and explore an [integration](/integrations) to quickly synthesize events data.

<Steps>
  <Step title="Content">
    **Focus on value**: Aim for 8-15 steps that educate viewers on the impact of a specific solution and the pain point it addresses.

    **Consider your audience**: Demo Centers are great champion enablement assets. What are questions your champions are likely to receive internally, and how can your demo get ahead of common stakeholder concerns?

    **Showcase integrations**: Demo your product's integrations or features that usually require expert guidance. Navattic demos can combine captures from multiple collections or platforms - no need to switch between different apps.
  </Step>

  <Step title="CTAs">
    **Be direct**: Include a single CTA that reinforces the next step in your sales process.

    **See conversions**: Consider embedding your demo on a landing page and [integrating with Google Analytics 4](/google-analytics-ga4) to combine Navattic engagement with your website event data.
  </Step>

  <Step title="Deployment">
    **Provide options**: Organize demos for various features or buyer personas. Include a short blurb to help viewers identify the experience that is most relevant to them

    **Try ungating**: Only a small portion of websites offer Demo Centers today. A Demo Center of any kind is likely to be an advantage over competitors. Consider ungating the page to allow internal champions to circulate this widely.

    <img alt="" />
  </Step>

  <Step title="Recommended Structure">
    **Steps 1-2**: Set the stage for your demo. What problem does this feature solve, when is it used, and who uses it?

    **Steps 3-9**: Use Tooltips, Beacons, and Triggers to create an interactive experience. Keep navigation minimal to demonstrate how seamless this feature is to use.

    **Steps 10-12**: What is the next step for qualified prospects? Conclude your demo with 1 direct CTA or route visitors back to your Demo Center landing page.
  </Step>
</Steps>

### Customer Interview Series

See how Demandbase uses Navattic as the foundation for their interactive demo library. Read about their strategy in the blog: [Customer Interview Series: Demo Library with Tara Quehl](https://www.navattic.com/blog/customer-interview-series-demo-libraries-with-tara-quehl)


# Feature highlights
Source: https://docs.navattic.com/use-cases/feature-highlights

Showcase specific features with focused, interactive product demos.

<CustomerQuote name="Dooly" />

<Icon icon="square-dashed-mouse-pointer" /> **Feature highlight** demos are used to educate prospects and drive more qualified sales conversations. These demos usually have a narrower scope than [Website demos](/use-cases/website-demos), and include more detailed walkthroughs of specific use cases, competitive features, or technical product areas like integrations. Embed feature demos on product landing pages or in your marketing outreach.

### Recommendations

For feature-specific demos, we recommend:

* Keep your demo short (8-15 steps) to quickly show the "wow" moment of that feature
* If your demo is embedded on a landing page, consider an ungated experience (without a form at the beginning)
* Maintain consistent CTAs across each of the feature-specific demos

<Info>
  **Blog**: Read [6 Feature Announcement Examples from SaaS Companies](https://www.navattic.com/blog/feature-announcements-examples-from-saas-companies) to see how other customers promote feature demos.
</Info>

### Feature Highlights Customer Examples

Below are some customer examples we love. Keep an eye out for the recommendations highlighted above.

<CardGroup>
  <Card title="Udemy: Udemy business" href="https://business.udemy.com/product-tour/" />

  <Card title="Datadog: Turn Security into a Team Sport" href="https://www.datadoghq.com/guided-tour/security/" />

  <Card title="Payhawk: Sage Intacct Native Integration" href="https://payhawk.navattic.com/xi4l0t6f" />
</CardGroup>

### Implementation Guide

Follow the guidance below to launch feature demos in no time. Use [Navattic Analytics](/analyze) to assess completion rates (tip: from your Analytics page, select **Compare All Demos** to view engagement and conversion across all of your demos).

<Steps>
  <Step title="Content">
    **Focus on the problem**: Aim for 8-15 steps that highlights the problem a specific feature or use case solves. Skip "how-to" style navigation in favor of value-driven storytelling.

    <img alt="Section Length vs Average Completion Rate" />

    **Make it interactive**: Use tooltips, timer triggers, beacons, and text animation to help visitors envision using this feature in their day to day. \*\*Tip: \*\*for a video-like experience, consider coupling voiceover with timer triggers to create a more automated experience.

    **Skip to the tough stuff**: Use a demo to showcase your product's integrations or features that usually require expert guidance. Let viewers skip the setup and explore integrations at their own pace.
  </Step>

  <Step title="CTAs">
    **Be direct and consistent**: Include a single CTA at the end of the demo that pushes qualified prospects to a sales-led demo, free trial, or gated asset.

    <Note>
      **Tip:** Common conversion CTAs are "Sign up free", "Book a demo", and "Get in touch"
    </Note>
  </Step>

  <Step title="Deployment">
    **Provide options**: Organize demos for various features or buyer personas, or use a checklist to present a list of options (ex. [Navattic: What's New?](https://navattic-docs.navattic.com/y6lv0ayb)). Include a short blurb under each checklist item to help viewers identify the experience that is most relevant to them

    **Try ungating**: Remember, feature demos are used to qualify prospects and to set the stage for more in-depth sales conversations. If gating your demo, enable the Form Setting "Skip if already submitted" to reduce friction for returning visitors.
  </Step>

  <Step title="Recommended Structure">
    **Steps 1-2**: Share the context for your feature. What does this feature do? When is it used? ([Klue's Triage Mode demo](https://klue.com/blog/introducing-triage-mode?utm_campaign=triage%20mode\&utm_source=linkedin\&utm_medium=social\&utm_content=employees#navatic-iframe) is a great example)

    **Steps 3-9:** Use Tooltips, Beacons, and Triggers to create an interactive experience. Keep text minimal to keep the focus on your product - demonstrate how easy and foolproof this feature is to use.

    **Steps 10-12:** What is the next step for qualified prospects? Conclude your demo with 1 direct CTA that is consisent across all feature demos.
  </Step>
</Steps>

## Tip: Drive middle-of-funnel engagement with a Demo Center

For website visitors that already know of your product, centralizing product demos is an effective way to drive site engagement. Include demos of new features or competitive differentiators and try organizing demos by use case or persona to connect prospects with the most relevant content.

**Consider a demo center when you have:**

* Multiple feature demos targeting the same **persona**
* Features that work together to support specific **use cases**
* Demo booths at **in person events** where prospects can explore independently

### Customer Examples

Below are some customer examples we love.

<CardGroup>
  <Card title="Digital Ocean: Product Tours" href="https://www.digitalocean.com/product-tours" />

  <Card title="Vitally Academy" href="https://www.vitally.io/academy#interactive-product-tours" />

  <Card title="Cvent: Interactive Demo Library" href="https://www.cvent.com/en/interactive-demo-library" />

  <Card title="Klue: Demo Arena" href="https://klue.com/demo-arena" />

  <Card title="UserEvidence: Demo Ranch" href="https://userevidence.com/demo-ranch/" />
</CardGroup>

### Customer Interview Series

1. See how **Klue** leverages Navattic for new feature announcements. Read about their strategy in the blog: [Customer Interview Series: Integration Enablement with Jason Oakley](https://www.navattic.com/blog/customer-interview-jason-oakley)

<MediaCard type="video" title="Feature Highlights" />


# In-app demos
Source: https://docs.navattic.com/use-cases/in-app-demos

Embed demos directly within your application for contextual user guidance.

<Icon icon="dock" /> **In-app demos** are used to boost new user activation rates for your app or a
newly launched feature by delivering value as soon as possible.

Similar to [Feature Highlights](/use-cases/feature-highlights), these demos enable and motivate users to adopt best practices and discover aha moments with minimal friction.Lastly, since demos are no-code to create, you can iterate based on demo completion data and experiment quickly with new ways of activating users.

<img alt="" />

# Recommendations

For a Free Trial, Freemium, or newly onboarded audience, we recommend:

* Keep your flows short (5-8 steps) to ensure new users are not overwhelmed by your product.
* Showcase related areas of your product by using a checklist that connects multiple flows. The benefits of this strategy are two-fold: Users stay motivated by their progress as they check off items on the list and users know exactly where they paused their progress should their learning be disrupted.
* Remember to include the why behind your ‘how to’ steps. If users understand the process, they are more likely to fully adopt your recommendations.
* Include CTA buttons that direct users to additional resources like docs or give users the opportunity to book time with a Customer Success Manager if they need further assistance.

<Note>
  **Blog**: Read

  <a href="https://www.navattic.com/blog/feature-announcements-examples-from-saas-companies">
    6 Feature Announcement Examples from SaaS Companies
  </a>

  to see how other customers promote feature demos.
</Note>

# Customer Examples

Below are some customer deployments we love. Keep an eye out for the recommendations highlighted above.

**1. Datadog**

To support the learning styles of all their users, Datadog offers multiple ways to get started with their product. Once users log in, they can dive straight in, watch a tutorial, or access a guided tour. Users simply click “See a Guided Tour” which takes them to a full-screen landing page with an [interactive demo](https://datadog.navattic.com/hq7w0l17).

![](https://archbee-image-uploads.s3.amazonaws.com/YYk8JOCMmxT-GPN-0CkK6/qwmgtG6XTZLG7ZTa3CoUG_untitled-13.png "Click \"See a Guided Tour\" to start a demo")

**2. MonitorQA**

To support new users exploring their product for the first time, the Monitor QA team triggers an exit intent pop up when a user is inactive for a certain period of time. Enabling slow-to-start users with their product demo that clarifies the set up process and showcases key product features prevents users from dropping off before they’ve seen value.

<img alt="" />

**3. Matillion**

To enable new users who need extra guidance, the Matillion team offers their users a choice — go through a product tour or jump right into using the tool. They use a checklist to give users a ‘choose your own adventure’ experience where they can navigate through the tour chronologically or explore based on functionalities that most interest them.

<img alt="" />

<img alt="" />

**4. Navattic**

To increase awareness and adoption of our new Account based engagement feature, our team created an in-app pop up that links out to a [feature specific demo](https://navattic-website.navattic.com/il1vk0u1h). Anyone who clicks on our new ‘Accounts’ tab has the opportunity to learn more about the feature via the interactive demo.

<img alt="" />

***

# Implementation Guide

Follow the guidance below to start optimizing your activation rates with customizable demos. Demos built with these best practices deliver value early to users. Keep an eye on your demo analytics to track completion rates and consider revising any steps with significant drop off rates.

## 1. Content

**Bundle essential workflows with a checklist**: Include a checklist with flows that are chronological or focus on a shared product area. Add goal-oriented descriptions to each item on your checklist to help users find the content that is most relevant to them.
**Make it interactive**: Use tooltips, triggers, and beacons to let viewers experience using this feature or envision how to integrate it in their day-to-day
**Focus on a goal**: Activate users early on by presenting a value-driven **5-10 step flow** that help users achieve enablement milestones.<img alt="Section Length vs Average Completion Rate" />

## 2. CTAs

Keep your audience in mind and be strategic. Create CTAs that are specific to each part of the user or trial customer journey. For instance, consider linking to a:

* Call booking page for your sales or support team
* Knowledge base
* Webinar registration page
* Product feedback form
* Pricing page for additional features

## 3. Deployment

**Add product tours to email onboarding sequences (easy)**: Optimize your existing email sequences by including a Product Demo. Consider making multiple demos that highlight your most essential features to help new users experience aha moments early on.

**Present demos through an in-app chat that is only accessible to users of your product (medium)**: Empower new users through a short demo in your FAQ snippets to resolve common mishaps while customers wait to chat with a representative.

<img />

**Add an interactive demo as an exit intent pop up (medium)**: Activate users who are unsure where to start by setting an exit intent pop up to appear after a certain amount of inactivity passes.

<img alt="" />

**Include demos in your product onboarding experience (advanced)**: Support all new users with in-product demos that users can choose to explore before they dive in to your product. We recommend using our [Navattic-Chameleon integration](https://www.chameleon.io/integrations/navattic) to show-case in-app interactive demos from any prebuilt Chameleon Experience.

<img alt="" />

## 4. Maintenance

Whether you embed your demo in app, share it via an exit intent pop-up, or send it via your onboarding sequences, you can easily sync updates to live demos. No need to re-record an onboarding video or revise your email templates every time this is a UI update in your product.

Whenever you need to revise your Product Demo, make your edits with the associated Captures, Flows, or Checklists and click “Publish”. This will automatically push the revised version out to all instances of your Product demo that have been shared or embedded.

Just need to replace a few captures? Easily do so without impacting the rest of your demo:

<MediaCard type="video" title="In Product Demos" />


# Navattic Use Cases
Source: https://docs.navattic.com/use-cases/index

Create demos that delight at every stage of the customer journey.

Create demos that support every stage of your customer journey. Explore detailed Implementation Guides and best practices for each of these common use cases.

### Marketing

Use interactive demos to capture interest and convert more visitors at the earliest stages of the funnel. Whether you're showcasing a product overview or launching new features, interactive demos help visitors understand your value—before signing up or talking to sales.

<CardGroup>
  <Card icon="panels-top-left" title="Website Overview" href="/use-cases/website-demos">
    Give website visitors a preview of your product with a **Try a demo** CTA.
  </Card>

  <Card icon="square-dashed-mouse-pointer" title="Feature Highlights" href="/use-cases/feature-highlights">
    Launch new features or share existing integrations.
  </Card>

  <Card icon="users" title="Conferences" href="/use-cases/conferences">
    Create standout booth experiences with shareable demos.
  </Card>

  <Card icon="layout-grid" title="Demo Center" href="/use-cases/demo-center">
    Equip sales teams with demos for every journey stage.
  </Card>
</CardGroup>

### Sales

Use demos to support your sales team at every stage of the deal cycle. From outbound outreach to conference booths and post-call leave-behinds, Navattic makes it easy to deliver consistent, compelling product experiences that drive conversations forward.

<CardGroup>
  <Card icon="mail" title="Sales Outreach" href="/use-cases/sales-outreach">
    Engage prospects and differentiate your sales process.
  </Card>

  <Card icon="gift" title="Sales Leave-Behind" href="/use-cases/sales-leave-behind">
    Equip champions with customized shareable demos.
  </Card>

  <Card icon="presentation" title="Sales Enablement" href="/use-cases/sales-enablement">
    Demo important workflows in reliable guided environments.
  </Card>
</CardGroup>

### Training

Use demos to drive product adoption and support customer success. From in-app guidance to training walkthroughs, Navattic helps users discover value faster and master key workflows.

<CardGroup>
  <Card icon="dock" title="In-app Demos" href="/use-cases/in-app-demos">
    Demo key activation points to boost engagement.
  </Card>

  <Card icon="user-round-plus" title="Customer Onboarding" href="/use-cases/training">
    Create demos to onboard users and showcase best practices.
  </Card>

  <Card icon="graduation-cap" title="Academy demos" href="/use-cases/demo-center">
    Help customers master essential workflows or train on advanced features.
  </Card>
</CardGroup>

<Info>
  Have questions or considerations about a use case not currently listed? Send a message to
  **[success@navattic.com](mailto:success@navattic.com)**
</Info>


# Sales enablement
Source: https://docs.navattic.com/use-cases/sales-enablement

Empower your sales team with interactive demos to accelerate deal cycles.

<CustomerQuote name="SourceDay" />

# Goals

Create a demo using Capture only steps and Beacons to help sellers reliably demo your most common workflows. These demos are designed to support synchronous settings or **presenter-led conversations** rather than asynchronous settings (ex. marketing use cases).

# Recommendations

* Use [Nav Links](https://www.loom.com/share/453383a381c84c92b6d34e4035eae19a?sid=0d53859a-0d4f-4490-8d9f-d53e67082e10)to quickly add multiple triggers to similar elements across Captures.
* Use Presenter Mode to hide dialog boxes using the keyboard shortcut Ctrl + P.
* Turn on Keyboard Navigation to progress through your interactive demo using your arrow keys.
* Keep Flows short (5-10 steps) and include a [Checklist]() to aid navigation
* Use the [Navattic Capture Editor](/build/captures/web) to help present the best version of your product
* Adjust the Beacon color in [Themes](/build/themes) to make this more or less apparent
* Add Trigger in a reliable space to allow presenters to "go back a step"

<img alt="" />

# Customer Examples

Locate the Beacon on each step to navigate through the demo.

<CardGroup>
  <Card title="Explore Vitally" href="https://training.navattic.com/6oa07tr" />

  <Card title="Explore Navattic" href="https://navattic-website.navattic.com/January2023" />
</CardGroup>

<Note>
  **Tip**: Create a version of your project that includes Modals and Tooltips, to share with your
  prospects as a sales leave-behind.
</Note>


# Sales leave-behind
Source: https://docs.navattic.com/use-cases/sales-leave-behind

Provide prospects with interactive demos they can share internally after sales calls.

<CustomerQuote name="Coupa" />

# Goals

A sales leave-behind is exactly what it sounds like — simply put, it is something you leave with prospective customers to maintain momentum after an initial conversation.

Interactive demos make great sales leave-behinds by reinforcing the most memorable moments of your conversation, educating prospects on your product, and **enabling your champions** in the procurement process, especially if additional stakeholders are joining the conversation on a rolling basis.

For a complex buying process with multiple decision-makers, an interactive demo is an excellent way to accelerate the sales process.

<Note>
  **Blog**: Read [How to Use Interactive Demos for Sales Leave
  Behinds](https://www.navattic.com/blog/interactive-demos-sales-leave-behinds) for customer
  insights and examples on this use case.
</Note>

# Recommendations

For leave-behind or enablement demos, we recommend creating multiple bite-sized demos that showcase different aspects of your product. Whenever a specific feature, use case, or persona is discussed on a sales call, reps can link out to the most relevant demo in their follow-up emails.

*Advanced tips to get the most from this use case:*

* **Customize** demos for your recipients with a [watermark](/product-updates#Sci_l), personal video greeting, or [personalization variables](/personalize)
* **Repurpose existing demos** and use [Find and Replace](/product-updates#2PrFw) to add your prospect's company names and logos, providing a highly personalized experience
* **Identify recipients** who open your demo with [query strings](/tracking/identify/visitors#query-strings) or [Account-Based Engagement](https://training.navattic.com/o9fg05mt) - both methods help you identify visitors without using a form gate
* **See viewer activity** via integration with [Slack](https://www.navattic.com/blog/slack-interactive-demos) or your CRM
* **Embed your** [Calendly or Chili Piper booking link](https://training.navattic.com/0u13e0bqe) to encourage prospects to schedule a follow-up - add this and/or other CTAs right after a "wow moment" in your demo

<Note>
  \*\*Tip: \*\*Enable your [Navattic Slack
  integration](https://www.navattic.com/blog/slack-interactive-demos) to receive real-time
  notifications when an identified Visitor or Account views your demo.
</Note>

# Customer Examples

Below are some customer examples we love. Keep an eye out for the recommendations highlighted above.

<CardGroup>
  <Card title="Vitally Blueprints" href="https://www.vitally.io/blueprints" />

  <Card title="Repsly" href="https://www.repsly.com/case-studies/altra" />

  <Card title="Jellyfish" href="https://jellyfish.co/platform/resource-allocations/" />

  <Card title="Revlitix's" href="https://www.revlitix.com/product-tour" />
</CardGroup>

<MediaCard type="demo" title="Sales Leave-Behind" />

<MediaCard type="demo" title="Sales Leave-Behind" />

***

# Implementation Guide

Sales enablement is the **most common sales use case** for interactive product demos. Follow the guidance below to create engaging assets for your champions to circulate in no time.

<MediaCard type="demo" title="Sales Leave-Behind" />

<img alt="" />

## 1. Content

**Make it user-friendly**: Your audience in this use case may be time-constrained. Include [navigation buttons](https://www.loom.com/share/dde828c52d4e4e4e820ddf64b2db5550) and value-driven copy to convey important points quickly. Keep each flow under 15 steps to encourage completion.

<img alt="" />

**Make it interactive**: Use tooltips, triggers, and beacons to let viewers experience using the product or envision how to integrate it in their day to day.

**Make it personal**: Consider presenting [multiple options](https://swipedon.navattic.com/product-tour-2023) in your demo to accommodate different stakeholder personas, features, or use cases.

<Note>
  **Tip:** Interactive demos are great champion enablement assets. What are questions your champions
  are likely to receive internally, and how can your demo get ahead of common stakeholder concerns?
</Note>

## 2. CTAs

\*\*Be direct: \*\*Include a single CTA at the end of the demo that pushes prospective customers towards the next step in your sales cycle.

**Consider your audience and get creative**: Use the appropriate CTA for each part of the sales journey. Consider linking to customer testimonials, a pricing page, a reference call scheduling page, or other pieces of sales collateral that are well-received by prospects.

Champions and other stakeholders who attended a live demo may have some product familiarity already and could be ready to skip ahead.\*\* **Turn on [**Escape View**](https://training.navattic.com/7429hwxgx)** \*\*to make your demo CTAs accessible at any time.

## 3. Deployment

**Provide options:** Organize demos for various features or buyer personas to help enable your champion. Embed demos side by side on a custom landing page, or use a checklist to present a list of options.

\*\*Share context: \*\*Include a short introduction to your demo or descriptions under each checklist item to help viewers identify the experience that is most relevant to them

\*\*Try ungating: \*\*Remember, sales-leave behinds are used to **mantain momentum** in the sales cycle. Consider ungating to reduce friction and use [query strings](/identify#6kxih) or [Account-based engagement instead.](https://training.navattic.com/o9fg05mt)

<CustomerQuote name="updates#CENjZ" />

## 4. Recommended Structure

**Steps 1-2:** Share the context for your demo. What does this product do? When is it used? ([Klue's Triage Mode demo](https://klue.com/blog/introducing-triage-mode?utm_campaign=triage%20mode\&utm_source=linkedin\&utm_medium=social\&utm_content=employees#navatic-iframe) is a great example)

<img alt="" />

**Steps 3-9:** Use Tooltips, Beacons, and Triggers to create an interactive experience. Keep text minimal to keep the focus on your product and reinforce those "wow" moments from your previous conversation.

**Steps 10-15:** What is the next step for qualified prospects? Conclude your demo with 1 direct CTA that is related to the next step in your sales process.


# Sales outreach
Source: https://docs.navattic.com/use-cases/sales-outreach

Increase response rates by including personalized demos in your sales outreach.

<CustomerQuote name="Insider" />

# Goals

**"When can I see the product?"** Start your sales process with a short product tour that engages your prospects, differentiates your sales process from competitors, and prepares prospects for a deeper-level conversation with AEs.

**This guide covers how to**:

* Create demos that follow content best practices
* Track visitors without using a form
* Receive real-time notifications of demo engagement

<MediaCard type="demo" title="Sales Outreach" />

***

# Implementation Guide

<img alt="" />

## 1. Content

**Share context**: Include a short introduction on step 1 of your demo to help viewers understand the objective and time commitment. For example, "See how Navattic supports customers in fintech with a 2-minute interactive demo."

**Try ungating**: Remember, sales outreach demos are used to garner interest in the product. Consider ungating to reduce friction and the Visitor Tracking methods below to identify your audience.

**Make it personal**: Consider presenting [multiple options](https://swipedon.navattic.com/product-tour-2023) in your demo to accommodate different stakeholder personas, features, or use cases. You can also add a [watermark](/product-updates#Sci_l), personal video greeting, or [personalization variables](/personalize).

**Make it user-friendly**: Your audience in this use case may be time-constrained. Include [navigation buttons](https://www.loom.com/share/dde828c52d4e4e4e820ddf64b2db5550) and value-driven copy to convey important points quickly. Keep each flow under 15 steps to encourage completion.

<img alt="" />

## 2. Visitor Tracking

<Note>
  While forms are an effective way to identify your demo visitors, they are not always a fit for the
  Sales Outbound use case as you have your recipients' contact information already. We recommend
  using these\*\* no-form\*\* tracking methods instead.
</Note>

**Track recipient engagement with Share Links:**

You can [customize Share Links](/identify#xcueE) directly within your Navattic workspace. This works similarly to a form, except you are filling in the information rather than asking your recipient to.

To customize your share link, visit your Product Demo --> Share Links --> Create Link > Identification & Personalization > add your variables as shown below.

<MediaCard type="demo" title="Sales Outreach" />

<img />

**Track recipient engagement with query strings:**

Query strings are a quick and easy way to identify visitors without a form fill. Simply add the string `?user.email=XXX@domain.com` to the end of your existing demo share link. This will tie the stated email to the browser that opens the link.

Be careful not to open the link yourself, as this will identify your own browser as your recipient instead.

You can combine this method with a tool like SalesLoft, Hubspot, Outreach, etc. to add query strings automatically by following the format: `navattic-demo-link``?user.email={{EMAIL_VARIABLE}}&user.fullName={{NAME_VARIABLE}}`

Take care to use the correct attribute name as these may vary between platforms. Here are a few common examples:

| Platform                                                                                              | Value | Attribute Name        | Complete query string for outreach                  |
| ----------------------------------------------------------------------------------------------------- | ----- | --------------------- | --------------------------------------------------- |
| [HubSpot](https://knowledge.hubspot.com/website-pages/personalize-your-content)                       | Email | \{\{contact.email}}   | navattic-demo-link?user.email=\{\{contact.email}}   |
| [Outreach](https://support.outreach.io/hc/en-us/articles/226680368-Outreach-Variables-Overview)       | Email | \{\{email}}           | navattic-demo-link?user.email=\{\{email}}           |
| [Salesloft](https://help.salesloft.com/s/article/Available-Dynamic-Fields?language=en_US#Person_Tags) | Email | \{\{email\_address}}  | navattic-demo-link?user.email=\{\{email\_address}}  |
| [Pardot](https://help.salesforce.com/s/articleView?id=sf.pardot_handlebars_merge_fields.htm\&type=5)  | Email | \{\{Recipient.Email}} | navattic-demo-link?user.email=\{\{Recipient.Email}} |

## 3. Notifications

**Get a real-time Slack or Email notification when visitors engage with your demo**. We recommend creating an Audience for "Identified visitors who view 2+ steps" and sending notifications to a Slack channel or individual emails. Visit [Playbooks]() to set this up.

**Tip:** You can even [set up routing to specific sales reps](/integrations/playbooks).

<img alt="" />

## 4. CTAs

**Be direct**: Include a single CTA at the end of the demo that pushes prospective customers towards the next step in your sales cycle.

**Embed your calendar**: Embed a Calendly or Chili Piper booking page directly in your demo. When choosing your step type, select **Embed** > **Calendly** or **Chilipiper** > **Enter the URL.** Try [this demo](https://training.navattic.com/0u13e0bqe)to see a Calendly embed in action.

<img alt="" />

<img alt="" />

## 5. Recommended Structure

**Steps 1-2:** Share the context for your demo. What does this product do? When is it used? ([Klue's Triage Mode demo](https://klue.com/blog/introducing-triage-mode?utm_campaign=triage%20mode\&utm_source=linkedin\&utm_medium=social\&utm_content=employees#navatic-iframe) is a great example)

<img alt="" />

**Steps 3-9:** Use Tooltips, Beacons, and Triggers to create an interactive experience. Keep text minimal to keep the focus on your product and reinforce those "wow" moments from your previous conversation.

**Steps 10-12:** What is the next step for qualified prospects? Conclude your demo with 1 direct CTA that is related to the next step in your sales process.


# Customer onboarding
Source: https://docs.navattic.com/use-cases/training

Create demos to onboard users and showcase best practices.

<CustomerQuote name="Form" />

Interactive demos are a great way to activate new users. Use demos throughout your knowledge base and customer journey to help customers master essential workflows, train on advanced features such as integrations, or to showcase exciting product updates. Keep in mind that demos can support your internal team enablement efforts, too.

### Recommendations

For training purposes, we recommend:

* Divide your content into digestible Flows of no more than 5-8 steps each
* Use a [checklist](/build#AIJEa) or demonstrate multiple workflows or to showcase important features. Aim to include 4-6 Flows in each checklist that are chronological or focus on a shared product area.
* Introduce your demos early in the customer journey: provide a demo onboarding option via in-app chat or in your onboarding resources to support different types of learners
* Consider using a demo to address FAQs that may be answered in 5-8 steps.
* Ungate demos to provide immediate value to your customers

### Customer Examples

Below are some customer examples we love. Keep an eye out for the recommendations above.

<CardGroup>
  <Card title="Traackr: Quickstart Course" href="https://academy.traackr.com/quickstart-course" />

  <Card title="Coursedog: Coursedog Universe" href="https://www.coursedog.com/resources/universe" />

  <Card title="Navattic: What's New?" href="https://training.navattic.com/r04504re" />

  <Card title="Vitally Academy: Interactive Demos" href="https://www.vitally.io/academy#interactive-product-tours" />
</CardGroup>

### Implementation Guide

Follow the guidance below to create training demos that will drive product adoption and usage across your existing customer base. Remember to check the [Project Analytics](/analyze) to view drop-offs for each step and use that data to continue improving your demo.

## 1. Structure

**Starting Flow**: Start with a goal-oriented introduction to the training module (ex. "Take the Navattic Crash Course to see how to create a project, view visitor data, and invite your teammates.")

**Checklist**: Include a Checklist to help users find the content that is most relevant to them. Make sure each Checklist task includes a clear goal-oriented description, just like your starting flow. Isolate your most essential workflows to help users get activated ASAP.

**Navigation**: It's important to make your onboarding resources as user-friendly as possible. Turn on Navigation Buttons in your [Flow Settings](https://demo-staging.navattic.com/docs) to help first-time users navigate smoothly throughout your demo. Consider adding a Progress Bar to your [Theme](/build/themes), to help users view their progress and manage their time.

<Note>
  **Tip:** Use a training demo to excite users about the product solutions they are about to unlock.
  No need to show every single click or feature in your onboarding demo, as users will likely have
  access to your product already.
</Note>

## 2. CTAs

**Consider your audience and get creative**:
Use the appropriate CTA for each part of the customer journey. Consider linking to a:

* Knowledge base
* Webinar registration page
* Product feedback form
* Pricing page for additional features

**Existing users may have some product familiarity already and be ready to skip ahead.**

Turn on [Escape View](https://training.navattic.com/7429hwxgx) to make your demo CTAs accessible at any time. ## 3. DeploymentDeploy demos alongside other training mediums like videos, written documentation, or live webinars to help customers find the resource that aligns with their learning style. We recommend an ungated experience for low friction new user onboarding. Consider these form-alternatives for managing the audience for your demos: \* Turn on [Passcode Protection](/product-updates#CENjZ) for any top-secret demos

* Embed demos on an existing website or learning management system that is only accessible to users
* Present demos through an in-app chat that is only accessible to users of your product

<img />

<Note>
  **Tip:** Empower your chatbot! Customers look to chatbots for real-time resources or support.
  Include a short demo in your FAQ snippets to clear up common mishaps while customers wait to chat
  with a representative.
</Note>

## 4. Maintenance

Navattic demos are easy to update, even after they have been Published and shared with your customers. No need to re-record a training video every time there is a UI update in your product. When it is time to update your Project, simply edit the associated Captures, Flows, or Checklists and click "**Publish**". This will push changes directly to all instances of this Project that has been shared or embedded. Replace outdated Captures at any time without impacting the rest of your demo.

<MediaCard type="video" title="Training" />


# Website demos
Source: https://docs.navattic.com/use-cases/website-demos

Embed interactive demos on your website to increase conversions and qualify leads.

<CustomerQuote name="Ramp" />

<Icon icon="panels-top-left" /> **Website demos** are concise, easy to follow, and value-driven. Include a demo as the primary or secondary CTA on your site to build product awareness and convert top-of-funnel leads. Use an ungated demo to direct traffic toward your primary website CTA or include a Form to send viewer information to your CRM. Consider linking out to a full-screen version of your demo to provide the most immersive viewing experience.

### Recommendations

For a top-of-funnel audience, we recommend:

* Lead with a value-driven introduction and keep dialog text concise ([Blog: Tips from a Copywriting Expert](https://www.navattic.com/blog/interactive-demo-copywriting-tips))
* Include 10-15 steps that tell a compelling story about your product; try a [Checklist]() to organize longer stories
* Embed your demo above the fold for 3.5x website visitor engagement ([How to Promote you Demo](https://www.navattic.com/report/state-of-the-interactive-product-demo-2023#How-to-Promote-your-Interactive-Demo))

### Customer Examples

Below are some customer examples we love. Keep an eye out for the recommendations above.

<CardGroup>
  <Card title="Atlan: See Product Tour" href="https://atlan.com/" />

  <Card title="Lattice: Start the Tour" href="https://lattice.com/tour" />

  <Card title="Traackr: Discover Traackr" href="https://www.traackr.com/influencer-marketing-platform" />

  <Card title="Dailypay: Take a Tour" href="https://get.dailypay.com/" />

  <Card title="CaptivateIQ: Tour CaptivateIQ" href="https://www.captivateiq.com/product-tour" />

  <Card title="Calm: Take a Product Tour" href="https://health.calm.com/employers/" />
</CardGroup>

### Implementation Guide

Follow the guidance below to create a high-converting demo for your marketing site. Demos built with these best practices see on average a 20-30% Flow completion and 10-15% conversion rate. Use [Project Analytics](/analyze) to see drop-offs for each step and to continue improving your demo.

<Steps>
  <Step title="Structure">
    **Steps 1-2**: Start with a value-driven introduction (ex. "Our product demo will show you how powerful Ramp can be for your business"). If using a Form, keep it as brief as possible (90% of current demos with forms include just 1-2 fields)]

    **Steps 3-8**: Use Tooltips to highlight a few key features. Remember to include wow moments, skip transitions (e.g., click here to move to next screen), and consider how each feature addresses prospect pain points

    **Steps 9-12**: Get ready to conclude your demo. What is one impressive wow moment you can end on? Include 1-2 differentiated CTAs on your last step.

    <Note>
      **Blog:** Read our [High Converting Interactive Demos Tips from a Copywriting Expert](https://www.navattic.com/blog/interactive-demo-copywriting-tips) for suggestions and customer examples.
    </Note>
  </Step>

  <Step title="CTAs">
    **Build on momentum**: Include a CTA after showcasing major product wow moments. Encourage conversion after every 5-7 steps or enable [escape view](https://training.navattic.com/7429hwxgx) to make CTAs accessible at any point. **Be consistent**: Maintain the same CTAs across your marketing journey to drive conversions towards your main conversion goal (ie, trial signups, demos booked). Utilize [UTM paramaters](https://blog.hubspot.com/customers/understanding-basics-utm-parameters) to track traffic that originates from Navattic.

    <img alt="" />
  </Step>

  <Step title="Gating vs. Ungating">
    We recommend providing both gated and ungated assets on your site. An ungated demo is an instant way to provide value to site visitors and to direct traffic towards your primary CTA. If using a form, we recommend including 1-2 fields within the first 5 steps of your demo. Make sure to integrate with your CRM to create or update contacts with demo engagement data.

    <Note>
      **Tip:** If using a form to gather leads, use [Personalization](/demos/personalized) to turn form fields into dynamic variables (ie., merge fields) that may be referenced throughout your demo.
    </Note>

    **Consider the deployment that shows your product best.** Share your project with end users via a direct link or website embed.Try out various responsiveness strategies and embed settings to find the best fit for presenting your demo. Check out customer example to see different options for successful deployments.

    <Note>
      **Tip:** Showcase your demo or demo CTA above the fold for 3.5x website visitor engagement.
    </Note>

    <img alt="" />
  </Step>
</Steps>

## Customer Interview Series

See how Repsly leverages a demo to drive conversion towards a `Book a Demo` CTA. Read about their strategy in the blog: [Customer Interview Series: Website CTA with Craig LeBlanc](https://www.navattic.com/blog/customer-interview-craig-leblanc)

<MediaCard type="video" title="Website Overview" />

<MediaCard type="video" title="Website Overview" />


# Approval Workflow
Source: https://docs.navattic.com/workspace/approval-workflow

Require approval before publishing changes to demos.

<Info>Available on the Growth plan and above.</Info>

When working with a team, you may want to ensure that changes to published demos are reviewed before going live. The **Require approval to publish** setting adds a review step so that only approved changes can be published.

## Enabling approval workflow

<Steps>
  <Step title="Navigate to workspace settings">
    Go to **Settings > General** in your workspace.
  </Step>

  <Step title="Enable the setting">
    Toggle on **Require approval to publish demos**. Once enabled, only admins and demo owners can directly publish changes to already-published demos. Other members will need to request approval first.
  </Step>
</Steps>

<Note>This setting only applies to demos that have already been published. Any team member can still publish a demo for the first time.</Note>

## Who can publish directly

When the approval workflow is enabled, the following users can publish changes without requesting approval:

* **Workspace admins**
* **Demo owners** (the person who created the demo)
* **Collaborators with publish permission** granted by the demo owner

All other team members must request a review before their changes can be published.

## Requesting a review

If you don't have permission to publish directly, you'll see a banner indicating that approval is required.

<Steps>
  <Step title="Click Request review">
    After making changes to a published demo, click **Request review** in the banner above the flow builder.
  </Step>

  <Step title="Select reviewers">
    Choose one or more reviewers from the list. Available reviewers include the demo owner, workspace admins, and collaborators with publish permission.
  </Step>

  <Step title="Add an optional message">
    Include context about what changed and why, so reviewers can evaluate your updates quickly.
  </Step>

  <Step title="Submit the request">
    Reviewers will receive an email notification with a link to review your changes.
  </Step>
</Steps>

<Note>There is a 24-hour cooldown before you can re-request a review from the same set of reviewers.</Note>

## Reviewing and approving changes

When you receive a review request, you'll see a banner in the demo builder indicating that changes are waiting for your review.

<Steps>
  <Step title="Click Review changes">
    Open the demo and click **Review changes** to see what was modified.
  </Step>

  <Step title="Approve the changes">
    If the changes look good, approve the request. The author (or any user with publish permission) can then publish the demo.
  </Step>
</Steps>


# Boards
Source: https://docs.navattic.com/workspace/boards

Organize your product demos onto shared views.

<Frame>
  <img alt="Boards" />
</Frame>

<Icon icon="grid-3x3" /> **Boards** are a powerful way to organize your product demos onto shared views.

### How to create boards

Follow these steps to learn how to create boards:

<Steps>
  <Step title="Create a board">
    Navigate to <Icon icon="grid-3x3" /> Board Settings

    and create a board for your newly created team. You can name the board anything memorable for your team ex. "Sales" or "Outbound demos". Any number of boards can be created for Launchpad.

    <img alt="Create board" />

    <Info>
      Over time you can create boards per use case, product, team, etc. We recommend you start simple and create boards based on your organization's initial needs.
    </Info>
  </Step>

  <Step title="Add demos to the new board(s)">
    Under <Icon icon="layout-grid" /> **Product demos**, find the top-performing demos relevant to your sales team. You can use the filters to narrow down the demos by activity or labels.

    Consult your top sales reps (AEs, SEs, BDRs, and SDRs) on what areas of the product are particularly important for them to show off in demos.

    <img alt="Add demo to board" />
  </Step>
</Steps>

<Icon icon="party-popper" /> **Congratulations** -- you've learned how to build <Icon icon="grid-3x3" /> **Boards** to organize your demo.

Next, learn how to add labels to demos and categorize them and make them easier to find.

<CardGroup>
  <Card icon="tag" href="/workspace/labels" title="Labels">
    Add labels to your demos to categorize them and make them easier to find.
  </Card>
</CardGroup>

## Navigating boards with teams

If your workspace has [teams](/workspace/teams) enabled and contains more than five boards, the board selector organizes boards into groups to make navigation easier.

Boards are grouped as follows:

* **Workspace** — Boards accessible to all workspace members
* **Personal** — Your private boards
* **\[Team name]** — One group per team you belong to, showing boards scoped to that team

Click a group name to expand it, then select the board you want to view. Workspace admins can see all boards across every group, including teams they're not a member of. Personal boards also display the owner's name so admins can identify who created each one.

<Note>
  Team boards can contain both Interactive Demos and Launchpad boards — you no longer need a Launchpad-only workspace to use team-scoped boards.
</Note>


# Directory Sync
Source: https://docs.navattic.com/workspace/directory-sync

Automatically provision users using an identity provider, such as Okta.

<Info>
  Enabled in workspaces on the Growth plan and above.
</Info>

### What does Directory Sync do?

1. **Centralized User Provisioning:** Admins can now easily add and remove users from your directory provider through a unified User Lifecycle Management (ULM) process. Your directory provider will be the source of truth for user and group lists, and Directory Sync will keep everything up-to-date in Navattic
2. **Automatic Updates:** No more duplicate manual data entry. Directory Sync takes care of:
   * Provisioning new users
   * Updating user attributes such as name and email
   * Deprovisioning users from your workspace

<Warning>
  With Directory Sync enabled, all users must be managed through SCIM.
</Warning>

### How to enable Directory Sync for your workspace

Once Directory Sync is enabled, you can navigate to Settings > Security > Directory Sync to set up the configuration.

Follow the steps to connect to your Directory provider.

Now, your Navattic workspace members will be updated accordingly when you add or remove users from your Directory.

<CardGroup>
  <Card
    title="Entra ID SCIM (formerly Azure)"
    href="https://workos.com/docs/integrations/entra-id-scim"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/azure.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Google SCIM"
    href="https://workos.com/docs/integrations/google-directory-sync"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/google.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="JumpCloud SCIM"
    href="https://workos.com/docs/integrations/jumpcloud-scim"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/jumpcloud.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="OneLogin SCIM"
    href="https://workos.com/docs/integrations/onelogin-scim"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/onelogin.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="Okta SCIM"
    href="https://workos.com/docs/integrations/okta-scim"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/okta.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Rippling SCIM"
    href="https://workos.com/docs/integrations/rippling-scim"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/rippling.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="CyberArk SCIM"
    href="https://workos.com/docs/integrations/cyberark-scim"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/cyberark.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="PingFederate SCIM"
    href="https://workos.com/docs/integrations/pingfederate-scim"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/ping-identity.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card title="Generic SCIM" href="https://workos.com/docs/integrations/scim" icon="id-card" />
</CardGroup>

## Mapping groups to teams

After setting up Directory Sync, you can link identity-provider groups to Navattic teams. When a user is added to or removed from a group in your directory, their Navattic team membership updates automatically.

### Setting up team mapping

1. Navigate to **Settings > Teams** and open the team you want to configure.
2. Select **Add directory group** and choose the group from your identity provider.
3. Confirm the mapping. Members of that group will be synced into the Navattic team.

<Note>
  Team mapping requires Directory Sync to be active and at least one group defined in your identity provider.
</Note>

### Removing a team mapping

When you remove a group mapping, you are prompted to choose one of two options:

* **Keep current members** — Existing team members remain in the team after the mapping is removed.
* **Remove current members** — Members who were added via the mapping are removed from the team when the mapping is deleted.

# FAQs

<Accordion title="How do I assign Navattic workspace roles to users added via directory sync?">
  Contact [success@navattic.com](mailto:success@navattic.com) to request this service. Please include the Group Name(s) and desired Navattic user role (ex. "I'd like to set all Marketing Operations (group name) to be Builders (user role) in my Navattic workspace.") This is a custom connection that our team can help enable.
</Accordion>


# Labels
Source: https://docs.navattic.com/workspace/labels

Add labels to your demos to categorize them and make them easier to find.

<Frame>
  <img alt="Labels" />
</Frame>

<Icon icon="tag" /> **Labels** are a way to categorize your demos and make them easier to find.

You can develop your own strategy for labeling your demos. For example, you could use labels to categorize demos by product feature, customer type, or sales stage. Here are some examples:

* **Product Feature**: "Product A", "Product B", "Product C"
* **Customer Type**: "Enterprise", "Small Business", "Individual"
* **Sales Stage**: "Prospecting", "Qualification", "Proposal"

### How to create labels

Follow these steps to learn how to create labels:

<Steps>
  <Step title="Create a label">
    Navigate to <Icon icon="tag" /> <a href="https://app.navattic.com/w/settings/labels">
    Label Settings</a>

    and create a label.

    <img alt="Create label" />
  </Step>

  <Step title="Add labels to your demos">
    Under <Icon icon="layout-grid" /> Product demos, select more actions on a demo to add labels.

    <img alt="Add label to demo" />
  </Step>
</Steps>

<Icon icon="party-popper" /> **Congratulations** -- you've learned how to build
<Icon icon="grid-3x3" /> **Boards** to organize your demo.

Next, learn how to manage your teams and specify their access to demos.

<CardGroup>
  <Card title="Teams" icon="users" href="/workspace/teams">
    Manage your teams and specify their access to demos.
  </Card>
</CardGroup>


# MCP server
Source: https://docs.navattic.com/workspace/mcp-server

Connect AI coding agents to your Navattic workspace using the Model Context Protocol.

The Navattic MCP server gives AI coding agents — such as Claude Desktop, Cursor, VS Code Copilot, Windsurf, ChatGPT, and Codex — structured access to your workspace. Agents can read analytics, browse and build demos, manage Launchpad share links, and query personalization data, all scoped to your workspace.

<Frame>
  <img alt="Navattic MCP server connected to an AI coding agent" />
</Frame>

<Note>
  The MCP server is available on the Startup plan and above.
</Note>

## How it works

The Navattic MCP server supports two authentication methods depending on your AI client:

* **OAuth** (Claude Desktop, Claude Code, ChatGPT, Gemini Enterprise) — sign in to Navattic when prompted. No Personal Access Token required.
* **Bearer token** (Cursor, VS Code, Windsurf, Codex, IBM Bob, Microsoft Copilot Studio) — create a Personal Access Token and add it to your client's config file.

All operations are scoped to your workspace — agents cannot access data from other workspaces, even with a valid resource ID from another workspace.

<Tip>
  Go to **Settings** > **AI** > **MCP** in your workspace to find your MCP server URL and the full setup guide for every client in one place.
</Tip>

## Step 1: Create a Personal Access Token (bearer token clients only)

If you're using Cursor, VS Code, Windsurf, Codex, IBM Bob, or Microsoft Copilot Studio, you need a Personal Access Token. Skip this step if you're using Claude Desktop, Claude Code, ChatGPT, or Gemini Enterprise.

<Note>
  Only workspace **Admins** can create Personal Access Tokens. Builders can view existing tokens in **Settings** > **Workspace** > **Access Tokens** but cannot create or revoke them. Each workspace supports up to 25 active tokens per user.
</Note>

<Steps>
  <Step title="Go to MCP settings">
    Navigate to **Settings** > **AI** > **MCP** in your Navattic workspace.
  </Step>

  <Step title="Create a new token">
    Click **Manage personal access tokens**, then click **Create token**. Enter a name for the token (for example, "Cursor agent").
  </Step>

  <Step title="Select scopes">
    Choose the scopes your agent needs. Each scope grants access to a specific set of tools:

    | Scope               | What it allows                                                                                   | Required role                               |
    | ------------------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------- |
    | **Analytics**       | View demo performance, visitor data, and account engagement                                      | Viewer or above                             |
    | **Demo Browsing**   | Browse projects, flows, and share links                                                          | Viewer or above                             |
    | **Demo Building**   | Create flows; edit steps, buttons, navigation, beacons, media, voiceover, and presenter settings | Builder or above                            |
    | **Demo Management** | Rename and organize projects; create share links                                                 | Builder or above                            |
    | **Demo Publishing** | Publish and archive demos                                                                        | Builder or above                            |
    | **Personalization** | View custom properties and visitor activity                                                      | Viewer or above                             |
    | **Launchpad**       | Browse and manage Launchpad share links, interest flows, and recipient visitor data              | Viewer or above (Launchpad workspaces only) |

    <Note>
      The **Launchpad** scope is only available in workspaces with Launchpad enabled and is only shown to users with the Launchpad app role. The scope picker will not display it otherwise.
    </Note>

    <Tip>
      Start with Analytics and Demo Browsing — these cover read-only operations. Add write scopes only if your agent needs to create or modify demos.
    </Tip>
  </Step>

  <Step title="Set an expiration">
    Choose a token lifetime: 7, 30, 60, 90, or 180 days. Tokens expire automatically; you'll need to create a new token when one expires.
  </Step>

  <Step title="Copy the token">
    After creating the token, copy it immediately. You won't be able to see it again.

    <Warning>
      Store your token securely. Anyone with the token can access your workspace within the granted scopes.
    </Warning>
  </Step>
</Steps>

## Step 2: Configure your MCP client

Connect your AI agent using the Navattic MCP server URL:

```
https://app.navattic.com/api/mcp
```

You can copy this URL from **Settings** > **AI** > **MCP** in your workspace. Use the instructions below for your client:

<Tabs>
  <Tab title="ChatGPT">
    ChatGPT uses OAuth — no Personal Access Token needed.

    <Steps>
      <Step title="Open ChatGPT settings">
        Open ChatGPT on the web → your profile → **Settings** → **Connectors**.
      </Step>

      <Step title="Enable developer mode">
        Open **Advanced** and enable **Developer mode**.
      </Step>

      <Step title="Create a connector">
        Go to **Connectors** → **Create**.
      </Step>

      <Step title="Add the Navattic MCP URL">
        Enter a name, choose **OAuth**, and paste the Navattic MCP URL: `https://app.navattic.com/api/mcp`.
      </Step>

      <Step title="Authorize">
        Click **Create**, then sign in to Navattic when prompted.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Claude Desktop">
    Claude Desktop uses OAuth — no Personal Access Token needed.

    <Steps>
      <Step title="Open Claude Desktop settings">
        In Claude Desktop, go to **Settings** → **Connectors**.
      </Step>

      <Step title="Add a custom connector">
        Click **+ Add custom connector**.
      </Step>

      <Step title="Enter the Navattic MCP URL">
        Paste `https://app.navattic.com/api/mcp` and click **Add**.
      </Step>

      <Step title="Authorize the connection">
        Claude Desktop will open a Navattic authorization page. Sign in and grant access.
      </Step>
    </Steps>

    <Accordion title="Alternative: edit the config file manually">
      If you prefer to configure Claude Desktop by editing the config file directly, add the following to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS):

      ```json theme={null}
      {
        "mcpServers": {
          "navattic": {
            "url": "https://app.navattic.com/api/mcp",
            "headers": {
              "Authorization": "Bearer YOUR_TOKEN"
            }
          }
        }
      }
      ```

      Replace `YOUR_TOKEN` with the Personal Access Token you created in Step 1. Restart Claude Desktop after saving.
    </Accordion>
  </Tab>

  <Tab title="Claude Code">
    Claude Code uses OAuth. Run this command in your terminal:

    ```bash theme={null}
    claude mcp add --transport http navattic https://app.navattic.com/api/mcp
    ```

    Then run `/mcp` in your Claude Code session and select **navattic** to authenticate.

    <Accordion title="Alternative: add to settings.json manually">
      Add to `~/.claude/settings.json`:

      ```json theme={null}
      {
        "mcpServers": {
          "navattic": {
            "type": "url",
            "url": "https://app.navattic.com/api/mcp",
            "headers": {
              "Authorization": "Bearer YOUR_TOKEN"
            }
          }
        }
      }
      ```

      Replace `YOUR_TOKEN` with the Personal Access Token you created in Step 1.
    </Accordion>
  </Tab>

  <Tab title="Codex">
    Add to `~/.codex/config.toml`:

    ```toml theme={null}
    [mcp_servers.navattic]
    url = "https://app.navattic.com/api/mcp"
    bearer_token_env_var = "NAVATTIC_TOKEN"
    ```

    Then set the environment variable in your shell (or add it to your shell profile):

    ```bash theme={null}
    export NAVATTIC_TOKEN=your_token_here
    ```

    Replace `your_token_here` with the Personal Access Token you created in Step 1.
  </Tab>

  <Tab title="Cursor">
    Add to `~/.cursor/mcp.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "navattic": {
          "url": "https://app.navattic.com/api/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_TOKEN"
          }
        }
      }
    }
    ```

    Replace `YOUR_TOKEN` with the Personal Access Token you created in Step 1.
  </Tab>

  <Tab title="VS Code">
    Add to your VS Code settings (the `mcp` section):

    ```json theme={null}
    {
      "servers": {
        "navattic": {
          "type": "http",
          "url": "https://app.navattic.com/api/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_TOKEN"
          }
        }
      }
    }
    ```

    Replace `YOUR_TOKEN` with the Personal Access Token you created in Step 1.
  </Tab>

  <Tab title="Windsurf">
    Add to `~/.codeium/windsurf/mcp_config.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "navattic": {
          "serverUrl": "https://app.navattic.com/api/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_TOKEN"
          }
        }
      }
    }
    ```

    Replace `YOUR_TOKEN` with the Personal Access Token you created in Step 1.
  </Tab>

  <Tab title="IBM Bob">
    Add to `~/.bob/mcp.json` for a global config, or `.bob/mcp.json` in your project root for a project-specific config:

    ```json theme={null}
    {
      "mcpServers": {
        "navattic": {
          "url": "https://app.navattic.com/api/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_TOKEN"
          }
        }
      }
    }
    ```

    Replace `YOUR_TOKEN` with the Personal Access Token you created in Step 1. You can configure MCP from the **Bob settings menu** under the **MCP** tab.
  </Tab>

  <Tab title="Gemini (Enterprise)">
    Gemini for Google Workspace Enterprise uses OAuth — no Personal Access Token needed. Setup requires admin access to your Google Workspace account.

    <Steps>
      <Step title="Open Gemini Enterprise settings">
        In the Google Cloud Console, navigate to **Gemini Enterprise** → **Data stores**.
      </Step>

      <Step title="Create a data store">
        Click **Create data store**, then search for **Custom MCP Server** and select it.
      </Step>

      <Step title="Add the Navattic MCP URL">
        Enter a name for the connection and paste the Navattic MCP URL: `https://app.navattic.com/api/mcp`. Set the transport to **StreamableHTTP**.
      </Step>

      <Step title="Configure authentication">
        Under **Authentication settings**, select **OAuth 2.0** and complete the authorization flow to connect your Navattic account.
      </Step>
    </Steps>

    <Note>
      Gemini Enterprise MCP integration requires a Google Workspace Enterprise plan with Gemini Enterprise add-on. Contact your Google Workspace admin if you do not have access.
    </Note>
  </Tab>

  <Tab title="Microsoft Copilot Studio">
    Microsoft Copilot Studio supports connecting to MCP servers via its onboarding wizard.

    <Steps>
      <Step title="Open Copilot Studio">
        In Microsoft Copilot Studio, open your agent and navigate to **Actions** → **Add an action** → **Connect an MCP server**.
      </Step>

      <Step title="Fill in server details">
        Enter a name (for example, "Navattic") and the Navattic MCP URL: `https://app.navattic.com/api/mcp`.
      </Step>

      <Step title="Add your token">
        In the **API key** field, enter your Personal Access Token.

        <Warning>
          Enter only the raw token value. Do not include `Bearer` or any other prefix. Copilot Studio automatically sends the request as `Authorization: Bearer <your-token>` — including the prefix yourself will cause authentication to fail.
        </Warning>
      </Step>

      <Step title="Save and test">
        Click **Save**. The Navattic tools will appear in your agent's action list.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## What you can do

Once connected, your agent can perform actions based on the scopes granted to its Personal Access Token. The available capabilities depend on which scopes you selected when creating your token.

**Analytics**

View demo engagement metrics and visitor data. Ask your agent to surface views, session counts, and click-through rates across all active demos, or drill into individual visitors and company accounts — including session history, demos viewed, and firmographic details. Filter by demo, company, location, industry, employee count, and custom properties.

**Demo browsing**

Search and read your workspace library. Your agent can list all projects, find demos by name or keyword, read flow step content, and list a demo's share links with their public URLs. It can also check whether a demo has unpublished draft changes, read the workspace's product knowledge base, and browse the captures available to anchor new or edited steps.

**Demo building**

Create new flows in an existing project and edit existing flows. Agents can edit all aspects of a flow's content:

* **Steps** — Add, remove, move, or update steps; change tooltip text, overlay style, and progress indicator behavior.
* **Buttons** — Change button labels, URLs, and click actions.
* **Navigation and exit views** — Update navigation behavior between steps and configure what viewers see at the end of a demo.
* **Beacons and triggers** — Add or update hotspot beacons and the click triggers that advance viewers through the flow.
* **Media and voiceover** — Swap out capture images or videos, and add or remove voiceover audio.
* **Presenter settings** — Update presenter notes and presenter mode configuration.

Edits are validated and applied atomically: if any action fails, nothing is saved.

You can also copy captures from one demo into another, and duplicate existing flows for reuse across projects.

**Demo management**

Create new projects, rename projects, and create share links.

**Demo publishing**

Publish demos and archive projects. Publishing makes any draft changes immediately visible to all visitors on the demo's share links and embeds. Archiving affects the demo's live URLs. Some workspaces restrict publishing to the demo's creator or admins.

**Personalization**

List custom properties set up for visitor personalization.

**Launchpad** (Launchpad workspaces only)

Browse, create, and look up 1-1 Launchpad share links with recipient and engagement data. Search interest flows by name or description.

Your agent also has access to three workspace resources regardless of scopes:

* **Workspace overview** — current project count, member count, and plan type
* **Navattic concepts** — a reference guide to the Navattic data model (projects, flows, steps, share links)
* **Flow editing guide** — explains the read→edit loop, step and button locators, the entity\_tag concurrency token, and how index positions shift after structural changes

<Note>
  When asking your agent to edit a flow, have it read the current flow document first to get the step structure and a version token. Pass that version token when requesting edits — if the flow has been changed since the read, the edit is rejected to prevent conflicts. After any structural change (inserting, moving, or removing a step), step indices shift; re-read the flow before sending the next batch. All edits in a batch apply atomically — if any action fails, nothing is saved.
</Note>

## Suggested prompts

Copy any of these prompts into your AI agent to get started. Replace the placeholder text in brackets with your own values.

**Analytics**

* "Which of our demos has the highest engagement rate over the past 30 days?"
* "List the top 10 visitors by total time spent across all demos this month."
* "Show me all visitors from \[company name] who have viewed our demos."
* "Which companies in the \[industry] sector have engaged with our demos recently?"
* "How many unique visitors did \[demo name] get last week, and what was the average session duration?"

**Demo library**

* "List all projects in the workspace and show how many flows each one has."
* "Find all demos related to \[product area or keyword]."
* "List all share links for \[demo name] and show their public URLs."
* "Does \[demo name] have any unpublished changes?"
* "Publish \[demo name] so the latest changes go live."

**Demo editing**

* "Read the flow document for \[flow name] in \[project name] and summarize what each step says."
* "Update step 3 of \[flow name] in \[project name] to say: \[new text]."
* "Add a new step after step 5 in \[flow name] with the title \[title] and body text \[body]."
* "Rename the project \[current name] to \[new name]."
* "Create a new project called \[name]."
* "Duplicate the flow \[flow name] in \[project name]."
* "Copy the captures from \[source demo name] into \[target demo name] so I can reuse them."

**Launchpad share links**

* "Create a Launchpad share link for \[first name] \[last name] at \[company] using the \[interest flow name] interest flow."
* "List all Launchpad share links created this week and show which recipients have viewed their demos."
* "Find the Launchpad share link for \[recipient name] and show me their engagement details."

**Personalization**

* "List all custom properties configured in the workspace."

## Use cases

<AccordionGroup>
  <Accordion title="Analyze demo performance in your coding environment">
    Ask your AI agent questions about demo engagement and visitor behavior. For example: "Which of our demos got the most engagement last quarter?", "Who from Acme Corp has viewed our demos recently?", or "What companies are showing the most interest this month?" The agent uses the analytics tools to query your workspace data and present results directly in your editor.
  </Accordion>

  <Accordion title="Build demos programmatically">
    Use your agent to create new projects and flows, duplicate existing flows, or copy captures between demos. Describe the steps you want in natural language and let the agent structure and create them for you. This is useful when building many similar demos, scaling a template across multiple projects, or automating demo creation as part of a deployment workflow.
  </Accordion>

  <Accordion title="Browse your demo library">
    Ask the agent to list all projects and find specific demos by name or description. The agent has access to your full workspace library, including flow structure and share links.
  </Accordion>

  <Accordion title="Automate demo maintenance">
    Use the agent to rename or archive projects as part of a release workflow. For example, archive old version demos automatically when a new version is deployed.
  </Accordion>

  <Accordion title="Manage Launchpad share links and track engagement (Launchpad)">
    Use the Launchpad capabilities to automate 1-1 share link creation and track which recipients have visited their demos. For example, ask the agent: "List all share links sent to prospects this week and show which ones have been viewed." You can also ask the agent to find the right interest flow for a prospect before generating a personalized link.
  </Accordion>

  <Accordion title="Edit a demo using AI">
    Use the Demo Building scope to read and update steps in an existing flow. The agent first reads the current flow to understand the step structure, then applies a batch of ordered edits — updating text, buttons, beacons, voiceover, and more. All edits in the batch apply atomically, so a partial failure leaves the flow unchanged. After any structural change (inserting, moving, or removing a step), the agent re-reads the flow because step indices shift. This approach makes it straightforward to apply consistent changes across many steps or flows at once.
  </Accordion>
</AccordionGroup>

## Managing tokens

You can view all active tokens from **Settings** > **Workspace** > **Access Tokens**. From there you can:

* See each token's name, scopes, creation date, and expiration
* Revoke a token at any time — revocation takes effect immediately

When a token expires or is revoked, any agent using it will receive authentication errors until you update its configuration with a new token.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can I create multiple tokens for different agents?">
    Yes. Create a separate token for each agent or environment, and name them to make revocation easier. For example, "Cursor - local dev" or "VS Code - production".
  </Accordion>

  <Accordion title="Is there a limit to how many tokens I can have?">
    Yes. Each user can have up to 25 active (non-expired, non-revoked) tokens per workspace. If you reach the limit, revoke unused tokens from **Settings** > **Workspace** > **Access Tokens** before creating new ones.
  </Accordion>

  <Accordion title="What happens if my token is compromised?">
    Revoke the token immediately from **Settings** > **Workspace** > **Access Tokens**. Then create a new token and update your agent configuration. The revoked token stops working as soon as you revoke it.
  </Accordion>

  <Accordion title="Who can create Personal Access Tokens?">
    Only workspace Admins can create Personal Access Tokens. Builders have view-only access to the tokens list and cannot create or revoke tokens. Viewer and Launchpad Rep roles cannot access the tokens settings at all.
  </Accordion>

  <Accordion title="Can a Viewer-role user create a token with write scopes?">
    No. The scope picker automatically disables write scopes (Demo Building, Demo Management, Demo Publishing) for users with Viewer-only roles.
  </Accordion>

  <Accordion title="Does the agent see all my workspace data?">
    The agent can only access data within the scopes you selected when creating the token. All data is also restricted to your workspace — the agent cannot access data from other workspaces.
  </Accordion>

  <Accordion title="Why don't I see the Launchpad scope when creating a token?">
    The Launchpad scope is only available to workspaces with Launchpad enabled and only shown to users with the Launchpad app role. If you don't see it, confirm your workspace has Launchpad and that your account has the Launchpad role. Contact your workspace admin if you need access.
  </Accordion>

  <Accordion title="Do I need a Personal Access Token for Claude Desktop or Claude Code?">
    No. Claude Desktop, Claude Code, ChatGPT, and Gemini Enterprise authenticate via OAuth — you simply sign in to Navattic when prompted. Personal Access Tokens are only needed for Cursor, VS Code, Windsurf, Codex, IBM Bob, and Microsoft Copilot Studio.
  </Accordion>
</AccordionGroup>


# Security & privacy
Source: https://docs.navattic.com/workspace/security

An overview of Navattic's security posture, data handling practices, and tools for protecting sensitive information in demos.

Navattic is built with security in mind at every layer — from how your demo content is captured and stored to how access is controlled within your workspace. For compliance documentation, certifications, and downloadable security materials, visit the [Navattic Trust Center](https://trust.navattic.com/).

## Compliance certifications

Navattic maintains industry-standard certifications to support enterprise procurement and infosec reviews. Current certifications — including SOC 2 Type II and GDPR compliance — are listed on the [Navattic Trust Center](https://trust.navattic.com/).

<Note>
  If your infosec team needs security documentation or you need to complete a vendor security questionnaire, visit the Trust Center or contact [success@navattic.com](mailto:success@navattic.com).
</Note>

## How Navattic captures and stores data

Navattic captures static HTML snapshots of your application — not live access to your product or its underlying data. When you use the capture tool:

* Navattic records a visual copy of your app at the moment of capture.
* Your live application data is not connected to or accessible through the demo.
* Captured content is stored and served from Navattic's cloud infrastructure.

This means visitors viewing your demo never interact with your actual application or its data.

## Protecting sensitive data in demos

Before sharing a demo, review your captures for any sensitive content that may have been included unintentionally.

### Avoid capturing sensitive screens

Before starting a capture session, navigate away from any screens that contain data you don't want included. You can also delete individual captures from a collection if they contain content you want to exclude.

### Blur sensitive content

Use the blur tool in the capture editor to mask areas containing name, locations, or sensitive data. Select any region of a capture and apply a blur to hide it from viewers.

### Edit or replace text

You can edit text directly within a capture to replace customer names, email addresses, or other sensitive strings with placeholder values.

## Demo access controls

Navattic gives you several ways to control who can view a shared demo.

| Setting                 | What it does                                                          |
| ----------------------- | --------------------------------------------------------------------- |
| **Link expiration**     | Set a date after which the share link stops working.                  |
| **Password protection** | Require viewers to enter an access code before viewing.               |
| **Domain restriction**  | Limit access to viewers from specific email domains.                  |
| **Form gating**         | Require viewers to submit a form before they can proceed.             |
| **Revoke access**       | From Launchpad, disable a share link at any time from the Manage tab. |

For more on gating demos with forms, see [Forms](/tracking/forms/index).

## Workspace security features

Navattic provides several tools for securing and governing your workspace.

<CardGroup>
  <Card title="SSO" icon="shield-check" href="/workspace/sso">
    Require members to authenticate using an identity provider such as Okta or Azure AD.
  </Card>

  <Card title="Directory sync" icon="users" href="/workspace/directory-sync">
    Automatically provision and deprovision users via SCIM.
  </Card>

  <Card title="Audit logs" icon="scroll-text" href="/workspace/audit-logs">
    Monitor workspace activity with a full audit trail. Available on Enterprise plans.
  </Card>

  <Card title="Custom domains" icon="globe" href="/workspace/custom-domains">
    Serve demos from your own branded domain over HTTPS.
  </Card>
</CardGroup>

### Roles and permissions

Navattic has three workspace roles:

* **Admin** — Full access to all workspace settings, demos, and members.
* **Builder** — Can create, edit, and publish demos. Cannot change workspace settings.
* **Rep** — View and share demos through Launchpad. Cannot build or edit demos.

This role separation helps ensure that only authorized team members can create or modify demo content.

## AI and data privacy

Navattic's AI features — including Copilot, AI avatars, and voiceover — process content to generate outputs on your behalf. Navattic does not use your demo content to train AI models. For specific details on data processing for AI features, refer to the [Navattic Trust Center](https://trust.navattic.com/).

## Security review support

If your procurement or infosec team needs additional documentation:

* Visit the [Navattic Trust Center](https://trust.navattic.com/) to download security reports and policies.
* Contact [success@navattic.com](mailto:success@navattic.com) to request custom security materials or fill out a vendor questionnaire.


# SSO
Source: https://docs.navattic.com/workspace/sso

Require members to authenticate using an identity provider, such as Okta.

<Info>Enabled in workspaces on the Growth plan and above.</Info>

## Enable SSO for your workspace

Navattic partners with [WorkOS](https://workos.com/) to support all major SSO providers. After it is enabled, you can navigate to Settings > Security to set up the configuration. The configuration setup steps will occur within your selected SSO provider; corresponding provider documentation is linked below.

Click "Manage SSO" to access a WorkOS portal that will walk you through step by step how to configure your chosen provider. Once you have selected your provider and completed the configuration steps, SSO will be turned on for your Navattic workspace, and all users will be required to complete the new authentication flow upon login.

### Supported SSO providers

Click on a provider to be taken to the relevant setup steps in the WorkOS docs. The configuration steps and confirmation will differ for each provider and be covered in the relevant docs.

<CardGroup>
  <Card
    title="AD FS SAML"
    href="https://workos.com/docs/integrations/microsoft-ad-fs-saml"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/microsoft.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="ADP OIDC"
    href="https://workos.com/docs/integrations/adp-oidc"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/adp.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Auth0 SAML"
    href="https://workos.com/docs/integrations/auth0-saml"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/auth0.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Azure AD SAML"
    href="https://workos.com/docs/integrations/azure-ad-saml"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/azure.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="CAS SAML"
    href="https://workos.com/docs/integrations/cas-saml"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/cas.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="ClassLink SAML"
    href="https://workos.com/docs/integrations/classlink-saml"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/classlink.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="Cloudflare SAML"
    href="https://workos.com/docs/integrations/cloudflare-saml"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/cloudflare.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="CyberArk SAML"
    href="https://workos.com/docs/integrations/cyberark-saml"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/cyberark.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="Duo SAML"
    href="https://workos.com/docs/integrations/duo-saml"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/duo.svg" className="my-0 h-6 w-6" />
}
  />

  <Card title="Generic SAML" href="https://workos.com/docs/integrations/generic-saml" icon="id-card" />

  <Card
    title="Google OAuth"
    href="https://workos.com/docs/integrations/g-suite-oauth"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/google.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="Google SAML"
    href="https://workos.com/docs/integrations/google-saml"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/google.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="JumpCloud SAML"
    href="https://workos.com/docs/integrations/jumpcloud-saml"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/jumpcloud.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="Keycloak SAML"
    href="https://workos.com/docs/integrations/keycloak-saml"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/keycloak.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="Microsoft OAuth"
    href="https://workos.com/docs/integrations/microsoft-oauth"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/microsoft.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="miniOrange SAML"
    href="https://workos.com/docs/integrations/mini-orange-saml"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/miniorange.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="Okta SAML"
    href="https://workos.com/docs/integrations/okta-saml"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/okta.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="OneLogin SAML"
    href="https://workos.com/docs/integrations/onelogin-saml"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/onelogin.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card title="OpenID Connect" href="https://workos.com/docs/integrations/oidc" icon="id-card" />

  <Card
    title="Oracle SAML"
    href="https://workos.com/docs/integrations/oracle-saml"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/oracle.svg" className="my-0 h-6 w-6" />
}
  />

  <Card
    title="PingFederate SAML"
    href="https://workos.com/docs/integrations/ping-federate-saml"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/ping-identity.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="PingOne SAML"
    href="https://workos.com/docs/integrations/ping-one-saml"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/ping-identity.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="Salesforce SAML"
    href="https://workos.com/docs/integrations/salesforce-saml"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/salesforce.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="Shibboleth"
    href="https://workos.com/docs/integrations/shibboleth"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/shibboleth.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="SimpleSAMLphp"
    href="https://workos.com/docs/integrations/simple-saml-php-saml"
    icon={
  <img
    src="https://cdn.workos.com/provider-icons/light/simple-saml-php.svg"
    className="my-0 h-6 w-6"
  />
}
  />

  <Card
    title="VMWare SAML"
    href="https://workos.com/docs/integrations/vmware-saml"
    icon={
  <img src="https://cdn.workos.com/provider-icons/light/vmware.svg" className="my-0 h-6 w-6" />
}
  />
</CardGroup>

### FAQs

<AccordionGroup>
  <Accordion title="How do I know the connection is complete?">
    The configuration steps and confirmation will be different for each provider and covered in the
    relevant docs. Once configured, users that exist in both your SSO provider and Navattic
    workspace will be able to sign into your workspace directly from the SSO provider's portal.
  </Accordion>

  <Accordion title="Are all Navattic workspace members required to use SSO, once configured?">
    Yes. If SSO is connected for your workspace, all members of your Navattic workspace regardless
    of user role will be required to login via the SSO provider portal.
  </Accordion>

  <Accordion title="Can I support multiple domains in my SSO provider?">
    Contact [success@navattic.com](mailto:success@navattic.com) to request this service. This is a custom connection that our team
    can help enable.
  </Accordion>
</AccordionGroup>


# Teams
Source: https://docs.navattic.com/workspace/teams

Organize workspace members into teams and control their access to demos.

<Frame>
  <img alt="Teams settings page showing a list of teams with member counts" />
</Frame>

Teams let you group workspace members together and control which demos and boards each group can access. Each team member is assigned a role that determines what they can do within that team.

## Creating a team

<Steps>
  <Step title="Open Team Settings">
    Navigate to **Settings** > **Teams** and click **Create team**.
  </Step>

  <Step title="Name and describe the team">
    Enter a **Name** for the team — something recognizable for your organization, such as "Sales Team" or "North America Sales."

    Optionally add a **Description** to explain the team's purpose. This helps other admins understand the team's scope at a glance.

    Click **Create** to save. You'll be taken directly to the team's detail page.
  </Step>
</Steps>

## Managing team members

From a team's detail page, you can add members, assign roles, and remove members.

### Adding members

Click **Add member** from the team detail page. In the modal:

1. Select one or more workspace members from the **User(s)** list.
2. Choose a **Role** to assign to all selected members. The role controls what each member can do within Navattic:

| Role        | What they can do                                            |
| ----------- | ----------------------------------------------------------- |
| **Admin**   | Full access: manage settings, publish demos, invite members |
| **Builder** | Create and edit demos, manage flows                         |
| **Viewer**  | View and share demos; no editing access                     |

Click **Add users** to confirm.

### Changing a member's role

On the team detail page, click the role chip next to any member's name to open a dropdown. Select a new role — the change takes effect immediately.

<Note>
  Launchpad Rep members are automatically assigned the Launchpad Rep role and cannot have their role changed from the team settings page.
</Note>

### Designating a manager

Workspace admins can designate any Launchpad Rep as a **Manager** on a team. Managers get access to the Launchpad Analyze pages — including Sharing activity, Buyer interest, and Sales impact — which are otherwise restricted to workspace admins.

To toggle manager status, open the team detail page, find the rep, and use the **Manager** toggle next to their name. The change takes effect immediately.

### Removing a member

Click **Remove** next to a member's name on the team detail page. Removing a member from a team does not remove them from the workspace.

### Searching members

Use the search bar at the top of the team detail page to filter members by name or email.

## Controlling demo access with teams

Teams work with [boards](/workspace/boards) to restrict which demos groups of users can see.

<Steps>
  <Step title="Create or edit a board">
    Go to the **Boards** page and click **Edit** on the board you want to restrict.
  </Step>

  <Step title="Set access to Team">
    Set the **Access level** to **Team** and select the team you want to grant access to.
  </Step>

  <Step title="Save">
    Click **Save**. The board — and all demos it contains — will now only be visible to members of the selected team.
  </Step>
</Steps>

<Note>
  Team-scoped boards can include any type of demo — Interactive Demos, Launchpad boards, or a mix. You do not need a Launchpad-only workspace to restrict board access to a team.
</Note>

## Editing a team

To change a team's name or description, open the team detail page and click **Team settings** in the top right. Update the name or description and save.

## Managing workspace roles

Navigate to **Settings** > **Roles** to view and manage the roles in your workspace.

The redesigned Roles settings page shows each role and its permissions in a table. You can see at a glance what each role can do across areas like demo building, publishing, sharing, and workspace administration.

### Theme permission

All workspaces can control which roles have access to themes. On any role's detail page, use the **Themes** permission toggle to allow or restrict that role from viewing and applying themes. When theme permission is off for a role, members in that role will not see the Themes section in the sidebar.

### Enhanced permissions

Creating or fully editing custom roles requires **Enhanced permissions**, available on the Enterprise plan. Without enhanced permissions, the Roles settings page is read-only — you can view the default role configuration but cannot modify it beyond the theme permission toggle.

To upgrade, visit **Settings** > **Billing** or contact your account team.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can a member belong to more than one team?">
    Yes. Workspace members can be added to multiple teams, each with a different role if needed.
  </Accordion>

  <Accordion title="What happens when I remove a member from the workspace?">
    Removing a member from the workspace does not automatically remove them from any teams they belong to. If you see an error related to a removed member on the Teams page, contact support to have the underlying data cleaned up.
  </Accordion>

  <Accordion title="Is there a limit to how many teams I can create?">
    Team limits depend on your plan. If you have reached your team limit, you'll see a notice on the Teams settings page. Contact sales to request an increase.
  </Accordion>
</AccordionGroup>


# Workspace captures
Source: https://docs.navattic.com/workspace/workspace-captures

Share capture collections across multiple demos from a central workspace library.

<Note>
  Workspace captures are available on the **Base** plan and above.
</Note>

<Frame>
  <img alt="Workspace capture collections showing shared captures linked across multiple demos" />
</Frame>

Workspace captures let you maintain a single library of capture collections that can be reused across multiple demos. Instead of recreating the same screens in each demo, you promote a collection to the workspace level once and link it wherever you need it.

## The workspace captures page

Navigate to **Workspace Captures** in the main sidebar to see all capture collections that have been promoted to the workspace level. From here you can:

* Browse and search your shared capture library
* Add new captures to an existing workspace collection
* Promote project-scoped collections to the workspace
* See which demos each collection is linked to

## Collection types

Capture collections exist at two scopes, indicated by icons in the captures list:

| Icon                          | Type                         | Scope                        |
| ----------------------------- | ---------------------------- | ---------------------------- |
| <Icon icon="globe" /> Globe   | Workspace capture collection | Shared across multiple demos |
| <Icon icon="folder" /> Folder | Project capture collection   | Scoped to a single demo      |

A workspace capture collection (globe icon) can be linked to any number of demos. A project capture collection (folder icon) belongs to one demo only.

## Promoting a collection to the workspace

Promoting a collection moves it from a single demo to your shared workspace library, where it can be linked to other demos.

<Steps>
  <Step title="Open the demo's Captures tab">
    Navigate to the demo that contains the collection you want to share. Open the **Captures** tab.
  </Step>

  <Step title="Open the collection menu">
    Find the collection and click the three-dot menu next to it.
  </Step>

  <Step title="Select Promote to workspace">
    Choose **Promote to workspace** from the menu. The collection is moved to the workspace library and its icon changes from a folder to a globe.
  </Step>
</Steps>

<Note>
  After promoting, the collection remains linked to the original demo. Any edits to the collection will now affect all demos it is linked to.
</Note>

## Linking a workspace collection to a demo

Once a collection is in the workspace library, you can add it to any demo from that demo's Captures tab.

<Steps>
  <Step title="Open the demo's Captures tab">
    Navigate to the demo you want to add the collection to and open the **Captures** tab.
  </Step>

  <Step title="Add a workspace collection">
    Click **Add collection** and choose **Add from workspace**. Select the workspace collection you want to link.
  </Step>
</Steps>

## Unlinking a collection from a demo

Unlinking removes the shared collection from a specific demo and replaces it with a local copy. The workspace collection itself is not affected, and other demos that use it are unchanged.

<Steps>
  <Step title="Open the collection menu">
    In the demo's Captures tab, click the three-dot menu on the workspace collection (globe icon) you want to unlink.
  </Step>

  <Step title="Select Unlink">
    Choose **Unlink** from the menu. A local copy of the collection is created for this demo, and the demo is no longer connected to the workspace version.
  </Step>
</Steps>

<Warning>
  After unlinking, changes to the workspace collection no longer apply to this demo. If you want to keep the demo in sync with updates, link it back to the workspace collection instead of unlinking.
</Warning>

## Editing a shared capture

When you open a capture that belongs to a workspace collection, a banner appears at the top of the editor:

> **Edits to this capture will affect \[N] demos across your workspace.**

The banner shows how many demos are currently using the collection. You can dismiss it by clicking **Dismiss**.

This warning is a reminder that any change you save—editing a tooltip, removing a step, updating a highlight—will appear in every demo linked to that workspace collection. If you only want to change one demo, [unlink the collection](#unlinking-a-collection-from-a-demo) first to create a local copy.


# Workspace Organization
Source: https://docs.navattic.com/workspace/workspace-organization

How to structure, manage, and govern a growing demo library in Navattic.

<Frame>
  <img alt="Navattic workspace" />
</Frame>

Navattic gives you several tools for keeping your demo library organized, current, and accessible to the right people. This page covers how to use them together as your library grows.

## Organizational building blocks

Before diving into strategy, here's a quick overview of what each tool does:

| Tool        | Purpose                                                                     |
| ----------- | --------------------------------------------------------------------------- |
| **Demo**    | A complete interactive experience made up of one or more Flows.             |
| **Flow**    | A step-by-step sequence within a demo.                                      |
| **Capture** | A snapshot of your application that one or more Flows reference.            |
| **Board**   | A curated view of demos, shared with specific teams or the whole workspace. |
| **Label**   | A tag applied to demos for filtering and categorization.                    |
| **Team**    | A group of users with scoped access to specific boards.                     |

<CardGroup>
  <Card title="Boards" icon="grid-3x3" href="/workspace/boards">
    Organize demos onto shared views.
  </Card>

  <Card title="Labels" icon="tag" href="/workspace/labels">
    Categorize demos for easy filtering.
  </Card>

  <Card title="Teams" icon="users" href="/workspace/teams">
    Scope access to demos by team.
  </Card>
</CardGroup>

## Structuring your demo library

### Boards

Create boards to group related demos — by use case, product area, sales team, or region. Start simple: a single Sales board and a single Marketing board is enough for most teams getting started. Add more boards as your library grows.

When setting up a board, decide who should see it:

* **Workspace-level access** — visible to all workspace members
* **Team-level access** — visible only to members of a specific [team](/workspace/teams)

Use team-scoped boards to prevent reps from one region or function from seeing demos that aren't relevant to them.

### Labels

Labels work across boards and let you filter demos by dimension. Some common label strategies:

* **By product area** — tag demos for each core feature or product line
* **By customer type** — enterprise vs. mid-market vs. SMB
* **By funnel stage** — prospecting, discovery, evaluation
* **By content status** — current, needs-update, archived

You can apply multiple labels to a single demo. Use the label filter on the Product demos page to find demos that match a specific combination.

### Tips for larger libraries

* Agree on a label taxonomy before you start labeling — inconsistent labels are hard to fix later.
* Use boards for audience and access, labels for content attributes.
* Review boards periodically and remove demos that no longer belong.

## Reusing content across demos

### Captures

A capture is a snapshot of your application that can be referenced by multiple flows across different demos. If your capture is updated (for example, after a product change), all flows using that capture reflect the update.

To reuse a capture in a new flow, use **Replace capture** from within the flow builder and select an existing capture from your workspace.

### Duplicating demos

To create a variation of an existing demo (for example, a version tailored to a specific vertical or audience), duplicate the demo from the Product demos page. The duplicate starts as a draft — you must click **Publish** before it appears on share links. Changes to the duplicate do not affect the original.

### Version history

Navattic tracks versions of your demos so you can see what changed over time. To access version history, open a demo in the **Build** tab and select **Versions** from the left sidebar.

## Keeping demos current

As your product evolves, your captures may become outdated. Here's a general maintenance approach:

1. **Set a review cadence.** For fast-moving products, review key demos each time a significant feature ships.
2. **Recapture changed screens.** Use the Chrome extension to take a new capture of a screen that has changed, then swap it into the relevant flow using **Replace capture**.
3. **Check labels for status.** Adding a "needs-update" label to outdated demos helps your team know which ones to prioritize.

<Note>
  Because captures can be shared across multiple flows, updating a single capture propagates the change everywhere it is used. Be careful when replacing shared captures in production demos.
</Note>

## Archiving and deleting demos

### Archiving a demo

Archiving removes a demo from your active library without permanently deleting it. Archived demos no longer appear on the Product demos page, but they can be restored at any time.

To archive a demo, open its dropdown menu from the Product demos page and select **Archive**.

To view and restore archived demos, go to **Workspace Settings > Archive**.

### Permanently deleting a demo

Admins can permanently delete an archived demo. Deletion removes the demo and all of its associated resources — flows, capture collections, captures, and published versions. This action cannot be undone.

<Warning>
  Permanently deleted demos cannot be recovered. Archive a demo first and confirm you no longer need it before deleting.
</Warning>

You can delete an archived demo in two places:

**From the Product demos page:**

1. Find the demo and open its dropdown menu.
2. Select **Delete**. This option only appears when the demo is archived and you are an admin.
3. Review the list of resources that will be deleted, then confirm.

**From the Archive page:**

1. Go to **Workspace Settings > Archive**.
2. Find the demo in the table and click the <Icon icon="more-horizontal" /> menu.
3. Select **Delete**.
4. Review the list of resources that will be deleted, then confirm.

## Governance and access control

### Roles

Navattic has four workspace roles that control what each user can do:

| Role              | What they can do                                                                                                      |
| ----------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Admin**         | Full workspace access: manage settings, configure integrations, invite and remove members, create and publish demos.  |
| **Builder**       | Create, edit, and publish demos. View analytics and integrations. Cannot manage workspace settings or invite members. |
| **Viewer**        | Browse the demo library and share demos. Cannot build or edit demos.                                                  |
| **Launchpad Rep** | View and share demos through Launchpad only. Cannot access the demo builder or workspace settings.                    |

Assign roles when inviting members. Go to **Settings > Members** to update existing roles.

### Permissions matrix

The table below shows which actions each role can perform across key areas of Navattic.

| Action                    | Admin | Builder | Viewer | Launchpad Rep |
| ------------------------- | :---: | :-----: | :----: | :-----------: |
| Create and edit demos     |   ✓   |    ✓    |        |               |
| Publish demos             |   ✓   |    ✓    |        |               |
| View demo library         |   ✓   |    ✓    |    ✓   |               |
| Share demos               |   ✓   |    ✓    |    ✓   |               |
| View analytics            |   ✓   |    ✓    |    ✓   |               |
| Archive demos             |   ✓   |         |        |               |
| Delete demos              |   ✓   |         |        |               |
| Access Launchpad          |   ✓   |    ✓    |        |       ✓       |
| Invite and manage members |   ✓   |         |        |               |
| Configure integrations    |   ✓   |         |        |               |
| Manage workspace settings |   ✓   |         |        |               |

### Approval workflow

If you want to prevent unapproved changes from going live on already-published demos, enable the **Require approval to publish** setting in **Settings > General**. Once enabled, team members without publish permission must request a review before their changes can go live.

See [Approval Workflow](/workspace/approval-workflow) for full setup details.

### Team-scoped boards

Use [Teams](/workspace/teams) to restrict which boards (and therefore which demos) specific groups of users can access in Launchpad. This is useful for separating demo content by region, function, or product line.

## FAQs

<AccordionGroup>
  <Accordion title="What's the difference between boards and labels?">
    Boards control which demos appear in a given view, and can be scoped to specific teams. Labels are tags you apply to demos for filtering — they don't control access. Use boards to organize by audience; use labels to organize by content attributes.
  </Accordion>

  <Accordion title="If I update a capture, does it update everywhere it's used?">
    Yes. Captures are shared across flows. If you replace or re-capture a screen, all flows that reference that capture will reflect the change. Review which demos use a capture before updating it in production.
  </Accordion>

  <Accordion title="Can I copy a demo to customize it for different audiences?">
    Yes. Duplicate a demo from the Product demos page to create an independent copy. The duplicate starts as a draft — publish it when you're ready for it to go live. Changes to the duplicate do not affect the original.
  </Accordion>

  <Accordion title="How do I prevent reps from editing published demos?">
    Assign reps the Launchpad Rep role in your workspace. Launchpad Reps can only view and share demos through Launchpad — they cannot access the demo builder. For admins and builders, use the [Approval Workflow](/workspace/approval-workflow) to require review before changes are published.
  </Accordion>

  <Accordion title="Where is version history?">
    Open a demo in the Demo builder, go to the **Build** tab, and select **Versions** from the left sidebar.
  </Accordion>

  <Accordion title="Can I make labels specific to a board?">
    Labels are workspace-wide and apply across all boards. You can use a naming convention to associate labels with specific boards (e.g., prefix labels with the board name), but labels themselves are not scoped to individual boards.
  </Accordion>

  <Accordion title="How do I permanently delete a demo?">
    You must be a workspace admin and the demo must be archived first. Once archived, open the demo's dropdown on the Product demos page and select **Delete**, or go to **Workspace Settings > Archive**, find the demo, and select **Delete** from its menu. Deletion is permanent and removes all associated flows, captures, and published versions.
  </Accordion>

  <Accordion title="Can I recover a deleted demo?">
    No. Permanent deletion cannot be undone. Archive demos first if you think you might need them later — archived demos can be restored at any time.
  </Accordion>
</AccordionGroup>