The Requests History dashboard helps you monitor the performance of your review requests and quickly troubleshoot any issues. Review requests will appear in the dashboard once the related order has been fulfilled.
To access the Requests History dashboard:
From your Judge.me admin, go to Reviews.
Go to the Review requests tab.
From there, you can see all review requests for fulfilled orders and take the following actions:
Sort the requests
By default, the Requests History dashboard shows the most recent requests first, sorted by the fulfilled date (shown in the Date column).
To change the sort order:
Click the Date header to sort the requests by fulfilled date.
Click the Order header to sort the requests by order name/number.
To limit results to a specific date range:
Click the arrow down icon (▾) next to the Date header.
Choose from the following presets:
Yesterday
Today
Last 7 days
Last 30 days
Last 90 days
Last 12 months
Last 3 years)
or select Custom to set a specific Starting and Ending date.
Click Apply.
Search for a specific request
To find a specific review requests:
Click the Search and filter icon (🔍︎) on the right.
Enter the order number, customer name, product, or email address to find the matching request.
Filter the requests based on status
To filter the requests by status to focus on requests that were sent, are scheduled to send, or were skipped:
Click the Search and filter icon (🔍︎) on the right.
Click Add filter + on the left, then select Status.
Choose from the following statuses:
Sent
Will send
Will skip
Skipped
Waiting for delivery
Send or skip requests
To take actions for each review request:
Find the request you want and click the 3-dot icon (⋯) next to it.
Choose one of the following actions:
Action | What it does |
Send request now | This action will immediately sends the review request.
Note:
|
Skip this request | This action will cancel this individual request. |
Always skip this customer | This action will add this customer to the Blocklist, which will cancel this and future requests to the customer. |
Always skip this product | This action will cancel this and future requests to this product.
(Available on the Awesome plan) |
See email history |
|
To skip all review requests that have not been sent:
Click the More actions dropdown in the top-right corner.
Select Cancel unsent requests skip all pending review requests for past orders.
Check status of the review requests
The Requests dashboard shows the current status of each review request so you can track what has been sent, what’s scheduled, and what needs attention.
Judge.me automatically skips review requests in the following situations to ensure relevance and avoid over-emailing:
Refunded or edited orders: If you refund or remove specific items, those items are excluded from the review request. For full order refunds, the request is skipped once we receive a restocking notification from Shopify.
Returns: Orders with active return requests are excluded. If needed, we may ask for additional permissions to access return data.
Skipped / Will skip
Another variant in the order
Another variant in the order
A review request is skipped and marked as "another variant in the order" if we've already scheduled a request for a different variant of the same product in the order.
If you still want to send this request, you can use the Send request now action.
Cannot process Custom line item
Cannot process Custom line item
A review request is skipped and marked as "cannot process Custom line item" when the customer bought a customized version of the original product (e.g. a necklace engraved with their name).
Because the custom item isn’t linked to a specific product page, we cannot match it to a reviewable product and you can’t use Send request now for these cases.
To collect reviews for custom line items, you can manually schedule review requests that point to the original product the customization is based on.
If you only want to send a few requests, you can schedule a manual review request for a single customer.
If you need to send many requests, you can schedule manual review requests in bulk using a CSV file.
In both cases, be sure to enter the product URL of the original, non-customized product so the review can be correctly attributed.
Email does not accept marketing
Email does not accept marketing
A review request will be skipped and marked as "Email does not accept marketing" if the "Send review requests to customers who have opted out of Shopify marketing emails" setting is disabled and the customer did not subscribe to marketing emails at checkout.
Requests with the “no email found” status cannot be resent with the Send request now action — if you try, you'll encounter the same status.
Hard bounce or spam complaint
Hard bounce or spam complaint
A review request is skipped and marked as "hard bounce or spam complaint" in these cases:
Hard bounce: The email address no longer exists.
Spam complaint: The customer might have clicked This is Spam or Mark as Spam in their email clients for a previous email.
In either case, our email provider (Postmark) blocks future emails to protect your sender reputation and Judge.me will automatically skip sending new requests to that address.
While we can attempt to reactivate the email address upon request, we generally recommend guiding the customer to leave a review directly on your product page instead.
Line item per order exceeded
Line item per order exceeded
A review request is skipped and marked as "line item per order exceeded" when the number of products in the order has passed the limit you've set for sending review requests.
For example, if the Collect reviews for this many items per order setting is set to 3 and the order has 5 products:
We will send out the review requests for 3 products.
We will skip the other 2 products and show the status "line items per order exceeded".
To avoid this, you can increase the number of review requests to send out for each order.
No email found
No email found
A review request will be skipped with the status "no email found" if there are no email address or phone number when the order was created (e.g. the customer added their email after checkout).
Requests with the “no email found” status cannot be resent with the Send request now action — if you try, you'll encounter the same error.
Instead, you can manually add a new request to reach out to the customer:
For one-off follow-ups, see this article to add a manual request.
If this issue affects many orders, see this article upload requests in bulk.
No engagement in the previous request
No engagement in the previous request
A review request with this status "no engagement in the previous request" is a reminder request. It is skipped if neither the initial review request nor the previous reminder email was opened by the customer. In this case, no further reminders will be sent. This helps prevent over-emailing disengaged recipients.
As this is the expected behavior designed to respect customer engagement levels, no action further action is needed when you see this status.
Product not in store
Product not in store
A review request is skipped and marked as "product not in store" when:
the product was set to Draft or was deleted
or the product is not available in your Online Store sales channel
If a review request is skipped due to the Product not in store status, you can still collect reviews by enabling out-of-store product review requests.
To do this:
From your Judge.me admin, go to Settings > Request scheduling.
Scroll down to the Advanced section.
Enable Send review requests for out-of-store products.
Enter a backup URL, ideally your Reviews Page. This link will be used in the email if the original product is unavailable.
Click Save.
Then, you can resend the requests with the Send request now action.
Request sent for another order recently
Request sent for another order recently
A review request is skipped and marked as "request sent for another order recently" if we already sent a review request to the same customer in the last 7 days.
If you still want to send this request, you can use the Send request now action to do so manually.
Review request is disabled for domestic order
Review request is disabled for domestic order
When the "Send requests for domestic orders" setting is disabled:
A review request is marked as "Skipped, review request is disabled for domestic order" if the request has already been skipped.
A review request is marked as "Will skip, review request is disabled for domestic order" if the request is scheduled to be skipped.
If you re-enable the "Send requests for domestic orders" setting:
Requests already skipped will not be retroactively resent.
Requests scheduled to be skipped will change back to the "Will be processed" status.
If you only want to resend one request with the "Review request is disabled for domestic order" status, use the Send request now action.
Review request is disabled for international order
Review request is disabled for international order
When the "Send requests for international orders" setting is disabled:
A review request is marked as "Skipped, review request is disabled for domestic order" if the request has already been skipped.
A review request is marked as "Will skip, review request is disabled for domestic order" if the request is scheduled to be skipped.
If you re-enable the "Send requests for international orders" setting:
Requests already skipped will not be retroactively resent.
Requests scheduled to be skipped will change back to the "Will be processed" status.
If you only want to resend one request with the "Review request is disabled for international order" status, use the Send request now action.
Unsubscribed email
Unsubscribed email
A review request will be skipped and marked as "unsubscribed email" if the customer has previously clicked Unsubscribe in another review request.
Requests with this status cannot be resent with the Send request now action — if you try, you'll encounter the same error.
To see all customers who unsubscribed from your review requests:
From your Judge.me admin, go to Settings > Request scheduling.
Scroll down to the Blocklist and unsubscribed emails section at the bottom.
Click Manage blocklist.
Scroll down to the Unsubscribed emails section.
Click View unsubscribed emails to see the list of unsubscribed customers.
Integrations
Event sent to Klaviyo
Event sent to Klaviyo
Review requests are marked as "Event sent to Klaviyo" when you enable sending review requests through Klaviyo.
This status doesn’t confirm the email was sent or delivered by Klaviyo, only that the event was sent successfully from Judge.me.
Waiting for delivery
Waiting for delivery
Other statuses
Email failed to deliver
Email failed to deliver
Issue:
The review request failed to send with the status "Email failed to deliver".
Why it happens and how to fix:
The "Email failed to deliver" status can happen for these reasons:
If the customer uses a Gmail address: check if you have verified your DKIM and Return-Path. Without these, Gmail may block your review request emails. Once both are verified, you can resend the request.
From your Judge.me admin, go to the Reviews section.
Click the Review requests tab.
Find the request you want to resend and click the 3-dot icon (...).
Select Send request now.
Invalid or outdated email address: If the customer is not using a Gmail address, it could mean the customer's email address is no longer valid or in use. In this case, you can manually schedule a new request to their new email address.
Will be processed
Will be processed
Troubleshoot
I'm missing requests in the Requests History dashboard
I'm missing requests in the Requests History dashboard
If you notice that some review requests seem to be missing from the Request History dashboard, there are two common reasons:
The order hasn’t been fulfilled yet
Review requests are only scheduled after an order is marked as fulfilled in your store.
If the order is still unfulfilled, you won’t see a request in the dashboard.
The requests are sorted by fulfilled date
The dashboard sorts requests by the fulfilled date (shown in the Date column), not by order ID.
This means requests may appear out of sequence when comparing order numbers. For example, if Order #2224 was fulfilled later than Order #2389, it will appear lower in the list even though the order number is smaller.