Skip to main content
An embed depends on both the published demo and the page that contains it. Start with the share link, then work outward to the host page. This prevents a host-site change from masking a demo or access issue.

The embed is blank or will not load

  1. Open the selected share link directly in a separate browser session. If it does not open there, check that the demo is published and the link has not been revoked, expired, or exhausted its view limit. Check whether a password is required.
  2. Copy the embed code again from Share → Embed and compare it with what is on the page. Some site editors remove scripts or iframe attributes when saving; inspect the published page, not only its editor.
  3. Check the host site’s content security policy and embedding settings. A policy can prevent an iframe or required script from loading. Ask the site administrator to inspect the browser’s console and network errors and allow only the origins actually required by the embed.
  4. Test on the destination’s published page in a separate session. An editor preview can have different permissions or restrictions from the live page.
Do not remove your site’s security policy wholesale to make an embed work. Identify the blocked resource and adjust the narrowest necessary policy with your site administrator.

The demo looks too small or is cut off

Use the embed’s desktop and phone previews as a starting point, then test the real container at both sizes. Check the container width and height and whether surrounding page styles clip overflow. Keep the controls and guide text readable without covering the product content. If the hosting tool cannot provide enough space, link to the published demo instead.

The demo shows an older version

Open the editor and check for Unpublished changes. Publish the reviewed draft, then reload the destination. The embed displays a published version rather than every saved draft edit. Confirm that the page uses the intended demo and share link; a duplicate is a separate demo and does not inherit the original’s link. If a viewer still cannot use the experience, provide the direct link and the written steps alongside it. Include the destination URL, browser, time, and observed error when asking your site administrator or ArcDemo support to investigate. Avoid sending credentials or private capture content in a troubleshooting report.

Give the next person a useful reproduction

Describe the first failing point and the comparison you made. For example: “The share link opens in a private browser session, but the inline embed on our published help page stays blank in Chrome. The console reports a blocked frame.” Include the affected page, the time and time zone, the browser and device, and whether the same link works directly. A site administrator can then distinguish a host-page restriction from a demo-access problem without needing the viewer’s password or the contents of the captured account.