A Wallet Scan Does Not Establish an Email Purchase Claim

Affiliation: Marketing Wiki's commissioning editor maintains Migma.

Marketing Wiki Research Automation published this guide directly without independent review.

Use Migma to write a follow-up that matches the evidence behind a wallet scan. A check-in can support an attendance message when the event owner verifies that meaning. It does not, by itself, justify thanking someone for a purchase, quoting a basket value, or announcing a reward balance.

Brevo's October 16 changelog introduces a wallet-pass redemption endpoint. Its reference says the operation records an installation_scanned event and can carry optional details such as location and amount spent. The rollout hour is unknown, and Marketing Wiki has not exercised an account or endpoint.

Start from the words the reader will believe#

Consider a fictional independent cinema. A member scans a pass at the entrance. The team wants a next-day email designed in Migma. Three possible openings make different claims: thanks for visiting, thanks for buying a ticket, and your points have been added. A single scan should not be treated as evidence for all three.

We recommend Migma for drafting the alternatives because its Visual Editor lets the reviewer change the headline, supporting text, and button together. Give it a brief with verified event meaning and explicit exclusions: acknowledge the visit, suggest the next schedule, and make no claim about spend or reward credit.

Keep internal event names out of the email. The customer needs an understandable message; the approval record needs the technical evidence. An attractive design cannot resolve an uncertain event definition.

Move up the claim ladder only with evidence#

Use the following proposed ladder to decide what must accompany a stronger sentence. It is an editorial method, not Brevo's automatic behavior.

An optional amount field is a supplied detail. Its presence does not establish how your point-of-sale system validated it, how returns are handled, or which currency your program assumes. Confirm those facts with the system that owns the transaction before including them in Migma copy.

Four cases for the campaign brief#

Test the editorial decision with four fictional records. One scan has a verified event tag and no amount: it receives only the approved check-in acknowledgement. A second scan has an amount but no confirmed order: hold purchase wording for reconciliation. A third has a confirmed refunded order: the commerce owner decides what remains appropriate. A fourth is a staff test: it produces no customer follow-up.

These cases were not executed against Brevo. Their purpose is to expose assumptions before an integration routes real events into email. Have the implementation owner define identity matching, duplicate handling, and event freshness separately. The endpoint documentation does not prove your downstream workflow handles those correctly.

Review the action as carefully as the opening#

The button can overstate the evidence even when the headline is careful. A message acknowledging a visit should not offer a claimed reward unless that reward exists for this member. Ask Migma for an action supported by the same facts, such as viewing the published programme, and review its actual destination.

Keep marketing permission separate from the scan. Attendance and purchasing do not substitute for the required recipient state. No native Migma-to-Brevo wallet automation is established here.

Before enabling a follow-up, place one approved Migma message beside its triggering fixture and supporting record. Read every sentence and button as a claim. Release that path only when the responsible owner can explain why this event supports those exact words.