Metadata shown on cards
Every card in the Proof Library carries a consistent set of metadata so a reviewer can scan the page and trust what they see without opening every item.
On every card:
- Type badge: labels the card as Video Testimonial, Written Testimonial, Review, or Social Post.
- Proof content preview: a thumbnail for video, the testimonial text body for written, a screenshot preview for reviews and social posts where available, plus a platform logo for review and social cards.
- Campaign name: which campaign the proof came from.
- Submitter identity: submitter name when available, falling back to email when no name was captured.
- Approval date: when the item was approved into the library.
- Star rating (testimonials only, where present): a horizontal row of five star icons with the rated count filled. Cards for legacy testimonials without a rating render without the star row rather than showing empty stars.
- Type-specific action: play for video, Copy for written testimonials, Open link for review and social cards. Video cards also support downloading the video.
This consistency means a reviewer can use the same scanning pattern across mixed proof types.
Status values and what each means
A submission moves through a small set of states. Only one of those states puts the item in the Proof Library.
- Pending: the submission has been captured but has not been reviewed. Pending items live on the campaign’s submissions view, not in the library.
- Approved: the submission has been approved by a reviewer. Approved items appear in the Proof Library on the next load.
- Rejected: the submission has been rejected by a reviewer. Rejected items stay on the campaign but never appear in the library.
The Proof Library shows approved items only. There is no draft view, no pending view, and no rejected view inside the library; those states stay on the campaign so the library remains a single, trustable place for proof that is ready to reuse.
Differences between card view and detail view
A card is built for scanning. A detail view is built for confirming.
What the card shows:
- Type badge, content preview, campaign, submitter identity, approval date.
- For testimonials with a rating: the star row.
- The type-specific action.
What the detail view adds on top of that:
- Submitter email alongside the name.
- The main question and any bullet guidance shown to the submitter.
- For text testimonials: the full response.
- For video testimonials: the embedded recording.
- For testimonials: the star rating positioned near the top of the submission next to the name and date.
If a card does not have enough context to decide, open the detail view from the campaign’s submissions list.
Legacy items and how they render
Items submitted before the redesigned collection page launched are called legacy items. They are still valid proof and they still appear in the library after approval, but they may be missing some of the newer fields.
How legacy items render:
- No star rating: the card renders without the star row rather than showing empty stars. The detail view shows a small No rating captured placeholder instead of empty stars.
- No submitter name on legacy text testimonials: the card falls back to the submitter email for identity.
- All other metadata (campaign, type, approval date, content) renders normally.
Legacy items are never re-prompted to backfill a rating or name. They stay exactly as they were captured.
Reviewer tips for using metadata versus opening detail
Use the card metadata when:
- You only need to confirm what type of proof an item is.
- You only need the campaign, submitter identity, or approval date.
- You only want to play a video, copy a quote, or open a review or social link.
Open the detail view from the campaign’s submissions list when:
- You need to see the rating in context with the response.
- You want to see the exact main question and the bullet guidance the submitter saw.
- You need the submitter email for follow-up.
- You are checking a legacy item and want to confirm what was and was not captured.
Status transitions and what triggers them
A submission’s state changes through reviewer action on the campaign:
- Pending → Approved: a reviewer approves the submission on the campaign. The item appears in the Proof Library on the next load with its full metadata.
- Pending → Rejected: a reviewer rejects the submission on the campaign. The item stays on the campaign but does not appear in the Proof Library.
- Approved → Rejected (correction): if an approval was wrong, the fix happens on the campaign’s submission, not in the library. Once the item is no longer approved, it stops appearing in the library on the next load.
Transitions are reviewer-driven. The Proof Library reflects whatever state the campaign currently records for each submission.