Social Proof & Trust

A UI pattern, not a component. Trust signals — star ratings, review counts, avatar clusters, "trusted by" copy — are compositions of primitives you already have. Cognivo does not ship a cg-trusted-badge: that would duplicate cg-rating, cg-avatar-group, andcg-text behind a rigid API. Compose instead.

Uses:cg-rating ·cg-avatar-group ·cg-text · governed variants live in bias-social-proof / bias-authority.

Rating + claim

social proof

A row of stars over a short, benefit-led claim. The stars carry thesocial-proof signal; the sentence names who the peer group is. Keep the claim specific — "thousands of Australian businesses" beats a vague "everyone".

Trusted by thousands of Australian businesses

<div class="trust-block">
  <cg-rating value="5" max="5" readonly></cg-rating>
  <cg-text color="secondary" size="sm">
    Trusted by thousands of Australian businesses
  </cg-text>
</div>

Avatars + sourced rating

social proof + authority

Stacked avatars make the crowd feel real (faces > numbers), the star row quantifies it, and naming the source — "Google reviews" — addsauthority. A specific, sourced rating (4.4 from 1,000+) is far more persuasive than a rounded, unattributed one.

4.4 from 1,000+ Google reviews

<div class="trust-row">
  <cg-avatar-group size="md"></cg-avatar-group> <!-- .avatars = [...] -->
  <div class="trust-copy">
    <cg-rating value="4.5" precision="0.5" readonly></cg-rating>
    <cg-text color="accent" size="sm" weight="semibold">
      4.4 from 1,000+ Google reviews
    </cg-text>
  </div>
</div>

Why it works — and when it backfires

cognition

Two biases do the work here. Social proof: people infer correct behaviour from what similar others do — so a visible crowd lowers perceived risk. Authority bias: a credible, named source (Google, an ISO cert, a publication) transfers its credibility to you.

Helps when…

The numbers are real and specific ("4.4 from 1,000+").
The source is named and verifiable — link it.
The peer group matches the visitor ("Australian businesses" on an AU site).
It sits near the decision point (pricing, signup), not buried in a footer.

Erodes trust when…

Claims are vague or unsourced ("thousands of happy customers").
Stars are decorative with no rating behind them.
Avatars are obvious stock faces — reads as fake.
It's over-used — a badge on every section signals insecurity, not confidence.

A quiet, sourced "4.4 from 1,000+ Google reviews" outperforms a big, vague "Trusted by everyone!". Generic trust badges read as AI-generated filler and reduce credibility. Prefer real, attributable proof.

For bias-tagged, analytics-tracked surfaces, reach for<bias-social-proof> (live counts, stacked avatars) and<bias-authority> (verified / certified / featured sources) instead of hand-rolling — they carry engagedBiasIds[] so the design advisor and analytics can see them.