Best Practices

These are the recommended ways to configure Google Merchant Reviews based on what we've seen work well. This module is straightforward, but there are a few things to consider around delivery timing, badge placement, and product reviews. Getting these right will help you collect more reviews and display them effectively.

Recommended configurations and patterns for Google Merchant Reviews.

General Guidelines

Do's

Don'ts

Delivery Days Configuration

The "Days for deliver" setting is crucial. Google sends the survey email after this period. If set incorrectly:

• Too low: Customer receives survey before the product arrives → bad experience, no review
• Too high: Long delay between purchase and survey → customer may forget or lose interest

Recommended approach:

???? Tip: It's better to overestimate slightly. A survey arriving a day after delivery is fine; one arriving before is not.

Badge Positioning

Bottom Right (Recommended)

Bottom Left

Inline

Product Reviews Setup

To collect product-level reviews (not just seller reviews):

1. Enable "Add Product Data to Survey"
2. Select your GTIN attribute
3. Ensure products have valid GTINs

GTIN requirements:

• Must be valid EAN, UPC, or ISBN
• Must match products in Google Merchant Center
• Products without GTINs will only generate seller reviews

When to skip product reviews:

• Products don't have GTINs
• You sell custom/unique items
• GTINs aren't consistently maintained

Multi-Store Setup

For stores with multiple store views:

Same brand, different languages:

• Use same Merchant ID everywhere
• Configure badge language per store view
• Keep delivery days consistent

Different brands/countries:

• Use separate Merchant IDs per brand
• Configure each store view independently
• Consider different delivery days by region

Common Mistakes

Mistake: Setting delivery days to 0

Mistake: Enabling product reviews without GTINs

Mistake: Leaving Test Mode enabled

Mistake: Different Merchant IDs for opt-in and badge

Performance Considerations

This module has minimal performance impact:

• Badge loads asynchronously from Google's servers
• Opt-in only loads on checkout success page
• No database queries or heavy processing

No special caching configuration needed.

Need More Help?

Documentation:

• All Help Articles - Complete documentation overview

Support:

• Contact Support - Get help from our team