Begin with the intended collection
List which service, location, format and time period the page needs. A general homepage collection and a narrowly focused service page may need different material. Do not assume that every Published response belongs everywhere. The visitor should understand the context of the evidence rather than see an impressive-looking but unrelated wall of praise.
Inspect the filter combination
Boast documents filters for factors including form, location, media and consent. Multiple controls can interact, so review the resulting set rather than checking each setting in isolation. Use fictional items representing an approved story, a held story and one belonging to another location. Define the expected included and excluded items before looking at the result.
Keep curation honest
Selecting a few relevant examples for a promotional page is not the same as presenting a complete review history. Label the presentation appropriately and avoid implying that an edited selection represents every customer. Do not use a sentiment filter to make an unsupported claim about universal satisfaction. Product capability does not decide whether the surrounding representation is truthful.
Verify after changes
A new form, tag or status rule can alter which items qualify without an obvious change to the page template. Record the intended rule and review the actual public output after an authorized configuration change. If the collection is unexpectedly empty, investigate the records and filters before removing safeguards. A missing widget is less damaging than publishing material whose permission or relevance is unresolved.
An original decision example
Illustrative paired test: the approved north-branch text item appears; the south-branch item and the permission hold do not. After changing the media filter, inspect the same three cases again. Passing means the intended collection is preserved, not simply that the previously blank area now contains something visually appealing.
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 consent states and agreed terms — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Boast response visibility states — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24