Identify the failing surface
First distinguish a missing response inside the account, an absent widget item and a failed widget load. They are different problems. Record which page, item and expected behavior are involved. Avoid repeatedly importing the same customer story or changing permission settings merely because the first visible page is empty. Preserve the current state while identifying the cause.
Trace the selection path
Compare the item’s current visibility state with the widget’s form, location, media and consent filters. Boast documents those as separate controls. A published story can still fall outside a deliberately narrow collection. Conversely, changing a filter to show everything may include material that was intentionally excluded. Use the documented intended collection as the reference rather than assuming empty always means broken.
Then inspect the integration
If the expected records qualify, check the actual page embedding the component and whether its dependencies are available. A direct sharing page and an embedded widget can behave differently. Inspect the supported configuration and browser-visible result; do not paste unknown scripts or disable security protections in an attempt to make a blank area disappear. Escalate unsupported integration behavior to the provider.
Confirm the smallest correction
After an authorized change, verify that the intended story appears and the held or unrelated examples remain excluded. Record what changed and the observed result. Do not call a problem solved because one item appeared after all filters were removed. The successful outcome is the correct collection on the correct surface, with its permission and relevance boundaries intact.
An original decision example
Illustrative diagnosis: the story is Published, but the widget selects a different form and only video items while the response is text. Confirm the intended collection before changing either filter. A correct exclusion should not be treated as a technical defect, and a repair should not broaden visibility for unrelated held responses.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Boast widget fields and filters — Merchant documentation · support.boast.io · Merchant-controlled · checked 2026-09-24
- Boast response visibility states — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Boast response social sharing and direct links — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24