Overview
What Evident does, how the pieces fit together, and where to start depending on what you are trying to ship.
3 min read
Evident collects evidence that your products are worth buying — reviews, photos, questions, loyalty activity — and puts it in front of shoppers without slowing your storefront down.
There are four things in the box. You can run any one of them on its own.
- Reviews. Request them by email after an order, moderate them, and display them on product pages with a verified-purchase badge.
- Loyalty. Points for orders and reviews, tiers, and rewards that redeem as store credit or a coupon.
- FAQs. Merchant-answered questions scoped to a product, a category, a page or a blog post, rendered with
FAQPagestructured data. - Galleries. Curated photo and video content, embedded anywhere.
Each of the four can be switched off per store under Settings → Features, which hides its widgets and its section of the admin sidebar.
How the pieces connect
Evident is not a storefront app that lives inside your theme. It is an API with a small storefront SDK in front of it.
- A platform connection (BigCommerce, Shopify, or your own code) supplies the catalogue and orders.
- Orders drive everything else. A shipped order is what schedules a review request, what awards loyalty points, and what makes a reviewer “verified”.
- The widgets read back out. A single
<script>tag plus adata-evident-widgetcontainer renders reviews, ratings, FAQs, galleries and the loyalty panel.
If you only remember one thing: nothing happens until orders are flowing. A store with a catalogue but no orders will look connected and do nothing.
Where to start
- Setting up for the first time → Quick start, then Connecting your store.
- Building on a custom storefront → Headless storefronts.
- Moving from Yotpo, Stamped, Judge.me, Okendo or Loox → Importing & exporting reviews.
- Writing code against the API → API keys & scopes and Using the API.
- Trying to achieve something rather than configure something → the Guides section is organised by job, not by screen.
What this section is, and is not
These docs are tactical: where a setting lives, what a field does, what happens when you change it. They assume you already know what you are trying to do.
For the broader “how do I run a review programme” question, read a guide. For connecting a specific third-party tool, see Integrations. For what a feature does before you buy, see Features.
Something missing or out of date? Email [email protected] — docs corrections go straight to the team that builds the feature.