Abrazo Embeds / Troubleshooting
Troubleshoot an embed that does not load
Check the host page, installation code, source resource, allowed origin, network policy, and current Integration Kit status in a useful order.
Updated
A blank or failed component can come from the website container, an incomplete installation, an unavailable source, an expired or mismatched protected setup, a browser policy, or an Abrazo service problem. Check each boundary once and record the first clear failure.
Confirm the page and installation
Open the published page in a signed-out window. Confirm the installation code is present once, the container is visible, and a cookie banner or script optimizer did not postpone the loader indefinitely.
Check the source and site permission
Open the source record in its owning Abrazo product. Confirm it is still public or shared for the component and that the current website origin matches the protected setup.
Capture useful support evidence
Record the public page URL, component name, time, browser, visible message, and whether the Integration Kit status page reports a problem. Do not send account credentials or a setup code.
Step by step
Work through the task
- 1
Open the published website page in a signed-out private window.
- 2
Confirm the component container is visible and the generated installation code appears once.
- 3
Disable only the site's script-delay or optimizer feature long enough to test whether it is blocking the loader.
- 4
Check the source record in the owning Abrazo product and confirm its public or protected availability.
- 5
Confirm the current website origin matches the approved protected setup.
- 6
Open Integration Kit status, then send support the page URL, component, time, browser, and visible error if the problem remains.
Common questions
What should I send to support?
Send the public page URL, component name, time, browser, visible message, and a screenshot. Do not send your password or a setup code.
Can a cookie banner stop the component from loading?
A site can delay third-party or optional scripts until consent. Check how the builder classified the Integration Kit loader and whether it runs after the required consent choice.