E-commerce
Social proof on the page where people decide.
Your product photography shows what the thing looks like in a studio. A customer's photo shows what it looks like in a kitchen with bad lighting, which is the version the person hovering over Add to cart is actually trying to imagine.
Who this is for
Online stores with real customers already posting about the product, most often homeware, apparel, beauty, food and anything with a visible result. If nobody is photographing your product yet, collection is your problem and a widget will not solve it.
A good fit
- Shopify, WooCommerce or any store where you can add a block to a product template
- Brands with an existing tagged-photo habit among customers, however small
- Categories where the buying question is "what will this look like in my life"
- Stores with a Google Maps listing carrying reviews that never reach the site
Probably not for you if
- Pre-launch stores with no customers and no posts. There is nothing to show yet
- Products where the proof that matters is a specification, not a photograph
- Anyone hoping to display photos from accounts they do not own and cannot get permission from
The proof exists. It is just not on the page.
Most stores already have everything they need scattered across three or four places, none of which is the product page. The work is not producing proof. It is moving it to where the decision happens and keeping it current after the launch week.
- Customer photos sit on Instagram, seen by people who already follow you rather than by people deciding whether to buy
- Google reviews sit on a Maps listing that a visitor has to leave your site to find
- The testimonials that did make it onto the site were pasted in eighteen months ago and have not moved since
- Screenshots of good posts go stale the moment the account changes its avatar or the post is deleted
Customer photography varies wildly in shape and quality, which is exactly what a masonry layout is for. It lets a tall phone photo sit next to a wide one without cropping either into nonsense.
Where it goes, and why there
A social feed on a homepage is decoration. The same feed lower on a product page, at the point where someone is weighing it up, is doing work. Placement decides whether this converts.
Below the product description
After the specification and before the reviews section. The visitor has finished asking what it is and started asking whether it is for them, which is exactly what a customer photo answers.
Beside the price on a considered purchase
On higher-value items where the hesitation is real, a compact review widget next to the price does more than a wall of photos further down. Reviews layout, five or six entries, not fifty.
On the cart or checkout page
A quiet strip of recent reviews at the point of highest abandonment. Keep it small and keep it below the primary action. This is reassurance, not a second sales pitch.
On category pages, filtered by tag
One campaign tag per collection lets a category page carry proof specific to what is on it, rather than the same homepage wall repeated.
Reposting a customer's photo is a permissions question, not a technical one
A photo posted publicly with your hashtag is not a photo you have been licensed to use in commercial marketing. Platform terms do not transfer any rights to you, and a product page is unambiguously commercial. This is the most common way a UGC programme creates a problem for the brand it was meant to help.
- Ask before a customer photo goes on a product page, a comment requesting permission and their reply is a real paper trail
- Keep attribution visible: handle, avatar and a link back to the original post
- Remove on request immediately and without negotiating; moderation is one click for exactly this reason
- Your own posts and your own Google reviews carry none of this friction, which is why most stores start there
- If you run a photo competition, put the licence terms in the entry conditions rather than assuming the tag implies consent
E-commerce questions, answered
The mechanism is well established (people use other people's behaviour to resolve uncertainty), but the size of the effect depends entirely on your category, your traffic and your placement. Treat any specific percentage you read as marketing rather than research, and measure it on your own store with a proper test.
Below the description and above or beside the written reviews. That is the point where a visitor has stopped asking what the product is and started asking whether it suits them. Above the fold it competes with your own photography and usually loses.
Yes. One feed can mix both, though on a product page they usually work better separately, reviews in a compact layout near the price, photos in a masonry grid further down. The same curated content can be embedded twice in two layouts.
The reliable levers are a printed card in the parcel with a short, unusual hashtag, a post-purchase email asking for a photo rather than a review, and actually resharing what people send. A widget displays the result; it does not create the habit.
The script is deferred and the feed is fetched after your page has rendered, so it never blocks your own content, and images inside it lazy-load. There is no iframe and no framework shipped to your visitors, meaningfully lighter than a stack of native platform embeds.
Keep reading
See it with your own content.
Connect one source on the free plan and the whole editor works against your posts before you publish anything.
Start free