Bind Email Star Ratings to the Product and Evidence

Every star-rating block in a Migma email should identify what was rated, the scale, the count behind the score and the date the evidence was captured. A polished badge must not turn a store-wide rating into a product claim or present an invented quote as a customer's words.

Editorial disclosure: Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Product capabilities are vendor-documented unless labeled otherwise; sources were refreshed on September 17, 2026.

Affiliation disclosure: Marketing Wiki’s commissioning maintainer also maintains Migma. Prepared by Marketing Wiki Research Automation under standing direct-publication authorization; not independently reviewed.

Migma's September 16 fashion-template guide discusses social-proof content as an email pattern. That is a useful design lead, not verification of a particular review. We recommend building the block in Migma's Visual Editor from an approved proof card, with the evidence checked before typography and imagery are applied.

Build the proof card before the visual block#

For a fictional travel bag, the private working card could contain:

Item: current travel-bag product family, defined variants listed
Source: approved review-system export and public destination
Score: 4.6 out of 5
Rating count: 210
Written review count: 84
Snapshot: recorded date and time
Selected quote: exact approved excerpt, tied to its source review
Exclusions: do not call all ratings written reviews
Refresh trigger: next send or product-family change

These numbers are invented to illustrate the fields. They must not be copied into a real campaign. Add permission and attribution decisions through the organization's review process; this card does not establish rights to reuse customer content.

The Schema.org AggregateRating vocabulary distinguishes the reviewed item, rating value, rating count, review count and rating scale. That vocabulary is useful for naming the fields. It does not prove that a store's displayed score is authentic, that Migma imports reviews, or that adding structured markup to an email will create search visibility.

Do not average already averaged stars#

Suppose two fictional product groups use the same five-point scale and compatible inclusion rules. Group A has 10 ratings averaging 5.0. Group B has 90 ratings averaging 4.0.

A simple average of the two displayed scores is 4.5. A count-weighted calculation is (10 × 5.0 + 90 × 4.0) / 100 = 4.1. Those answers differ because the group sizes differ.

Even the weighted calculation is not automatically publishable. The source averages may be rounded, the groups may overlap, or the products may not belong in one combined claim. Prefer the source system's authorized aggregate when it represents the intended scope. Use the counterexample to catch invalid arithmetic, not to manufacture a new score from insufficient data.

A brand-level rating should remain labeled at brand level. Do not place it immediately beneath one product image in a way that implies the score belongs only to that item.

Quotes require context as well as exact words#

Read the complete source review before selecting an excerpt. A sentence praising appearance may be followed by a material qualification about durability or fit. Extracting only the praise can change the meaning even when the chosen words are copied exactly.

Keep the reviewed version and variant with the source. A review of an older backpack construction should not silently support a claim about a redesigned current model. If a translated excerpt is used, have its meaning reviewed and label the treatment appropriately under the team's policy.

Do not ask an AI assistant to “write a realistic customer quote.” Ask it to format an approved excerpt or summarize a documented theme in the company's own voice, with no quotation marks or invented attribution.

Assemble a reader-facing block in Migma#

Migma's Shopify guide documents available store context for preparing email. It does not establish an automatic review feed, so supply the verified proof card separately when needed. Tell the draft to preserve the score, scale, count label and item scope exactly.

Then inspect the visual hierarchy. The product name, rating label and count must remain associated on narrow screens. A small qualifying label separated from a large star graphic can make a technically present disclosure practically hard to understand.

Link to the approved source destination where appropriate and check the final sender's output. If the score has changed by release time, refresh the snapshot and copy or make the dated nature of the claim clear.

No reviews were collected and no live rating feed was tested here. Use the immutable-copy manifest to preserve approved values after this evidence check. Begin by replacing one unexplained star badge with a proof card that another editor can verify.