name: Walnut Embedded Components
description: >-
  Walnut's client-side and embeddable surface. Delivery is iframe-based rather than
  library-based: there is no web-component package, no loader script, and no npm-distributed
  element library. A demo, Playlist or Deal Room is published as a URL and dropped into a host
  page as an <iframe> snippet copied from the application, optionally on a customer-owned custom
  domain. Creation-side tooling is a Chrome extension. There is no first-party JavaScript SDK.
generated: '2026-08-13'
method: searched
source: https://help.walnut.io/help/playlists/embed-demos
docs:
  - https://help.walnut.io/help/playlists/embed-demos
  - https://help.walnut.io/help/demos/publish/embed-performance
  - https://help.walnut.io/help/demos/publish/custom-domain
  - https://help.walnut.io/help/demos/getting-started/chrome-extension
  - https://help.walnut.io/help/demos/analyze/tracking-pixels

loader_libraries: []
loader_note: >-
  None published. Walnut ships no <script> loader, no npm element package and no CDN bundle. The
  embed is a raw iframe whose src points at app.teamwalnut.com or a customer custom domain.

families:
  - name: Embedded demo
    kind: iframe embed
    description: >-
      An interactive product demo rendered inside a host page — a website, CMS, LMS, help center
      or content portal — anywhere HTML iframes are allowed.
    how_to_get: >-
      Walnut Library → three-dot menu on the demo thumbnail → "Get embed code"; or Demo Launcher
      → three-dot menu → "Get embed code" → "Copy Embed Code".
    mechanism: <iframe> snippet generated by the application
    configurable:
      - Fixed-size wrapper for responsive layout
      - Default language for the embedded experience
      - Screen display settings
    docs: https://help.walnut.io/help/playlists/embed-demos
  - name: Embedded Playlist
    kind: iframe embed
    description: >-
      A curated multi-asset experience (demos, videos, PDFs) embedded the same way as a single
      demo, with the same embed-code flow.
    docs: https://help.walnut.io/help/playlists/embed-demos
  - name: Digital Sales Room / Deal Room
    kind: hosted surface
    description: >-
      A shared, branded deal space with live interactive demos embedded directly into it, plus
      content tabs and a Mutual Action Plan. Delivered as a Walnut-hosted link rather than
      something a developer mounts.
    plan: Scale
    docs: https://www.walnut.io/digital-sales-room-software/
  - name: Showcase
    kind: hosted surface
    description: Public, embeddable interactive demos intended for marketing sites and campaigns.
    docs: https://www.walnut.io/showcases/
  - name: Custom domain
    kind: delivery configuration
    description: >-
      Serve demos from the customer's own domain via a CNAME record instead of
      app.teamwalnut.com. An add-on feature.
    mechanism: CNAME
    add_on: true
    docs: https://help.walnut.io/help/demos/publish/custom-domain
  - name: Tracking pixels
    kind: injected snippet
    description: >-
      Customer-supplied code snippets added to demo screens, so third-party analytics and
      advertising pixels fire inside the demo experience.
    docs: https://help.walnut.io/help/demos/analyze/tracking-pixels
  - name: Embedded lead forms
    kind: third-party embed
    description: >-
      HubSpot, Marketo and Pardot forms embedded inside a demo, plus support for external forms
      hosted on the customer's own site when the demo is iframe-embedded, and GatedContent forms.
    providers: [HubSpot, Marketo, Pardot, GatedContent, external]
    docs: https://help.walnut.io/help/demos/personalize/lead-forms/external-lead-forms
  - name: Salesforce deal view
    kind: host-application embed
    description: >-
      Walnut demo analytics embedded into Salesforce object layouts — launch demos, see deal
      analysis and open custom Walnut reports from inside the Salesforce app.
    plan: Accelerate and Scale
    docs: https://help.walnut.io/help/integrations/salesforce/setup-6-embed-deal-view
  - name: Highspot pitch content
    kind: host-application embed
    description: Walnut demos included as content inside Highspot Pitches.
    docs: https://help.walnut.io/help/integrations/more-integrations/highspot.md

creation_tooling:
  - name: Walnut Chrome Extension
    kind: browser extension
    description: >-
      Captures screens from a live product (HTML capture and video capture), records interactions,
      runs Story Capture, and plays Playlists.
    store_url: https://chromewebstore.google.com/detail/walnut-sales-demo-platfor/mccegadjoafkdahijbbincjlicfjjibd
    browsers: [Chrome]
    firefox_supported: false
    firefox_note: >-
      Walnut documents that it does not currently support a Firefox browser extension.
    docs: https://help.walnut.io/help/demos/getting-started/chrome-extension

performance_guidance:
  docs: https://help.walnut.io/help/demos/publish/embed-performance
  note: >-
    Walnut publishes a dedicated guide on how and when an embedded demo loads and its effect on
    page speed, plus a benchmarks page at
    https://help.walnut.io/help/resources/benchmarks/embedded-performance.

gaps:
  - No web component, custom element, or npm-published embed library.
  - No JavaScript SDK for programmatic control of an embedded demo (no play/pause/navigate API).
  - >-
    No documented postMessage event contract between the embedded iframe and the host page, so a
    host site cannot react to in-demo events client-side; engagement data comes back only through
    webhooks or the Customer Data API.
  - >-
    Embed codes are produced by clicking in the application. There is no API to generate or
    manage a share link or embed snippet.