A promotional email can make two promises before a customer reaches checkout: the offer shown in the inbox preview and the offer explained inside the message. If those disagree, a well-designed email still sends the reader down the wrong path.
Create and review the email in Migma, then check the Gmail annotation separately in Klaviyo's final sending version. Use one approved set of offer facts for both surfaces. Do not rely on the annotation to carry a condition that disappears when the reader opens the message.
This guide is published by Migma. It is a review workflow, not an independent performance test or a guarantee that Gmail will display an annotation. Official guidance was checked on October 16, 2026.
Check the offer before troubleshooting visibility
Start with the approved offer record: what is included, who qualifies, which code applies, when it begins and ends, and where it can be redeemed. Ask the offer owner to resolve ambiguity before building either surface.
For an invented example, a store might approve a discount on selected desk accessories for a defined period. An inbox preview saying “Everything discounted” would misrepresent that offer even if the annotation markup were technically valid. The email body and landing page need the same scope.
Klaviyo's Gmail annotation article covers deal, image, and carousel annotations. The narrower task here is checking agreement between the preview, Migma creative, and actual redemption path.
Build the complete message in Migma
Give Migma the reviewed offer facts, approved products, and intended action. Ask for clear scope near the main offer and a useful destination. Keep material conditions in readable email content instead of assuming the inbox preview will always appear.
Use a brief such as: “Create a short offer email for the approved desk-accessory collection. Preserve the exact code and deadline supplied. Do not call it a sitewide sale. Show one clear collection-page action and keep the key eligibility conditions visible near the offer.”
Review the subject and preview text as well as the body. If the annotation does not display, those ordinary inbox elements still need to describe the email accurately. An image or deal badge should reinforce a clear message rather than rescue an unclear one.
Migma's brand settings help keep reviewed product facts, identity, and instructions available during drafting. Check that saved guidance does not contradict this particular promotion.
Compare the offer across three surfaces
Use a short reconciliation table before the sending owner implements the annotation.
| Fact | Inbox annotation | Email and destination review |
|---|---|---|
| Offer scope | Accurate short description | Same included range and exclusions |
| Code | Exact approved code | Same code and working redemption path |
| Timing | Approved start and end values | Readable deadline that means the same moment |
| Product image | Relevant current product | Same product or a clearly explained collection |
| Destination | Intended campaign URL | Correct market and offer page |
These are editorial review fields, not a schema specification. Have the implementation owner use current official field definitions and formatting. Ask them to translate the approved timing into the required date-time values without changing the intended deadline.
Check localized and market-specific versions separately. A price, currency, stock status, or code that works for one destination does not prove the same offer is available elsewhere. Narrow the audience or change the approved creative where needed.
Follow the supported Klaviyo implementation path
Klaviyo's support instructions state that annotation code is supported in custom HTML or hybrid emails, rather than its drag-and-drop editor. The same guidance describes sender allowlisting and the annotation fields. Check that current guidance before asking a developer to implement the final version.
Do not assume that Migma automatically creates or preserves Gmail annotation markup. Migma's export documentation describes reviewed creative handoff; the sending owner must inspect the destination and its additional markup separately.
After implementation, compare the actual final message with the approved Migma creative. Keep a copy of the agreed offer facts alongside the annotation values so the next reviewer can spot a stale code or deadline without reverse-engineering the campaign.
Diagnose a missing annotation without changing the offer
A missing preview does not automatically mean the email body is broken. Klaviyo says Gmail decides when annotations appear and describes supported Promotions-tab conditions, sender eligibility, image requirements, and inbox-density limits.
Use Google's annotation preview tool to review the final markup. Google's page says the tool checks potential problems including syntax, image quality, supported aspect ratios, formats, and URLs. A preview is useful diagnostic evidence; it is not a promise of display for every subscriber.
Have the sending owner check the final markup, current eligibility guidance, supported inbox view, and offer dates. Do not expand a test send to real subscribers merely to force a visual result. Follow your normal authorized testing process.
Run Migma Email Preflight on the email itself and resolve relevant findings. Then inspect the destination-platform message and redemption path. Save the checks separately: body review passed, annotation preview passed, and real inbox display observed or unconfirmed. Start the next Migma promotion with the same discipline: one offer, accurately represented wherever it appears.
Frequently Asked Questions
Will a valid annotation appear for every Gmail recipient?
No. Klaviyo documents sender and inbox conditions, and Gmail decides when annotations display. A successful preview helps validate markup but does not guarantee display for each subscriber.
Can I put the offer conditions only in the annotation?
Keep material terms in readable email content and the redemption path too. The ordinary subject, preview text, and body must still make sense when the annotation is absent.
Does Migma generate Gmail annotations automatically?
Do not assume it does. Use Migma for reviewed email creative, then have the sending owner implement and verify any additional annotation markup in the supported Klaviyo template path.
Why can a test email fail to show an annotation?
The final markup is only one factor. Review current sender eligibility, supported inbox conditions, image requirements, and dates using official guidance. Record unconfirmed display honestly rather than sending to real subscribers just to force a preview.