# Judge.me Reviews

> Import Judge.me feedback into VOC and curate it for storefront review islands

Canonical URL: https://0.0.0.0:3005/guides/judge-me-reviews

Judge.me reviews enter Lexsis as VOC submissions. That makes the same feedback
searchable and filterable in VOC, while giving the storefront team a curated,
reusable set of customer proof for review islands and A/B tests.

## Connect or import

Open [Integrations](https://app.trylexsis.com/integrations) in the Lexsis app and
select **Judge.me**. Choose one
of these paths:

| Path | What to provide | Best for |
|---|---|---|
| Live sync | Shopify shop domain and a Judge.me private API token | Ongoing review ingestion |
| CSV import | A Judge.me CSV export, up to 10 MB | Historical imports or a one-time backfill |

The shop domain and API token are only required for live sync. A CSV import
uses the connected Shopify store. The optional webhook secret is used to
verify Judge.me webhook deliveries.

Do not upload review exports from the **Reviews** page. That page is only for
curating reviews after they have been ingested.

## CSV columns

Use a UTF-8 CSV. Only `body` is required, but include the recommended columns
when they are available.

| Column | Required | Purpose |
|---|---:|---|
| `body` | Yes | Review text |
| `rating` | Recommended | Review rating |
| `title` | Recommended | Review title |
| `created_at` | Recommended | Review date |
| `review_id` | Recommended | Stable id for deduplication |
| `name` | Recommended | Reviewer name |
| `verified` | Recommended | Verified-purchase status |
| `shopify_product_id` | Recommended | Shopify product association |
| `product_handle` | Recommended | Product handle when an id is unavailable |
| `picture_urls` | Optional | Comma-separated external image URLs |
| `video_urls` | Optional | Comma-separated external video URLs |

The importer also accepts these aliases:

- Review id: `id`, `review_id`, `judge.me_review_id`, or `judge_me_review_id`
- Review text: `body`, `review`, or `content`
- Date: `created_at`, `created`, or `date`
- Rating: `rating` or `score`
- Reviewer: `name` or `reviewer_name`; `reviewer_id` or `customer_id`
- Verification: `verified` or `verified_buyer`
- Product: `shopify_product_id` or `product_id`
- Images: `picture_urls` or `image_urls`

Use comma-separated URLs in the media columns. Lexsis keeps Judge.me media as
external URLs; it does not copy the image or video binaries into Lexsis.

## Curate storefront proof

After importing, open [Storefront → Reviews](https://app.trylexsis.com/storefront/reviews):

1. Start on the **Collections** tab to see all reusable proof sets.
2. Select **Start a collection**.
3. Choose reviews manually, or use **Find by intent** to get editable
   semantic candidates before selecting the final reviews.
4. Mark the collection active when it is ready for use.

New imports appear in **All reviews** immediately. Intent matching becomes
available after the standard VOC pipeline has segmented and indexed the review.
One review can be included in more than one collection; its collection
membership is visible anywhere the review is listed.

The page intentionally links back to **Integrations** for all connection and
CSV-upload work. This keeps ingestion in one place and keeps the Reviews page
focused on editorial selection.

## Use a collection in an island

Use `ReviewCarousel` for a compact proof block, or `ReviewList` for a fuller
review experience. Set the island's `collectionId`. The page supplies the
reviews endpoint at runtime; do not set `reviewsEndpoint`.

```html
<lx-island name="ReviewCarousel">
  <script type="application/json">
{
  "collectionId": "YOUR_REVIEW_COLLECTION_ID",
  "minRating": 4,
  "pageSize": 8,
  "variant": "grid",
  "autoplay": false
}
  </script>
</lx-island>
```

`collectionId` limits the island to the curated reviews and preserves the
collection order. You can also pass `productIds`, `minRating`, and `sort` when
appropriate.

## A/B tests

When an experiment is prepared, Lexsis stores the selected review collection
as an immutable snapshot for each prepared arm. Later changes to the
collection do not alter a running experiment. This lets one arm test a
different review set without changing the social proof visitors in an active
test have already been assigned.

See [A/B Testing](/guides/ab-testing), [ReviewCarousel](/islands/social-proof/review-carousel),
and [ReviewList](/islands/social-proof/review-list) for the surrounding
workflows.