Embed Parameters, Allowed Domains, and Troubleshooting

Diagnose embed loading, responsive layout, language/theme, authentication, and browser-policy issues.

Best for: Event producers, display operators, accessibility leads, broadcast/AV engineers, web teams, and authorized remote operators.

Before you start

Availability depends on event access, plan entitlements, destination enablement, language configuration, and supported browser/display/network behavior.

• Use the correct event and final source/target language configuration.
• Know the physical or web destination, resolution, audience, privacy level, and monitoring owner.
• Test the final receiving screen, embed, graphics path, or operator device—not only the setup preview.

Troubleshooting steps

1. Inspect the final page. Confirm exact parent URL, scheme, iframe URL, and error.
2. Check allowed domains. Match hostname/subdomain and environment exactly.
3. Check CSP/frame policy. Parent and child policies must permit the embed.
4. Check HTTPS. Remove mixed-content HTTP resources.
5. Check parameters. Use documented encoding/names and enabled language values.
6. Check layout. Inspect iframe CSS, aspect/height, overflow, mobile breakpoints, and safe areas.
7. Check browser features. Autoplay/TTS/fullscreen and third-party storage may need policy/user action.
8. Reproduce minimally. Test the same iframe on a simple approved page to isolate host-site CSS/scripts.

After the fix: The intended audience or operator receives the correct event, language, styling, and control level with a documented reconnect and fallback path.

Confirm the fix

• The issue is isolated to domain/security policy, URL/parameter, event state, or host-page layout and fixed without weakening unrelated protections.

If the problem continues

Works directly but not embedded

Check allowed domain/CSP/frame policy.

Works on desktop not mobile

Fix responsive height/overflow and mobile browser restrictions.

Redirects to sign-in

The wrong authenticated destination was embedded.

Escalation and safety

• Do not use wildcard domains unnecessarily.
• Do not weaken CSP globally.
• Never log/share private tokens.

Related guides

• Embed 4All Captions in a Website
• Security and Privacy
• Network Requirements